Google Analytics has added a default “AI Assistant” channel group for traffic from recognized AI chatbot referrers, with Google citing ChatGPT, Gemini and Claude as examples.
GA4 property owners no longer need to create custom channel groups with regex patterns to separate AI assistant visits from recommendations. Until now, all AI chatbot traffic ended up in the referral bucket by default.
What’s new
The update touches three traffic source dimensions at once.
When Google Analytics detects a referrer that matches a detected AI assistant, it assigns “ai-assistant” as the middle value. These sessions are then grouped under the AI Assistant channel in the standard channel group reports. The campaign dimension is given the reserved label “(ai-assistant)”.
All three changes occur automatically. Property owners do not need to configure anything.
Google described the update as a way to “monitor how generative AI impacts your business by tracking user clicks, trending AI sources, and how that traffic compares to traditional channels like organic search.”
Google has not released the full list of recognized AI Assistant recommenders. The Help Center entry gives ChatGPT, Gemini and Claude as examples.
context
Google has been working on this for almost a year. In August, the Analytics team released instructions for creating custom channel groups with regex patterns to capture traffic from AI assistants. This guide mentioned ChatGPT, Gemini, Microsoft Copilot, Claude, and Perplexity as platforms to pursue. This marked the point at which Google began treating AI assistant traffic as a category worth measuring separately in its own documentation.
The custom channel group workaround had limitations. Regex patterns required manual maintenance as AI platforms changed domains. Property owners required editor-level access to set it up. And the limitation to two custom channel groups in GA4 meant that one of only two available slots had to be dedicated to AI tracking.
This follows a pattern set by Google in 2022 when it added “cross-network” as a default channel group to capture Performance Max and Smart Shopping traffic. This update also moved traffic from a generic bucket to its own dedicated channel without the need for manual configuration.
AI traffic attribution is a recurring measurement challenge. Last year, Google fixed a bug that caused search traffic in AI mode in GA4 to be reported as “direct” instead of “organic” after a noreferrer code removed referrer headers. Google has also added AI Mode data to Search Console performance reports, but this traffic will be rolled into existing totals rather than displayed as a separate category.
Why this is important
Anyone running a custom channel group to track AI Assistant traffic may be able to simplify this setup as the native channel appears in reports. The native channel potentially reduces the need for regex patterns and the manual channel ordering that Google recommended last year.
For properties without custom AI tracking, this traffic is automatically broken down by referral. Sessions that previously appeared as generic referral traffic from chatgpt.com or claude.ai have their own channel.
One loophole worth noting is the referrer limit. AI assistant traffic that arrives without a referrer header still ends up in Direct. This can happen through in-app browsers and mobile apps, or when users copy and paste links. The new channel only captures what GA4 can identify about the referrer.
Looking ahead
Beyond the three examples mentioned, Google has not published which AI assistants are on the list of recognized referrers. It also didn’t say how the list will be updated as new platforms come onto the market. Five platforms were mentioned in the August 2025 Custom Channel Groups Guide, but the new automated system does not indicate full coverage.
The Default Channel Group Definitions page has not yet been updated to include AI Assistant in the channels table, so the full technical definition is not available for review. The custom channel group regex patterns that Google released last year can still cover platforms that are not on the recognized referrer list.
Featured image: Stocking/Shutterstock
Follow us on Facebook | Twitter | YouTube
WPAP (907)
