GA4's AI Assistant channel: what it shows and what it misses
How the channel is defined
According to Google's help page on default channel groups, the AI Assistant channel matches when "the medium exactly matches ai-assistant". GA4 sets that medium, and the campaign (ai-assistant), when the referrer matches Google's list of AI assistants. Google names ChatGPT, Gemini, DeepSeek, Copilot and Grok as examples.
What it does well
- It is on by default in every GA4 property. Nothing to configure.
- It moves AI visits out of the general Referral bucket, so trends are easier to see.
- It works across all standard Acquisition reports.
What it misses
- Google's own AI answers. Clicks from AI Overviews and AI Mode count as Organic Search. If AI Overviews are a large part of your search presence, the AI Assistant channel underestimates AI influence. Our guide on how to measure Google AI Overviews traffic shows what you can track instead.
- Visits without a referrer. Links opened from some apps have no referrer and land in Direct.
- Engine-level detail at a glance. The channel is a single row. Add Session source as a secondary dimension to split it.
- Assistants not on Google's list. Smaller assistants fall back to Referral until Google adds them. Google says it reviews its source lists at least once a year.
Getting more detail
- In GA4, build a custom channel group or an exploration filtered to medium = ai-assistant, broken down by source and landing page.
- In Countnest, the AI traffic view splits 17 assistants by default and shows the landing pages for each, alongside AI crawler activity.
Which should you use?
If you already run GA4 with Google Ads, the built-in channel is a good start. If you want a privacy-first setup with a smaller script, EU-hosted data and engine-level AI reporting without configuration, Countnest is built for that. Many sites run both during a trial to compare.
See your own numbers in minutes
30-day free trial, no card required. Then from $14 a month. Cancel anytime.
Start free for 30 days