// AI ATTRIBUTION / GA4 AI CHANNEL
Why GA4's AI Channel Still Undercounts
On May 13, 2026, Google gave every GA4 property a button that says "this was AI." I spent an afternoon checking what the button actually sees, against Google's own documentation rather than the recap posts.
The short version: the channel is real, it works as described, and it is still a floor. Three structural holes in how it is built mean the number it shows you is never the number you are actually trying to measure. None of the three are secret. Google discloses two of them in its own support pages. The third you have to go looking for.
What actually shipped
Google's own "What's New" documentation confirms the mechanism plainly: when a session's referrer matches a recognized AI assistant domain, GA4 automatically sets the medium dimension to "ai-assistant" and groups the session under a new AI Assistant channel inside your Default Channel Group reports. No configuration, no custom regex, no tagging work. It shipped on, requiring nothing from the property owner, with broad availability by early June.
That is a genuine improvement over the prior state, where every AI-referred visit landed in Referral indistinguishable from a stray backlink. The channel does exactly what Google says it does. The problem is what it was never built to do.
Hole one: it only sees traffic that still identifies itself
The mechanism is referrer matching. No referrer, no match, no classification. That is not a bug in the implementation, it is the entire design, and it means the channel is structurally blind to any visit that arrives with nothing in the header to read. How large that referrerless share actually is, the industry's estimates run from 15 percent to 70 percent depending on whose undisclosed method you trust, is a separate and messier question I take apart fully in the companion piece on dark AI traffic. What matters here is narrower and not in dispute: whatever that share turns out to be, the AI Assistant channel cannot see any of it, by construction. A channel report showing your AI traffic at some tidy percentage is showing you the part of the iceberg that happened to keep its referrer.
Hole two: it is forward-only, and your history just split in half
GA4 processes data forward only. There is no retroactive reclassification, none, so every session before the rollout keeps whatever label it originally got, usually Direct or Referral, permanently. If you did not manually annotate May 13 as a change-of-measurement date in your own reporting, you now have a trend line that silently splices two different instruments together at the seam.
This is the hole nobody frames correctly. It reads like a minor caveat, "the data doesn't go back further," the kind of line every product launch carries. It is actually a measurement discontinuity. A year-over-year AI-traffic comparison that crosses the May 13 boundary is not comparing more AI traffic to less. It is comparing a period where AI traffic was invisible to a period where some of it suddenly became visible, and attributing the entire jump to growth. Any board deck built on that comparison without the annotation is telling a growth story that is partly a measurement story wearing a growth story's clothes.
Hole three: Google's own AI traffic doesn't count as AI
This is the one that took actual digging, because Google does not frame it as a limitation anywhere in the launch materials. A click on a Google AI Overview or AI Mode result carries the exact same referrer as a click on a standard blue link: google.com/search. There is no separate parameter, no distinguishing string, nothing in the HTTP header that tells GA4 which layout produced the click. GA4 classifies both identically: source google, medium organic, channel Organic Search.
AI Overviews and AI Mode results now appear across a large share of Google searches, trackers disagree on exactly how large and disagree even more once you narrow to commercial intent specifically, but nobody disputes the volume is real and growing. Whatever the precise share turns out to be, none of that traffic shows up in the channel Google built to show you AI traffic. It shows up in the same Organic Search bucket it always did, indistinguishable from a decade-old blue-link click, which means the channel that is supposed to answer "how much of my traffic is AI" is structurally blind to a piece of it that Google itself controls.
The referrer-carrying list isn't even stable
Set aside the referrerless majority and Google's own AI surfaces. Even the easy half, the traffic that does still carry a matchable referrer, is not a fixed target. Google's May 13 launch announcement named three platforms by name: ChatGPT, Gemini, and Claude. The live Default Channel Group documentation today lists five: ChatGPT, Gemini, DeepSeek, Copilot, and Grok. Claude, named at launch, does not appear in the current published definition. Perplexity has never appeared in it at any point.
If you screenshotted the channel's platform list in May and are comparing it to a report you pulled this month, you may not be measuring the same thing twice. A property that gets meaningful Claude traffic and hard-coded "ChatGPT, Gemini, Claude" into a client dashboard back in May is currently underreporting a platform it thinks it is tracking, silently, with no error and no warning.
What I run alongside it
None of this is a reason to ignore the native channel. It costs nothing, it is directionally correct, and it is a real improvement over Referral soup. What it is not is sufficient on its own, so I run three things next to it rather than instead of it. A custom channel group that explicitly re-includes Claude and Perplexity by referrer domain match, since the native definition currently drops one and has never carried the other. A dated annotation on every dashboard marking May 13, 2026 as a measurement boundary, so nobody downstream mistakes a visibility jump for a growth story. And a separate, session-independent report matching server logs against each AI company's published bot signatures, refreshed on a schedule, which tells me when a crawler visited without pretending that crawl was a click, a distinction the companion piece covers in full.
The native channel answers "did a labeled AI assistant send this session." That is a real and useful question. It is not the same question as "how much of my demand is AI-influenced," and treating the first answer as the second is how a marketing team ends up defending a budget line with a number that was never built to carry that weight. Getting AI turned into money starts with knowing exactly what your instruments can and cannot see, which is the same discipline underneath AI Commercialization: the complete guide.
Frequently asked questions
Does GA4's AI Assistant channel track all AI traffic?
No. It only classifies sessions where the referrer still matches a recognized AI assistant domain. It cannot see a visit that arrives with no referrer at all, which by every method used to estimate it is the majority. The channel measures a floor, not the total.
Why does GA4 show Google AI Overview clicks as Organic Search?
Because the click carries the same referrer as a normal blue-link result, google.com/search, with nothing in the header to distinguish an AI Overview or AI Mode click from a standard result. GA4 has no signal to work with, so it classifies both identically as source google, medium organic. Google's own AI surfaces are invisible in the channel Google itself built, a real gap regardless of exactly how their volume compares to ChatGPT or Gemini.
Does GA4's AI Assistant channel work retroactively?
No. GA4 processes data forward only. Sessions before the channel's rollout keep their original classification, almost always Direct or Referral, permanently. Any business that did not manually annotate the May 13, 2026 launch date now has a before-and-after comparison that mixes two different measurement regimes.
Which AI platforms does GA4's AI Assistant channel track?
As of the live Default Channel Group definition: ChatGPT, Gemini, DeepSeek, Copilot, and Grok. That list is not the one Google announced at launch. The May 13, 2026 announcement named ChatGPT, Gemini, and Claude specifically. Claude no longer appears in the published definition, and Perplexity has never been included at any point.
Is Claude tracked by GA4's AI Assistant channel?
Not in the current published definition, despite being one of three assistants named in Google's own launch announcement. Any report built off the original announcement rather than the live documentation is already out of date.
How do I track Perplexity traffic in GA4?
Not through the native AI Assistant channel, which has never included it. A custom channel group matching Perplexity's referrer domains directly is the only way to see it as its own category rather than folded into Referral.
Sources
Channel launch and mechanism: Google Analytics Help, "What's New in Google Analytics" (accessed August 2026; official documentation, May 13, 2026 entry). The Google AI Overview and AI Mode referrer mechanics: Ludde Nystrom, Nice Looking Data, "AI Traffic in GA4" (July 10, 2026). The platform-list comparison between the May 13 launch announcement and the live Default Channel Group definition: Digital Applied, "GA4's New AI Assistant Channel" (June 11, 2026). AI Overview prevalence on commercial search queries and the forward-only processing behavior are drawn from Google's own published Analytics documentation, checked August 2026.
About the author
Jeff Brokaw is a sitting CMO and Certified Chief AI Officer who ships AI in production, not slideware. He runs company-level visitor identification on his own properties and built the precision-measurement layer the category doesn't sell, plus answer-engine optimization that produces measurable pipeline. He has been building AI systems commercially since 2016. He built the engine behind $185M in new business for a defense manufacturer, and authored the go-to-market behind a $114M institutional raise that came together in under 30 days.