Google has added AI Assistant as a default channel group in Google Analytics 4, automatically separating visits referred from chatbots such as ChatGPT, Gemini, and Claude from organic search and referral traffic. The change rolls out across all properties from 13 May 2026 and requires no configuration on the property owner's side.
For marketing and growth teams, this is the first time mainstream web analytics has treated generative AI assistants as a distinct acquisition channel rather than bundling them into Referral or Direct. It does not solve attribution on its own, but it gives every GA4 user a comparable, free baseline for measuring how much traffic large language models are sending their way.
This is not an Owlpen feature; we cover the platform implication briefly at the end. The remainder of the article focuses on what is changing inside Google Analytics and what teams running paid and organic acquisition should do next.
What has changed
Until now, a visitor arriving from an AI assistant typically appeared as either Referral (if the assistant set a referrer header) or Direct (if it did not). That made it almost impossible to isolate AI-driven discovery in standard reports. The AI Assistant default channel group changes that by recognising a list of known AI assistant domains at the point of session attribution and tagging the resulting session with a dedicated medium and campaign value.
The mechanics
When the referrer matches a recognised AI assistant, GA4 assigns the medium value ai-assistant and the campaign value (ai-assistant). These values then map into the new default channel group of the same name, alongside Organic Search, Paid Search, Referral, Direct, and the rest.
Where the data shows up
Anywhere GA4 surfaces the default channel grouping: Acquisition reports, Traffic acquisition, the Realtime card for source/medium, and Explorations using the Channel group dimension. Custom channel groups you have already built are unaffected and continue to run alongside the default. If you previously wrote a regex to capture ChatGPT or Perplexity into a custom group, you can keep it, retire it, or rename your custom group to mirror Google's definition.
What you need to do to enable it
Nothing. The default channel group is applied automatically to all properties on Google's rollout schedule. There is no setting to toggle, no API call to make, and no measurement protocol change required. Historical data is not reclassified; only sessions from the rollout date onwards land in the new group.
Rollout window
Google's support article cites a release date of 13 May 2026 for the AI Assistant default channel group. Properties may see the change appear earlier or later within the rollout window. Year-over-year and month-over-month comparisons that span the rollout date should be read with the change in mind, because Organic Search and Referral may show a step-down as AI traffic moves into the new group.
Which assistants are recognised
Google's help centre confirms the channel covers chatbots like ChatGPT, Gemini, and Claude, but does not publish an exhaustive list. From the limited public information, marketing teams should assume the major Western consumer assistants are covered (ChatGPT, Gemini, Claude, Copilot, Perplexity) and that the list will expand quietly over time as Google adds more referrers. If you need to confirm whether a specific assistant is included, the cleanest test is to ask the assistant a query that prompts it to cite your site, click the citation, and check the Realtime report.
One important nuance: the new group catches traffic from agent-driven browsing sessions and from retrieval-augmented citations that appear in chatbot answers. It does not specifically separate the two, so a visit driven by an autonomous agent and a visit driven by a person clicking a chatbot citation will both appear under the same channel group.
What it does not capture
The AI Assistant group is built on the same foundation as every other GA4 channel: it relies on the referrer header that the browser passes when the user clicks through. That has real-world limits.
In-app and mobile assistants
Assistants that open links inside their own in-app browser, or that operate primarily on mobile, often arrive at your site without a referrer header. Those sessions still land in Direct. If your audience uses ChatGPT or Gemini predominantly on mobile, expect a portion of AI-driven traffic to remain hidden in Direct after this change ships.
Answer-only interactions
If the assistant answers a user's question by summarising your content without the user ever clicking through, no session is generated and no data appears in GA4 at all. The new channel group only measures visits, not influence. Brand and content teams that suspect they are losing measurable traffic to zero-click AI answers will not get visibility into that loss from this update.
UTM-tagged links
If you have built campaigns that send users to your site via an AI assistant and you control the destination URL (for example, content placed deliberately for AI ingestion), the channel rules for prompt or campaign-tagged URLs still take precedence over the AI Assistant group. Tagged sessions will be attributed by their explicit utm_source and utm_medium values as before.
What marketers should do now
The practical to-do list is short but worth executing in the first month after the rollout.
Annotate the rollout date
Add a property-level annotation on 13 May 2026 (or the date the change appears in your reports) noting the introduction of the AI Assistant channel group. This stops analysts in three months reading a step-change in Organic or Referral as a campaign result rather than a categorisation change.
Retire or rename custom channel groups
If you previously rolled your own AI Assistant group with a regex on the referring host, decide whether to keep it (for backwards comparability), rename Google's group, or retire yours. Running both is fine but creates two competing numbers in dashboards.
Update conversion attribution dashboards
Any dashboard that filters by channel group (Looker Studio, GA4 Explorations, BigQuery exports) will start showing an AI Assistant value. Make sure your filters, joins, and palette assignments do not collapse the new value into Other.
Track conversion behaviour separately
Visitors arriving from an assistant tend to have a different intent profile to visitors from organic search: they have been pre-briefed by the model before they arrive, and they often click through with a more specific question. Compare bounce rate, scroll depth, and conversion rate by channel group, and adjust landing-page content for AI traffic if the gap is material.
Owlpen and Google Analytics
Owlpen, our cost and performance intelligence platform, focuses on operational and procurement workflows; it does not surface or replicate web analytics. Properties using GA4 will see the AI Assistant channel group inside Google Analytics directly, and any Looker Studio or BigQuery reporting layered on top will inherit it automatically.
For the small number of clients who ask Coaley Peak to consolidate web acquisition data into a wider operational view, we are tracking the channel group rollout and will pull the new dimension into bespoke reporting where it is in scope. If that applies to your engagement, no action is required from your side; we will flag it as part of the next reporting refresh.
Not in Owlpen
Owlpen does not include a web analytics or marketing attribution module. The AI Assistant default channel group is a Google Analytics feature and will be available to GA4 property owners directly, with no Owlpen integration required. Clients with bespoke Coaley Peak reporting that includes GA4 data will see the channel group flow through automatically once Google enables it on the property.
If you would like to discuss how AI-driven traffic is changing the way your business measures acquisition, contact us at enquiries@coaleypeak.co.uk or read more about the Owlpen platform.
Disclaimer. This article is published by Coaley Peak Ltd for general informational purposes only. The views expressed are those of the author, Stephen Grindley, and do not constitute legal, regulatory, financial, or technical advice. Nothing in this article should be relied upon when making procurement, investment, compliance, or technology decisions. References to third-party products, platforms, and companies are for informational purposes only and do not constitute endorsement. Release dates, feature behaviour, and the list of recognised AI assistants are those described by Google in its public help-centre material at the time of writing and have not been independently verified by Coaley Peak. Readers should seek independent professional advice appropriate to their specific circumstances. Information was accurate to the best of the author's knowledge at the date of publication. Coaley Peak Ltd and Stephen Grindley accept no liability for any loss or damage arising from reliance on the contents of this article.