Your search traffic is flat. Your Direct traffic is climbing, and somebody in the meeting has already floated a theory: maybe it’s Google’s AI answers. Nobody assigned you to verify that theory, and GA4 doesn’t flag a channel definition changing under your feet. Here’s the check, run directly against Google’s own documentation and verified as of 2026-08-18.
Does Google AI Mode Send a Referrer?
No, not into the channel built to catch it. GA4’s AI Assistant group, which Google shipped on 2026-05-13, matches referrer and medium patterns from ChatGPT, Gemini, Deepseek, Copilot and Grok. Google’s own documentation states plainly that the channel “excludes Google’s AI Overviews and AI Mode,” verified live on 2026-08-18.[1]
That’s worth sitting with, because it corrects a common assumption. GA4 does have native handling for AI-assistant traffic now, five named assistants, matched without any configuration. Google’s own release notes for the same launch name a different roster, ChatGPT, Gemini and Claude[4], so Claude’s status is genuinely unsettled and Perplexity is absent from both pages. Google’s own AI surfaces are the one exception, carved out by design rather than left out by oversight.
So where do AI Mode and AI Overviews clicks land instead? Under Organic Search, the same channel a plain blue-link result lands in. The same Google page states that Organic Search covers arrivals via “non-ad links in organic-search results, including Google’s AI Overviews and AI Mode.”[1] It isn’t hidden. It’s classified alongside the rest of Google’s own search surface, on purpose, and that fact alone reframes what “AI traffic in Direct” actually means for a Google-heavy site.
Two things stay genuinely unverified here, and it’s more useful to say so than to guess. Google hasn’t published the literal referrer header an AI Mode click sends, so the classification above tells you where GA4 puts the traffic, not exactly what triggers it. And Google’s own Search Central documentation on AI features says nothing about referrer or analytics behavior at all.[2] Neither gap has a primary source closing it as of 2026-08-18, and this post won’t pretend otherwise.
How to Check What Your Own Property Sees
The only number that matters is the one in your own property, and finding it takes about 10 minutes. Open GA4’s Traffic Acquisition report, filter Session default channel group to AI Assistant, and you’ll see ChatGPT, Gemini, Deepseek, Copilot or Grok sessions, matched natively since 2026-05-13. You won’t see AI Mode there, and that’s expected, not a bug.
For the exact filter, GA4’s matching rule is narrower than most people assume. AI Assistant requires the session medium to exactly equal “ai-assistant,” applied only against the five named referrers.[1] Direct is defined just as narrowly: source exactly matches “(direct)” and medium is one of “(not set)” or “(none).”
| GA4 channel | Field-match rule (Google’s own definition) |
|---|---|
| AI Assistant | Medium exactly matches “ai-assistant,” auto-applied for the five named referrers |
| Direct | Source exactly matches “(direct)” and Medium is “(not set)” or “(none)” |
That distinction matters for diagnosis. A session with an unrecognized but non-empty referrer typically falls into Organic Search or an Unassigned bucket, not Direct. So if your Direct number specifically is what’s climbing, an AI-driven session with the referrer stripped entirely, most often by a mobile app’s in-app browser, is a more likely cause than a normal desktop or mobile-web AI Mode click, which should already be counted under Organic Search. This diagnostic sits alongside the broader setup covered in the wider AI-referral tracking setup and the fuller account of why AI traffic still shows up as Direct, and it’s worth running before assuming your custom channel group needs a rebuild.
Why the Answer May Change
This is live behavior, not a published specification, so treat everything above as dated rather than permanent. Google added the AI Assistant channel on 2026-05-13 with no changelog promising it stays fixed, and browser referrer defaults are documented to change independently of anything Google controls.[3] Revisit this check on a schedule, not once and never again.
Two blind spots are worth naming precisely, because “the referrer is missing” hides two different failures. First, mobile apps with an embedded in-app browser can strip a referrer entirely regardless of the surface that sent the click, which is the same first-party signal loss covered in the click-ID mechanics behind the same first-party signal loss on the paid side. Second, and more fundamental: a zero-click citation, where an assistant answers the question without the reader ever visiting your site, never generates a session at all. No analytics tool sees it, because there’s nothing to see. That gap isn’t a GA4 limitation. It’s outside what any web analytics platform measures.
What to Do With the Answer Either Way
If your Direct traffic climbed and your Organic Search didn’t move with it, the honest sentence to bring to the meeting is that Google’s own AI surfaces report under Organic Search by design. A Direct spike is more likely from an app-embedded browser stripping the referrer, or from an assistant GA4 doesn’t natively match, than from AI Mode itself.
If Organic Search climbed with no matching keyword-level story in Search Console, that’s consistent with AI Mode traffic landing exactly where Google built it to land. If you have not yet built the custom channel group for the assistants GA4 does not match natively, setting up GA4 to recognize AI assistant traffic is the configuration step that comes first. Either way, name the pattern precisely rather than reaching for a percentage nobody has verified, and treat this check as one input into the Analytics Trust Gap rather than the whole explanation for it.
Sources
- Google Analytics Help, Default Channel Group Definitions – No visible revision date on the page itself; verified live 2026-08-18. States the AI Assistant channel groups traffic from ChatGPT, Gemini, Deepseek, Copilot and Grok and explicitly “excludes Google’s AI Overviews and AI Mode.” States Organic Search “includes Google’s AI Overviews and AI Mode” alongside standard non-ad search results. Also defines the exact field-match rule: AI Assistant requires medium exactly “ai-assistant”; Direct requires source exactly “(direct)” and medium “(not set)” or “(none).” ↩
- Google Search Central, AI Features and Your Website – Page states a last-updated date of 2025-12-10 UTC; re-verified live 2026-08-18. Confirms sites appearing in AI Overviews and AI Mode are included in Search Console’s overall search traffic, and that AI Overview clicks run “higher quality” by time-on-site. States nothing about referrer-header behavior for outbound clicks. ↩
- MDN Web Docs, HTTP Referrer-Policy Header – Last modified 2026-08-07. Documents the strict-origin-when-cross-origin default: a cross-origin request at the same security level sends only the origin, and an HTTPS-to-HTTP downgrade sends no referrer at all. General browser mechanism, not specific to Google AI Mode. ↩
- Google Analytics Help, What’s New in Google Analytics – Verified live 2026-08-18. The May 13, 2026 release-note entry announcing the AI Assistant channel names ChatGPT, Gemini and Claude as covered chatbots, a different roster than the channel-definition page, which names Deepseek, Copilot and Grok and does not name Claude; neither page names Perplexity. ↩
Seeing these patterns at your company?
Book a free WebOps Diagnostic. I'll review your site before the call and share specific observations.
Book a Free Call →Frequently Asked Questions
No. ChatGPT lands in GA4's AI Assistant channel, shipped 2026-05-13, alongside Gemini, Deepseek, Copilot and Grok. Google's AI Mode and AI Overviews are explicitly excluded from that channel and classified under Organic Search instead, per Google's own default channel group documentation, verified 2026-08-18.
Google hasn't published a reason. Its documentation states only that AI Assistant excludes Google's AI Overviews and AI Mode, and that both count under Organic Search instead, the same bucket as a standard search result. One plausible mechanism: an AI Mode click and a normal result click send the same google.com referrer, leaving GA4 no header difference to key a separate rule on.
Not reliably today. A custom rule needs a distinguishing referrer or campaign pattern, and Google hasn't published one that separates an AI Mode click from a normal organic result click. Both currently classify the same way in GA4, under Organic Search, with no documented signal to split them apart.
Partly. It solves the piece where ChatGPT, Gemini, Deepseek, Copilot or Grok send a recognizable referrer. It does nothing for Perplexity, absent from both of Google's pages on the feature, for mobile in-app browsers that strip referrers entirely, or for zero-click citations that never generate a session at all. Claude's status is genuinely unsettled: Google's own release notes for this feature do name it, the definitions page does not.
Not in GA4's native AI Assistant channel. Google's documentation names ChatGPT, Gemini, Deepseek, Copilot and Grok as the matched referrers; Perplexity and Claude.ai are absent from that list. Google's own release notes for the same feature do name Claude, so its status is genuinely unsettled; Perplexity is absent from both pages. Traffic from those two still depends on whether their referrer survives the click, and if it doesn't, it lands in Direct.
