GA4 Adds “AI Assistant” Default Channel: ChatGPT, Gemini, and Copilot Traffic Now Breaks Out of Referral
Web Analytics

GA4 Adds “AI Assistant” Default Channel: ChatGPT, Gemini, and Copilot Traffic Now Breaks Out of Referral

Google Analytics 4 now has a dedicated bucket for traffic arriving from AI assistants. As of June 7, 2026, a new Default Channel Group called AI Assistant is available across GA4 properties, automatically reclassifying sessions from ChatGPT, Gemini, Copilot, Grok, and DeepSeek out of Referral and into their own channel. No configuration required.

What the new channel is

The AI Assistant channel is a built-in Default Channel Group in GA4 that matches sessions where the traffic medium is set to ai-assistant and the campaign is (ai-assistant). Google rewrites the source classification automatically when an incoming click matches a list of known AI referrers. The result is a clean, named channel that sits alongside Organic Search, Direct, and Referral in standard acquisition reports.

Signal Value GA4 now sets
Session medium ai-assistant
Campaign (ai-assistant)
Default Channel Group AI Assistant
Old bucket (before) Referral

Timeline and rollout

Google first added the classification logic on May 13, 2026. Wide property availability followed on June 7, 2026. The change is documented in the Google Analytics Help center under “Default Channel Group” and “What’s new in Analytics.” Trade coverage came from Search Engine Roundtable, ALM Corp, GA4 Optimizer, and DigitalApplied.

Which platforms are recognized, and which are not

Google officially names five AI assistants in the channel definition:

  • ChatGPT (OpenAI)
  • Gemini (Google)
  • Microsoft Copilot
  • Grok (xAI)
  • DeepSeek

Perplexity is not in the official definition. Traffic from Perplexity continues to land in Referral. Analysts who care about Perplexity referrals need a custom channel group with a regex match on the perplexity.ai domain, a manual step GA4 does not handle automatically.

What this does not cover

Three limitations matter for anyone reading early data:

  • No retroactive reclassification. Historical sessions already recorded as Referral or Direct stay there. The AI Assistant channel only captures data going forward from the rollout date.
  • Google AI Overviews and AI Mode are excluded. Those are search-surface features, not external chat referrers. They do not flow into the AI Assistant channel.
  • Dark traffic is unchanged. Copied links, app-based clicks, and sessions with missing referrers still land in Direct. The channel cannot recover unattributed AI traffic that never carried a referring domain.

Why AI assistant referrals behave differently

Users arriving via an AI assistant typically asked a specific question and received a contextualized answer before clicking. The intent arriving on your page is narrower and better-formed than a generic Google referral. Practitioners (GA4 Optimizer, DigitalApplied) report that this traffic often arrives with a clearer reason to engage with the specific page it lands on, though concrete benchmarks are still emerging. Isolating the channel makes that behavior measurable.

What to do now

A few practical steps are worth running through:

  1. Check Reports → Acquisition → Traffic acquisition. The AI Assistant channel appears there automatically once sessions qualify. No setup needed for the five named platforms.
  2. Do not expect retroactive data. Segment comparisons before May 13 will show zero in the AI Assistant column, which is expected, not missing data.
  3. Add Perplexity manually. In GA4, go to Admin → Data display → Channel groups and create a custom rule matching source contains perplexity.ai with medium referral.
  4. Tag AI-driven campaigns explicitly. If you distribute content through AI-integrated products (newsletter tools, AI-powered social schedulers), tag outbound links with a consistent UTM medium. Building those URLs with a structured campaign URL builder keeps the medium value clean and prevents sessions from landing in the wrong channel.
  5. Pair with UTM standards. The AI Assistant channel catches organic referrals from AI assistants. Paid or editorial placements in AI newsletters still need manual UTM tagging. A documented GA4 UTM tagging standard prevents overlap between AI Assistant and your other campaign channels.

Sources: Google Analytics Help (“What’s new in Analytics,” “Default Channel Group”); Search Engine Roundtable; ALM Corp; GA4 Optimizer; DigitalApplied.

Alex Savich

Digital marketing journalist covering MarTech, AI, SEO, and analytics for Elsop Insights.