Google Analytics Adds AI Assistant Channel Group

Google has added a new default channel group to Google Analytics called AI Assistant, giving GA4 property owners automatic separation between traffic from chatbots like ChatGPT, Gemini and Claude and the wider Referral channel. The change updates three traffic source dimensions and applies with no setup required. For marketing teams trying to attribute pipeline and conversions to AI search, it’s the most useful GA4 measurement update Google has released this year.

What’s Changed

When Google Analytics detects a referrer that matches a recognised AI assistant, three dimensions update at once:

• Medium is set to ai-assistant.
• Sessions appear under the AI Assistant channel in Default Channel Group reports.
• The campaign dimension carries a reserved (ai-assistant) label.

Google describes the update as a way to monitor how generative AI is influencing visits and conversions, and how this traffic compares to organic search and other established channels. The named referrers are ChatGPT, Gemini and Claude, although Google hasn’t published the complete list of platforms covered.

Why This Update Matters

Until now, traffic from AI assistants has appeared in the Referral channel alongside every other inbound referring domain. The only way to break it out cleanly was a custom channel group built on regex patterns, with Google publishing template guidance for this approach in August 2025. As Search Engine Journal pointed out, that workaround had three specific drawbacks. The regex needed updating whenever an AI platform changed domain or added subdomains, set-up required editor-level GA4 access and properties are capped at two custom channel groups in total. That last cap forced a trade-off between AI tracking and other reporting priorities.

The native channel removes those constraints. Properties that never set up a regex workaround will see AI traffic broken out automatically, while teams already running a custom solution can simplify what they’re maintaining. Sessions, conversions and assisted conversions from AI sources can now be analysed alongside Organic Search, Paid Search and Direct in the standard reports most marketing teams already use.

Google’s classification choice matters too. Treating AI assistants as a peer channel to organic, paid and email, rather than another row in the referral list, aligns GA4 reporting with how decision-makers now discover suppliers and brands.

A Limitation Worth Knowing About

The new channel only captures sessions that arrive with a referrer header GA4 can read. Visits that come through in-app browsers, mobile chatbot apps or links copied and pasted into a fresh tab will still attribute to Direct, because the referring source is stripped or absent at the point of click. This isn’t unique to AI traffic. Google fixed a similar issue last year, when its own AI Mode search results were stripping referrer headers and routing organic visits into Direct.

The practical implication is that AI Assistant figures in GA4 should be read as a lower bound rather than the full picture of AI-driven visits. If your reports show a sharp lift in Direct traffic alongside the new AI Assistant channel, both signals deserve attention. Pairing this data with referrer log analysis, server-side tagging and dedicated LLM visibility tracking will close more of the gap.

What It Means for AI Search Measurement

For anyone investing in AEO and GEO, the update finally connects AI visibility work to first-party traffic data in GA4 without manual configuration. AI Share of Voice has been a useful proxy for visibility within tools like ChatGPT and Perplexity, but matching that visibility to actual visits, lead quality and revenue has required custom tagging that not every team has the resources to build.

It’s also part of a wider shift in how Google reports AI traffic. Google added AI Mode data to Search Console performance reports earlier this year, although that traffic is still blended into existing totals rather than reported as a separate category. Read together, the two updates give marketing teams a clearer view from AI-driven impressions through to engaged sessions and conversions. That’s the data B2B and public sector teams need to justify ongoing investment in AI search work.

How We’re Planning to Use This

We’re working on bringing the new AI Assistant channel into our purpose-built reporting platform, which pulls Google Analytics, Search Console and conversion data into one branded view for clients. Once integrated, AI Assistant traffic will sit alongside Organic Search, Paid Search and Referral in that same view, with the same period comparisons and filters built into the rest of the platform.

For our AI SEO clients, the new channel will fit alongside the AI Share of Voice tracking and LLM performance analytics work we already deliver. The goal is a single line of sight from AI visibility through to GA4 sessions and conversions.

If you’d like to understand what AI Assistant traffic looks like for your own site, get in touch.