Direct / None means GA4 lacks a clear referral source. Legitimate direct visits and missing source information can both contribute. Someone may type your address or open a bookmark; another visitor may follow a campaign link whose source information never reaches Analytics.
Start by checking how a known link reaches a tracked landing page. Then use the report to choose what to investigate next. You can fix avoidable measurement gaps, but you cannot identify every visit or eliminate all Direct / None traffic.
What does (direct) / (none) mean?
In a source / medium report, (direct) is the source and (none) is the medium. It is different from the broader “Direct” channel label. Google’s explanation of Direct / None lists missing campaign information, redirects, offline documents and tracking interference among the possible causes, alongside direct visits.
Keep the report’s scope in view. Use Session source / medium to investigate session acquisition; First user source / medium answers how a user was first acquired. Google’s guide to traffic-source scopes also explains why a direct return can retain credit for an earlier campaign. A recorded source is not a complete history of every click.
Does Direct / None mean traffic from AI?
No. Direct / None alone cannot establish whether traffic came from AI. It does not identify Google AI Mode, a chatbot, a messaging app or any other particular source. There is no basis here for claiming that Google AI Mode strips referrers by design or that all its clicks become direct traffic.
Google says traffic from AI Overviews and AI Mode is included in Search Console’s overall Web performance reporting. That aggregate does not isolate AI clicks, and it does not explain an individual GA4 Direct / None session. If AI visibility is your wider question, our AI search and SEO checklist separates observable evidence from assumptions.
Worked example: a newsletter link
This is an illustrative example, not measured Serpio results. An untagged email link can arrive without identifiable campaign information, especially when the email client provides no usable referrer. Add campaign parameters to a link you control so Analytics has explicit values to collect:
https://tryserpio.com/?utm_source=newsletter&utm_medium=email&utm_campaign=ga4_guide
utm_source=newsletternames the source distributing the link.utm_medium=emaildescribes the marketing medium.utm_campaign=ga4_guideidentifies this campaign so its links can be grouped.
Google’s manual-tagging documentation explains how these parameters populate traffic-source dimensions. Use a consistent naming convention; UTM values are case-sensitive, so newsletter and Newsletter split reporting.
- Test the link as delivered. Open a test email and follow its actual link, including any email-service wrapper or short URL. Check the final address for all three parameters and their exact values. On desktop, use the browser’s Network panel with Preserve log enabled to inspect redirects and find the hop that drops or changes a parameter. If the site cleans the address with JavaScript, also inspect what the first permitted Analytics event actually receives.
- Check collection. In an authorized test, use Tag Assistant to enable debug mode for your device, then open GA4’s Admin → Data display → DebugView. Inspect the landing-page event’s
page_locationparameter. Check that the correct property receives the tagged location when analytics consent permits collection. Keep the test separate from customer results. - Find the session in reporting. Open Reports → Acquisition → Traffic acquisition, select the test date range, and change the table’s primary dimension to Session source / medium. Search for newsletter / email; add Session campaign as a secondary dimension to check
ga4_guide. If your report navigation differs, locate Traffic acquisition in the published report collection; an editor can restore it. See Google’s Traffic acquisition report guide.
Clicking the link does not guarantee that classification. It depends on your implementation, consent, collection and report processing. Google also notes that a new campaign encountered during an existing session does not start a new session. Test a fresh session and allow processing time before diagnosing a missing row.
A five-point troubleshooting checklist
Pick one affected landing page and one link whose origin you know. Record what you inspected, the finding and the change date.
- Campaign tags. Inspect the actual outbound links in emails, social posts, partner placements and documents you control. Check source, medium and campaign values for omissions, typos and inconsistent case. A missing tag identifies a preventable gap in campaign labeling; it does not identify the source of old direct sessions. Fix the distributed link. Keep internal navigation links free of acquisition UTMs; our internal linking guide covers connecting useful pages.
- Redirects. Compare the original link, each redirect destination and the landing URL. Check shorteners, tracking wrappers, domain redirects and URL-cleaning scripts. A parameter disappearing at a particular hop gives you a concrete redirect rule to fix. A final URL that retains the tags passes this check, but does not prove Analytics collected them.
- Tracking on landing pages. With consent granted in your test, inspect the first page a visitor reaches, including alternate templates and mobile pages. Use DebugView to check that a page view reaches the intended property with the correct page location. A missing event or wrong measurement ID points to a collection problem. If tracking begins only on a later page, the original campaign information may be unavailable. Missing tracking can also mean missing visits, not simply more direct visits.
- Consent behavior. Test the initial state, rejection, acceptance and later changes using your own test sessions. For consent-mode implementations, Tag Assistant shows defaults and consent updates. Check whether the banner’s choice reaches the tag and whether the landing context is still available when collection is permitted. A mismatch suggests an implementation defect; correctly withheld collection is an expected privacy outcome. Preserve visitors’ choices. Do not bypass consent or assume every declined visit becomes direct.
- Relevant cross-domain setup. If the journey crosses domains you manage, such as a separate checkout, check the configured domains and that their tags use the same web stream’s G- ID. Follow a real link or form and inspect whether the
_gllinker parameter survives redirects. Missing linker data or self-referrals warrant investigation of session continuity. Follow Google’s cross-domain instructions; this configuration does not recover an unknown external source and is unnecessary for a journey that stays on one domain.
Use patterns to choose the next test
Filter to (direct) / (none) and compare complete reporting periods. Look at both session counts and share: the share can increase simply because another channel declined. Do not assume a general industry growth rate explains your site.
- Deep landing pages: prioritize the links and templates leading there. Long URLs can still be bookmarked or shared.
- New users: inspect collection and identity continuity. A reported new user is not proof of a stripped referrer.
- Devices: reproduce the journey on the affected device or browser. Mobile traffic alone does not identify a messaging app.
- Timing: compare changes with email sends, releases and consent-banner updates. Coincidence helps choose a test, not establish a cause.
After a fix, repeat the known-link test and annotate your report. Review comparable periods alongside visits and sign-ups, allowing for consent and processing limits. Better labeling helps future analysis; it does not reconstruct unknown historical sources.
If the next step is publishing useful content consistently, see how Serpio’s article workflow works. Use a defined reader question and a measurable next action, then evaluate the results without promising a particular traffic source.



