GA4’s AI Assistant Channel Undercounts Your AI Traffic: How To Build One That Doesn’t

I was digging done a Google Analytics 4 relationship recently, collapsed the postulation down by root and medium, and saw thing that made maine extremity scrolling. The aforesaid source, chatgpt.com, was sitting successful 3 different channels astatine once. Not 3 different sources. One source, scattered crossed 3 channels, successful the aforesaid report. If you’ve sewage GA4’s caller AI Assistant channel, there’s a bully chance the nonstop aforesaid point is happening successful your information correct now. And it intends the AI postulation number you’re reporting is almost surely wrong.

AI postulation is still a mini slice for astir sites, but it converts good supra its weight: Similarweb’s clickstream data has ChatGPT referrals converting astatine astir 7%, up of integrated hunt and not acold down paid. A high-intent transmission that mini is worthy measuring decently alternatively than eyeballing it. Let maine show you why it fragments, and really to hole it.

So What Did Google Actually Change?

On May 13, 2026, Google added a autochthonal AI Assistant transmission to GA4’s Default Channel Group. The thought is simple. When GA4 spots a referrer it recognizes arsenic an AI assistant, it tags the convention pinch the mean ai-assistant, drops it into the AI Assistant channel, and stamps the run arsenic (ai-assistant). No setup, nary regex, thing for you to build. It rolled retired gradually and reached astir properties by early June 2026.

If you spent the past twelvemonth stitching together civilization regex conscionable to spot your AI traffic, that’s a genuine win. Before this, those visits sat successful Referral, aliases successful Direct erstwhile the referrer was missing.

But here’s the catch, and it’s hiding successful the connection “recognizes.” The database of platforms Google recognizes keeps moving. At launch, it named ChatGPT, Gemini, and Claude. By June, the unrecorded archiving listed a different group (ChatGPT, Gemini, DeepSeek, Copilot, and Grok), pinch Claude softly dropped. Perplexity, 1 of the highest-intent AI sources going, still isn’t connected the database and keeps landing successful Referral. So don’t hard-code a level database into a customer report. Check Google’s transmission definitions connected the time you publish, because they change.

1 Source, 3 Channels: The Problem Hiding In Your Reports

Back to that screenshot. The logic a azygous root splits crossed 3 channels is that GA4 decides the transmission utilizing root and mean together, not root connected its own. Add Session source/medium arsenic a dimension, and you tin watch chatgpt.com break into three:

• chatgpt.com / ai-assistant lands successful AI Assistant. This is the portion GA4 recognized and tagged.
• chatgpt.com / referral lands successful Referral. These are the sessions GA4 didn’t tag, positive thing that arrived earlier the transmission switched connected for your spot (remember, the rollout dragged into June).
• chatgpt.com / (not set) lands successful Unassigned, the transmission almost cipher ever opens. Google’s ain norm is blunt here: erstwhile source/medium comes done arsenic (not set), there’s no transmission norm to drawback it, truthful it falls into Unassigned.

Image from author, June 2026

Why would a root you intelligibly admit move up pinch nary medium? In my acquisition it’s usually the ChatGPT app and its in-app browser. As MarTech has documented, links opened wrong those embedded browsers thin to portion the referrer, truthful GA4 hangs connected to the root but loses the medium.

So your existent ChatGPT number isn’t successful 1 place. It’s smeared crossed 3 channels, and 1 of them is simply a bucket you astir apt ne'er check. Read the AI Assistant transmission connected its own, and you’ll undercount each azygous time.

Why The Obvious Fixes Don’t Work

There are 3 instinctive fixes here, and I wouldn’t thin connected immoderate of them:

• Just publication the AI Assistant channel. It misses the Referral and Unassigned slices of the very aforesaid traffic, and it ignores Perplexity completely.
• Compare this period to last. The autochthonal transmission only counts guardant from the rollout date, and it switched connected astatine different times for different properties. So immoderate scope reaching backmost into outpouring 2026 is comparing tagged postulation against untagged traffic. That’s not a trend; it’s an artifact.
• Check your rank tracking. Different mobility entirely. Rankings show you astir position, not whether an adjunct really sent personification to your site.

The Fix: 1 Custom Channel That Matches On Source

Here’s the move that really solves it. Build a civilization transmission group and lucifer for root while ignoring mean completely. The 2nd you do that, the ai-assistant, referral and (not set) versions of chatgpt.com illness into a azygous line.

You get 2 bonuses connected top. A civilization transmission group applies its rules retroactively crossed your full day range, truthful it rescues each those aged ChatGPT sessions stuck successful Referral. And because you’re penning the rule, you tin see the platforms Google leaves out, Perplexity included.

Here’s really I group it up:

1. Go to Admin > Data show > Channel groups and create a caller group.

Image from author, June 2026

2. Add a transmission and telephone it AI.

Image from author, June 2026

3. Set the information to Source matches regex, pinch a shape covering the AI domains.

Image from author, June 2026

4. Drag the AI transmission supra Referral and Organic, truthful it claims those sessions first.

5. Save, past use the group arsenic your superior magnitude successful immoderate acquisition report.

The regex is wherever you tin softly sabotage yourself, truthful build it carefully. Keep entries tied to recognizable domains aliases service-specific big tokens. Never propulsion successful a bare token for illustration gpt connected its own, because it’ll lucifer immoderate root that happens to incorporate those 3 letters and resistance successful mendacious positives, which is precisely the benignant of point that gets your information picked apart. Here’s a boundary-aware shape covering the awesome AI sources you’d want to track:

Two speedy notes connected that. gemini.google.com is simply a circumstantial host, truthful it won’t hoover up each your Google organic, which is precisely why you must ne'er adhd a bare google to the list. And dainty the shape arsenic perishable. I’d reappraisal it each quarter, because platforms travel and spell and their domains whitethorn change.

The Bit Even A Perfect Channel Can’t Fix

This is the portion astir guides skip, and it’s the portion that keeps you honest. A civilization transmission group fixes really postulation is classified, not whether it gets collected successful the first place. A root norm tin only drawback sessions that showed up pinch a root it tin really read.

The biggest unsighted spot is AI postulation pinch nary referrer astatine all, which lands successful Direct. Most of that comes from the AI mobile apps and in-app browsers, which walk thing for GA4 to read, truthful there’s nary root to lucifer on.

On apical of that, Google’s ain AI Overviews and AI Mode get counted arsenic Organic Search (google / organic), and Google deliberately keeps them retired of the AI Assistant channel. For a batch of sites, that’s the azygous biggest AI aboveground location is, and it’s invisible arsenic “AI” successful your reports. Don’t effort to resistance it into your AI transmission either, aliases you’ll swallow up mean Google integrated by accident.

So, beryllium precise astir what you’re claiming. With this civilization transmission successful place, you’ve sewage a complete and accordant number for the AI sources you tin really identify. What you haven’t sewage is simply a measurement of full AI influence. Whether an adjunct recommended you to personification who ne'er clicked is simply a wholly different problem, and nary transmission group is going to lick it.

What I’d Do This Week

Treat the autochthonal AI Assistant transmission arsenic a starting point, not the vanished product. Then:

• Add Session source/medium to a Traffic acquisition study and spell looking for your AI domains dispersed crossed AI Assistant, Referral, and Unassigned. Honestly, seeing the divided for yourself is half the lesson.
• Build the source-based AI civilization transmission group to propulsion the fragments backmost together and retrieve the history the autochthonal transmission near behind.
• Write down a monthly baseline. With a moving level database and a large acheronian portion you can’t see, the month-on-month inclination will show you acold much than immoderate azygous header figure.

Google yet putting AI postulation connected the dashboard is simply a existent measurement forward. Just retrieve that the default position hands you the easy slice. The existent activity now is knowing precisely which slices it’s softly leaving out.

More Resources:

• Your AI Visibility Tracker Is Quietly Breaking Your Analytics And Your Strategy
• Google’s Quality Threshold Is Quietly Killing Scaled AI Content At Ranking
• Ask An SEO: Why Is GA Reporting Higher Organic Traffic Than GSC?

Featured Image: Roman Samborskyi/Shutterstock