Key Takeaways
- On 13 May 2026, Google added a built-in AI Assistant channel group to GA4, auto-populating three session dimensions with no setup required.
- Previously, capturing this traffic required a custom channel group with a maintained regex, using one of only two available custom slots in the property.
- The channel captures sessions that arrive with a referrer header. Industry analysis suggests 60 to 80 percent of AI-originated visits include one; the rest land in Direct.
- Google has not confirmed the full list of recognised AI referrers, retroactive data reclassification, or how the medium propagates to linked Google Ads accounts.
- Treat the AI Assistant channel as a partial baseline. If a custom channel group is already running, keep it active for 30 days to compare coverage.
What Changed on 13 May 2026
On 13 May 2026, Google updated the Default Channel Group definitions in GA4 to include a new built-in group: AI Assistant. The update is automatic. No configuration is required.
When traffic arrives from a recognised AI assistant referrer, GA4 now auto-populates three session dimensions. The medium becomes ‘ai-assistant’. The Channel Group becomes ‘AI Assistant’.
The Campaign field receives the reserved label ‘(ai-assistant)’. The data flows directly into standard Acquisition reports, sitting alongside Organic Search, Paid Search, Referral, and Direct.
For context, capturing this category of traffic previously required building a custom channel group with a manually maintained regex pattern. Google published guidance for that regex in August 2025. Nine months later, they’ve absorbed the same logic into the default setup.
That timeline is worth noting. GA4’s product team doesn’t update default channel definitions frequently. For Google to move AI assistant traffic from a custom workaround into the standard taxonomy, the volume of that traffic must have crossed an internal threshold of significance.
Why This Matters: The End of the Workaround
The custom channel group solution worked, but it created friction that most clients couldn’t manage on their own.
Editor access to a GA4 property is not something most business owners hold or maintain. Many agencies manage this access on behalf of clients, which created a dependency: a client wanting to see AI traffic data couldn’t pull it from their own reports without involving their agency first.
The regex also had a limited lifespan. As new AI platforms emerged, the pattern needed updating. Left unchanged, it would quietly miss newer referrers. And the maintenance burden fell entirely on whoever managed the property.
There was also a structural constraint specific to GA4. Each property allows a maximum of two custom channel groups. An agency working with a client that had multiple attribution needs, perhaps one custom group for affiliate traffic and another for AI sources, was consuming both available slots before covering anything else.
The new default removes all of this. The AI Assistant channel appears automatically in every GA4 property, globally. No regex, no access requirements, no slot consumption.
For clients who never had the custom group running, this is the first time AI assistant traffic will appear as a distinct acquisition source, rather than being folded silently into Referral or Direct.
The Limitation Worth Understanding: Referrers and the Floor Problem
This is the part most coverage of this update overlooks.
The AI Assistant channel works by reading the referrer header: a value sent by the user’s browser when they click a link. When someone reads an answer in ChatGPT, clicks a cited source, and lands on your site, the browser typically sends a referrer header identifying chatgpt.com as the origin.
GA4 reads that header, matches it against recognised AI assistant domains, and assigns the session to the AI Assistant channel.
The problem is that referrer headers are not always sent.
Industry analysis suggests roughly 60 to 80 percent of AI-originated visits arrive with a clean referrer header intact. The remaining 20 to 40 percent of land is direct traffic, indistinguishable in GA4 from a user who typed your URL into the address bar.
Several common scenarios cause the referrer to be stripped or absent:
Traffic from native mobile apps
When someone uses ChatGPT or Claude through the native iOS or Android application rather than a mobile browser, the referrer is often stripped at the operating system level. GA4 never sees where the visit originated.
In-app browsers
Many users access AI tools through in-app browsers inside other applications. These environments frequently suppress referrer data as a privacy measure.
Copy and paste behaviour
An AI assistant provides a link. The user copies the URL and pastes it into the browser’s address bar rather than clicking directly. No referrer is generated. The visit registers as Direct.
Influence without a click
Perhaps the most significant gap. A user asks an AI model about a product or service category. The model mentions your brand. The user doesn’t click through; they close the conversation and run a branded search instead. The visit appears under Organic Search, with no visible connection to the AI interaction that prompted it.
The practical implication: the AI Assistant channel captures the floor of AI-driven traffic, not the ceiling. Whatever volume appears in your GA4 AI Assistant report, the actual influence of AI assistants on your traffic is likely higher. How much higher depends on your audience’s device habits and how they typically interact with AI tools.
This isn’t a flaw in the new default group specifically. It’s a constraint of how referrer-based attribution works across the web. The same limitation applies to direct referral traffic from social platforms and messaging apps.
Understanding the ceiling-floor distinction is what separates an accurate reading of the data from an optimistic one.
What Google Hasn't Said Yet
Three open questions are worth flagging for anyone interpreting this data.
Which AI assistants are on the list?
Google’s May 2026 changelog references ChatGPT, Gemini, and Claude by name. The August 2025 regex guidance covered those three, plus Microsoft Copilot and Perplexity.
It isn’t clear from Google’s current documentation whether all five referrers are included in the new default definition, or whether additional platforms have been added.
Without a published list, you’re relying on what the data shows rather than what Google has formally confirmed.
Is it retroactive?
Google has not confirmed whether sessions from before 13 May 2026 will be reclassified under the AI Assistant channel. Based on Google’s standard practice when updating channel definitions, industry consensus is that the change applies forward only. Historical data remains attributed as it was recorded at the time.
If you’re comparing year-over-year acquisition data, this matters directly. AI-referred sessions from May 2025 would have been labelled as Referral or Direct. Equivalent sessions from May 2026 appear under AI Assistant. The comparison is not like-for-like.
Is the documentation updated?
As of mid-May 2026, the Default Channel Group definitions page in Google’s support documentation had not been updated to include ‘AI Assistant’ in its published channel table.
The change is live in the product but not yet fully reflected in the official reference material. This creates ambiguity for anyone trying to understand the precise rules governing the channel’s behaviour.
A fourth question, relevant for clients running Google Ads: it’s unclear from current documentation whether the AI-assistant medium value propagates to linked Ads accounts for attribution purposes. This may or may not matter depending on the specific attribution model in use, but it remains unaddressed in Google’s changelog.
What This Means for Clients: Practical Steps
Add a property annotation
In GA4, add an annotation on 13 May 2026 noting the introduction of the AI Assistant default channel group. This ensures that anyone reviewing Acquisition data a year from now understands why the channel appears from that date. It’s a small action that prevents confusion at reporting time.
Run custom and default groups in parallel
If a custom channel group for AI traffic was already active on a property, keep it running for at least 30 days alongside the new default. Compare the session counts from both views. The discrepancy will indicate whether the custom regex was catching traffic that the default definition misses, or whether they’re effectively covering the same referrers.
Break out individual assistants using the source dimension
The AI Assistant channel groups all recognised AI traffic together. For clients where knowing which specific assistant is driving conversions matters, adding the source dimension to Acquisition reports shows the split: chatgpt.com, claude.ai, gemini.google.com, and so on. This is increasingly relevant for GEO and content strategy decisions.
Treat it as a baseline, not a complete picture
The AI Assistant channel is a useful signal, but the volume you see in GA4 understates the real influence of AI assistants on your traffic. A visitor who clicks an AI-sourced link but returns later via branded search will appear under Organic Search, not AI Assistant. Understanding this matters when assessing channel performance against other acquisition sources. For context on how attribution gaps affect what gets reported, see our post on why websites get traffic but no leads.
Treat it as a baseline, not a complete picture
AI-referred visitors tend to arrive with a higher level of prior knowledge than a typical referral visitor. The AI model has already contextualised the topic, answered initial questions, and surfaced your brand as relevant. That pre-briefing often shows up in conversion rates.
If the AI Assistant channel is active in a property, it’s worth checking whether conversion rates from this channel differ meaningfully from Referral or Organic Search.
The Strategic Question Now in Front of Every Business
Google adding a default channel group to GA4 is a formal acknowledgement that AI assistants are a measurable acquisition channel.
The question of how to track this traffic, which occupied a fair amount of attention in the analytics community over the past 18 months, is largely settled. The plumbing is in place.
What isn’t settled is the more important question: how much of a business’s content and optimisation effort should be directed at being cited by these models, rather than simply ranked in traditional search?
The AI Assistant channel data will help answer that question over time, but the answer depends on understanding what the channel captures and, equally, what it misses.
We’ve been tracking this category of traffic for clients for some time. The addition of a default channel group makes the data more accessible, but the interpretation still requires context. If you’d like to understand what AI traffic looks like across your specific property, including the gap between what GA4 shows and what’s likely arriving through less visible paths, that’s a useful conversation to have before concluding the numbers.
In the meantime, if your broader digital strategy is due for a review, our post on whether SEO is worth it for small businesses covers some of the same questions about attributing value to organic channels.
Frequently Asked Questions
The AI Assistant channel is a new default channel group in Google Analytics 4, introduced on 13 May 2026. When traffic arrives from a recognised AI assistant referrer such as ChatGPT or Claude, GA4 automatically assigns the session to this channel and populates three dimensions: medium (ai-assistant), Channel Group (AI Assistant), and Campaign (ai-assistant).
No. Based on Google’s standard practice with channel definition changes, the AI Assistant channel applies from 13 May 2026 forward. Historical sessions attributed to Referral or Direct prior to this date are not reclassified. If a custom channel group was running before this update, that group’s historical data remains in place.
The channel only captures visits that arrive with a referrer header. Traffic from native iOS or Android AI apps, in-app browsers, or copy-pasted links often arrives without a referrer and is recorded as Direct instead. What you see in GA4 is a floor figure, not the full picture of AI-influenced visits to your site.
Three things to track: keyword ranking movement on target terms, organic traffic volume in Google Analytics, and enquiries attributed to organic search. Early signals improved crawl coverage and indexation; small ranking movements usually appear within 90 days. Traffic and lead lift tend to follow from months six to twelve.
If a custom channel group was already active before May 2026, run it in parallel with the new default for 30 days to compare coverage. After that, the default group may be sufficient unless you need to track referrers not included in Google’s definition, or require continuity with your custom group’s historical data.
Google’s May 2026 changelog names ChatGPT, Gemini, and Claude. Microsoft Copilot and Perplexity were covered in the August 2025 regex guidance. A definitive published list of all recognised referrers has not yet been made available by Google.
