I was digging through a Google Analytics 4 account recently, broke the traffic down by source and medium, and saw something that made me stop scrolling. The same source, chatgpt.com, was sitting in three different channels at once. Not three different sources. One source, scattered across three channels, in the same report. If you’ve got GA4’s new AI Assistant channel, there’s a good chance the exact same thing is happening in your data right now. And it means the AI traffic number you’re reporting is almost certainly wrong.
AI traffic is still a small slice for most sites, but it converts well above its weight: Similarweb’s clickstream data has ChatGPT referrals converting at around 7%, ahead of organic search and not far behind paid. A high-intent channel that small is worth measuring properly rather than eyeballing it. Let me show you why it fragments, and how to fix it.
So What Did Google Actually Change?
On May 13, 2026, Google added a native AI Assistant channel to GA4’s Default Channel Group. The idea is simple. When GA4 spots a referrer it recognizes as an AI assistant, it tags the session with the medium ai-assistant, drops it into the AI Assistant channel, and stamps the campaign as (ai-assistant). No setup, no regex, nothing for you to build. It rolled out gradually and reached most properties by early June 2026.
If you spent the last year stitching together custom regex just to see your AI traffic, that’s a genuine win. Before this, those visits sat in Referral, or in Direct when the referrer was missing.
But here’s the catch, and it’s hiding in the word “recognizes.” The list of platforms Google recognizes keeps moving. At launch, it named ChatGPT, Gemini, and Claude. By June, the live documentation listed a different set (ChatGPT, Gemini, DeepSeek, Copilot, and Grok), with Claude quietly dropped. Perplexity, one of the highest-intent AI sources going, still isn’t on the list and keeps landing in Referral. So don’t hard-code a platform list into a client report. Check Google’s channel definitions on the day you publish, because they change.
1 Source, 3 Channels: The Problem Hiding In Your Reports
Back to that screenshot. The reason a single source splits across three channels is that GA4 decides the channel using source and medium together, not source on its own. Add Session source/medium as a dimension, and you can watch chatgpt.com break into three:
chatgpt.com / ai-assistantlands in AI Assistant. This is the slice GA4 recognized and tagged.chatgpt.com / referrallands in Referral. These are the sessions GA4 didn’t tag, plus anything that arrived before the channel switched on for your property (remember, the rollout dragged into June).chatgpt.com / (not set)lands in Unassigned, the channel almost nobody ever opens. Google’s own rule is blunt here: when source/medium comes through as (not set), there’s no channel rule to catch it, so it falls into Unassigned.
Source link
Disclaimer
We strive to uphold the highest ethical standards in all of our reporting and coverage. We blogs.grocliq.com want to be transparent with our readers about any potential conflicts of interest that may arise in our work. It’s possible that some of the investors we feature may have connections to other businesses, including competitors or companies we write about. However, we want to assure our readers that this will not have any impact on the integrity or impartiality of our reporting. We are committed to delivering accurate, unbiased news and information to our audience, and we will continue to uphold our ethics and principles in all of our work. Thank you for your trust and support.
Website Upgradation is going on for any glitch kindly connect at [email protected]
