Full disclosure: This post contains affiliate links. If you make a purchase through these links, 99signals may earn a commission at no additional cost to you.
For the past two years, every visit your site received from ChatGPT, Gemini, or Claude either showed up as generic referral traffic or, worse, as direct traffic if the referrer header got stripped.
That changed on May 13, 2026.
Google pushed a native “AI Assistant” channel into GA4’s Default Channel Group. No custom regex. No manual configuration. AI referral traffic now gets its own row in your acquisition reports, sitting alongside Organic Search, Paid Search, Direct, Referral, and the rest.
The plumbing question is settled. The strategic question is just beginning.
Table of Contents
What Actually Changed in GA4
The update is mechanically simple. It modifies three traffic source dimensions at once, all automatically.
When Google Analytics detects a referrer matching a recognized AI assistant, three things happen simultaneously.
Medium gets assigned the value ai-assistant.
Channel Group routes the session into a new “AI Assistant” channel inside the Default Channel Group.
Campaign receives the reserved label (ai-assistant).
You don’t have to do anything. The classification kicks in automatically across Traffic Acquisition reports, User Acquisition reports, and any channel-based exploration.
Google’s official “What’s New” entry covers ChatGPT, Gemini, and Claude as the primary recognized assistants, with the list likely to expand as Google updates its internal referrer mapping.
The Real Story Behind GA4’s AI Assistant Channel
On the surface, this is a quality-of-life update for analytics teams that were tired of writing regex rules to identify AI referrers.
But the real story isn’t the feature. It’s what the feature signals.
Google is formally acknowledging that AI assistants are a meaningful acquisition channel, distinct from organic search, paid, social, and referral. They’ve earned their own row in the default reporting interface that most marketing teams look at first.
That’s a positioning decision, not just a technical one.
For two decades, the default channel group has been the foundation of how marketers think about traffic sources. Organic Search. Paid Search. Direct. Referral. Adding “AI Assistant” to that list says something specific: this is no longer a fringe channel you need to track with custom configuration. It’s table stakes.
The data itself isn’t new. Marketers who built custom channel groups with regex patterns have been seeing some version of this traffic for over a year. What changed is who can see it. Every CMO, founder, and VP of marketing pulling up GA4 next month will see AI traffic as a distinct line item without having to ask their analyst to build a custom report.
That visibility shift is the real story. Once it’s in the default report, it’s in the boardroom conversation.
The Three Things GA4 Still Can’t Tell You
Here’s where the marketing coverage of this update tends to oversell what changed.
GA4 now tells you that AI traffic exists on your site. It does not tell you anything about the quality, source-level competitive landscape, or upstream signals that produced that traffic.
It can’t tell you which queries triggered your citations. When someone arrives from ChatGPT, you see the visit. You don’t see the prompt. You don’t see whether you were cited as the primary recommendation, mentioned in passing, or surfaced as one of five options. The post-click data is rich. The pre-click context is invisible.
It can’t show you competitive AI visibility. GA4 is a site-level tool. It measures what happens on your domain. It has no way to tell you how your AI visibility compares to competitors, which platforms are sending traffic to others in your category, or whether your AI share of voice is growing or declining relative to the market.
It can’t catch the traffic that isn’t getting through. A meaningful portion of AI referrals arrive without a referrer header, especially from mobile apps. Native iOS and Android chatbot apps often strip referrer data entirely, which means those sessions still land in Direct traffic, invisible to the new channel. If your AI Assistant channel shows zero traffic, that’s not necessarily because no one is visiting you from AI. It might mean they’re arriving in a way GA4 can’t detect.
This is why the GA4 update is a measurement floor, not a measurement ceiling.
Five Steps to Get the Most Out of GA4’s AI Assistant Channel
The temptation with any new analytics feature is to spend a week exploring the dashboard and call it a strategy.
Skip that approach.
Here’s what’s worth doing now, in order of priority.
1. Check whether the channel is populating
The rollout is gradual. Open Reports > Acquisition > Traffic Acquisition, filter by Session Default Channel Group, and look for “AI Assistant.” If you see it, note your current baseline numbers. That’s your benchmark going forward.
2. Audit your AI crawler access
If AI bots can’t crawl your site, they can’t cite it, and your AI Assistant channel will reflect that gap. Check whether your robots.txt or your CDN/WAF is blocking ChatGPT-User, OAI-SearchBot, Perplexity-User, or Claude-SearchBot. This is the silent killer of AI visibility, and most teams don’t realize they’re blocking the bots that decide whether they get cited.
3. Set up tracking for the gap GA4 can’t cover
GA4 tells you what happened after the click. To understand what’s driving (or preventing) those clicks, you need pre-click visibility into how AI platforms are citing you, who’s getting cited instead, and which queries are triggering your appearance.
This is where I’d point you to Semrush One. Their AI Traffic dashboard tracks visibility trends across ChatGPT, Perplexity, Google AI Mode, Claude, and Bing in a single view, the Citations tool shows which of your URLs are getting cited and which queries are surfacing them, and the Site Audit flags whether your technical setup is quietly blocking AI crawlers.
The combination matters because GA4 alone gives you a partial picture.
Semrush offers a free 7-day trial on
4. Don’t delete your custom channel groups yet
If you built a custom AI traffic channel group before this update, keep it running for now. Google’s internal list of recognized AI referrers may not catch niche tools, and your custom regex might capture sources the default channel misses. Run both side by side until you’re confident the default channel is comprehensive.
5. Review your existing segments and filters
Any segment built around the medium dimension may now implicitly include or exclude AI traffic in unexpected ways. A filter like “medium does not contain cpc” will now also exclude AI Assistant sessions. Audit your existing analytics setup before assuming the new channel just slots in cleanly.
The Bigger Signal
Strip away the technical details and what Google is really saying with this update is: AI is now a permanent channel, not an emerging one.
You can track it in the same reports you’ve been using for fifteen years. It shows up next to Organic Search. The bar for measuring it just dropped to zero.
That’s a meaningful shift, but it’s also a clarifying one. The marketers who’ve been waiting for “official” recognition of AI traffic before investing in the channel just got it. The ones who’ve been building AI visibility strategies for the past year just got their work validated in the default dashboard.
The next question isn’t whether AI is a real channel. Google’s classification answers that.
The next question is what you’re actually doing to grow your presence inside it.
Related Articles