GA4 property owners will now see chatbot-referred traffic separated from generic referrals inside their standard acquisition reports. Google confirmed on May 13, 2026, in its Analytics Help Center "What's New" documentation, that a native "AI Assistant" channel has been added to GA4's Default Channel Group, requiring no configuration from property owners.
What Changed in GA4's Default Channel Group
The update, published in the Google Analytics Help Center on May 13, 2026, modifies how traffic source dimensions are processed. When Google Analytics detects a referrer matching a recognized AI assistant, it automatically assigns the value "ai-assistant" to the medium dimension. Those sessions are then grouped under the "AI Assistant" channel within Default Channel Group reports, and the campaign dimension receives the reserved label "(ai-assistant)." All three dimension changes occur simultaneously, with no action required from the property owner.
The new channel appears alongside Organic Search, Direct, Paid Search, and Organic Social. Any acquisition report that uses the Default Channel Group now surfaces AI traffic as a distinct line item. Traffic acquisition, user acquisition, and channel-based explorations all reflect the new channel going forward.
Which AI Platforms Are Covered
Google names ChatGPT, Gemini, and Claude as examples of recognized assistants, but has not published the full recognized referrer list. Google has also not stated how the list will be updated as new platforms launch. The August 2025 custom channel group guidance named five platforms, ChatGPT, Gemini, Microsoft Copilot, Claude, and Perplexity, but the new automatic system does not specify its full coverage.
The Default Channel Group definitions page has not yet been updated to include "AI Assistant" in its channel table, so the full technical definition is not available to review.
Why This Update Follows Years of Misattribution
The original default channel system, designed before generative AI platforms became significant traffic sources, had no classification for chatbot referrals. Those sessions were typically logged as Referral, or, in cases where the referrer header was stripped, as Direct.
The custom channel group workaround that preceded this update carried significant limitations. Regex patterns required manual maintenance as AI platforms changed domains. Property owners needed editor-level access to configure them. GA4's limit of two custom channel groups also meant that properties tracking AI traffic manually were consuming one of only two available slots for that purpose.
This follows a pattern Google established in 2022 when it added "cross-network" as a default channel group to capture Performance Max and Smart Shopping traffic, an update that similarly moved sessions from a generic bucket into a dedicated channel without requiring manual configuration.
Known Limitations of the New Channel
The update does not resolve all AI attribution gaps. Traffic originating from AI mobile apps and certain embedded browser contexts will still arrive without a referrer header and will continue to land in the Direct channel. That is a structural limitation of how browsers and apps handle referrer data, not a platform-specific problem.
Studies of AI referral traffic suggest that only 60 to 80 percent of actual AI-originated visits carry a clean referrer header. The remainder appear as Direct or go uncategorized. For marketers building measurement around AI search visibility, the GA4 AI Assistant channel captures the floor of that traffic, not the ceiling.
The custom channel group regex patterns Google published in August 2025 can still cover platforms that are not on the recognized referrer list, and may remain useful for properties that need broader coverage than the native channel provides.
What This Means for GA4 Reports and Attribution
Marketers reviewing Traffic Acquisition or User Acquisition reports should expect to see a new "AI Assistant" row appear going forward. For properties that had previously relied on generic Referral traffic to represent chatbot visits, the arrival of this channel will shift some volume out of Referral and into AI Assistant. That reclassification reflects the same underlying sessions; the traffic has not changed, only how it is categorized.
Properties that built custom channel groups to track AI traffic should verify whether the native channel and their existing custom definitions are capturing the same sessions before removing the custom configuration. Existing filters or segments built around the medium dimension may also need to be reviewed, as any segment using a condition such as "medium does not contain cpc" will now implicitly exclude AI-assistant sessions as well.
Google's official "What's New" page lists the AI Assistant traffic measurement feature under the May 13, 2026, release and states that:
"You can now identify how users are discovering your site through chatbots like ChatGPT, Gemini, and Claude via a new AI Assistant channel in your Default Channel Group reports."
