How to Track AI Search Traffic in GA4 and Search Console

Most teams discover they have AI traffic by accident.

Someone spots utm_source=chatgpt.com in a landing page report. Or a sales call opens with "I found you through ChatGPT." And suddenly there's a question nobody can answer with the reports they've got.

The good news is that GA4 finally has a native answer, added in May 2026. The less good news is that it misses more than most people realise — and a chunk of AI traffic is genuinely unmeasurable no matter what you configure.

Here's what to set up, and what to accept you'll never see.

The short version

GA4's native AI Assistant channel covers ChatGPT, Gemini, DeepSeek, Copilot, and Grok automatically. It notably excludes Perplexity, it's forward-only, and Google's own AI Overviews and AI Mode stay inside Organic Search rather than being split out.

A custom channel group catches what the native one misses. Ten minutes to build.

Search Console's AI Mode filter is your only first-party window into Google's own AI surfaces.

And a lot is simply invisible — sessions arriving with no referrer, mobile app traffic, and every citation where you were the source and nobody clicked.

Step 1 — Know what the native channel does

Google added AI Assistants as a default channel group on 13 May 2026. No setup needed. When an incoming click matches Google's internal list of AI assistant referrers, GA4 rewrites the medium to ai-assistant and groups the session accordingly.

To see it: Reports → Acquisition → Traffic acquisition, with the primary dimension set to Session default channel group.

Genuine progress, and it solved the "why is everything Unassigned" problem for the named platforms. But three limits are worth knowing before you report the number to anyone:

It's forward-only. Sessions processed before the rollout keep whatever channel they originally got. Your historical AI traffic stays misfiled.

Perplexity isn't on the list. Google's published set names ChatGPT, Gemini, DeepSeek, Copilot, and Grok. Perplexity — one of the higher-intent AI sources — keeps landing in plain Referral.

Google's own AI surfaces are excluded. AI Overviews and AI Mode traffic stays inside Organic Search by design. You can't separate it in GA4 at all.

Step 2 — Build a custom channel group

This catches the platforms the native channel misses and gives you one consistent bucket.

Admin → Data display → Channel groups → Create new channel group.

Add a channel called AI Search with the condition Session source matches regex:

chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|claude\.ai|copilot\.microsoft\.com|grok\.com|deepseek\.com|meta\.ai|you\.com|phind\.com

Then drag it above Referral. This is the step people skip and it breaks everything — GA4 evaluates channel rules top to bottom, so if Referral sits higher it claims every AI session first and your new channel stays permanently empty.

Two practical notes. GA4's regex matching is case-sensitive, so if your source report shows both ChatGPT and chatgpt, cover both. And keep the native channel rather than replacing it — treat your custom group as the wider net over the top.

Step 3 — Use Search Console for Google's AI surfaces

Since GA4 folds AI Overviews and AI Mode into Organic Search, Search Console is your only first-party view of Google's own AI surfaces. It added an AI Mode filter in June 2025.

What to watch there is the divergence between impressions and clicks. The characteristic AI Overview pattern is impressions climbing while clicks fall — more people seeing you, fewer visiting. If a page shows rising impressions and falling clicks over a few months, an AI Overview is very likely appearing above it and answering the question.

That divergence is probably the most useful signal available to you, precisely because it needs no new tooling.

Step 4 — Read your server logs

The most underused method, and the only one that shows AI activity before a click exists.

Your server logs record every AI crawler visit. Two things worth separating:

Retrieval bot hits — OAI-SearchBot, Claude-SearchBot, PerplexityBot — tell you which pages are being fetched to build answers. This is upstream of citation and completely invisible in GA4.

User-triggered fetches — ChatGPT-User, Claude-User, Perplexity-User — represent a real person, right now, whose assistant is reading your page on their behalf. That's a human seeing your content, and no analytics platform will ever record it as a session.

Verify by reverse DNS rather than trusting the user-agent string, since anyone can fake a header.

What you genuinely cannot measure

Being honest about this matters, because otherwise you'll spend weeks chasing a number that doesn't exist.

Referrer-less sessions. A substantial share of AI referrals arrive with no referrer header and land in Direct. Estimates vary widely by platform and by study, and I'd treat any precise figure sceptically — but the direction is consistent: your real AI traffic is higher than your dashboard shows.

Mobile app traffic. Assistant apps generally pass no attribution data.

Zero-click citations. The big one. You were the source, the answer used your content, and nobody visited. Pew found only about 1% of AI Overviews led to a click on a cited source — so most of your "AI visibility" is, by construction, invisible to analytics.

Query data. Assistants don't surface the prompt, so there's no keyword equivalent. You can see that someone came from ChatGPT; you can't see what they asked.

The consequence is that AI visibility and AI traffic are different quantities, and only the second is measurable. Anyone selling you a complete picture of the first is selling you a model, not a measurement.

What the numbers mean when you have them

Three things worth knowing as you read your new channel.

AI referrals are small but high-intent. Chartbeat found AI chatbot referrals grew over 200% while still representing under 1% of total publisher referrals. Multiple analyses find AI-referred visitors convert at substantially higher rates than organic — the figures range widely enough that I wouldn't quote a specific multiple, but the direction is consistent across sources.

So judge it on conversions, not sessions. A channel at 0.5% of traffic converting several times better than organic deserves attention that its session count doesn't suggest.

And compare it against itself. Month-over-month growth in your AI channel is meaningful. Comparing its absolute size to organic isn't, because they're at completely different scales and stages.

Frequently asked questions

Does GA4 show ChatGPT traffic?
Yes, since May 2026. GA4 added a native AI Assistant channel that automatically recognises ChatGPT, Gemini, DeepSeek, Copilot, and Grok. It excludes Perplexity, which still lands in Referral, and it's forward-only, so sessions from before the rollout keep their original classification. A custom channel group with a source regex fills both gaps.

Can you see AI Overview impressions?
Not separately in GA4 — Google's AI Overviews and AI Mode traffic stays inside Organic Search by design. Search Console added an AI Mode filter in June 2025, which is the only first-party view available. The most practical signal is the divergence between impressions and clicks: rising impressions with falling clicks strongly suggests an AI Overview is appearing above your result.

How do I measure GEO performance?
Combine three layers, and accept that none is complete. GA4 custom channel groups capture the clicks that arrive. Server logs show which pages retrieval bots are fetching, which is upstream of citation. Manual or tool-assisted prompt testing shows whether you're appearing in answers at all. The gap between citation and traffic is real and permanent — Pew found only about 1% of AI Overviews led to a click on a cited source.

What to do next

Build the custom channel group. Ten minutes, and remember to drag it above Referral or it'll sit empty and you'll conclude you have no AI traffic.

Then open Search Console and look at your top pages for impressions-up, clicks-down. That pattern is AI Overviews at work, and it tells you which of your pages are being answered rather than visited — which is the list worth restructuring first.

Free: The SEO audit checklist.

---

Related guides

• SEO when AI answers the question first — what to do about what you find
• llms.txt and AI crawlers — the bots showing up in your logs
• Search Console: the 5 reports that matter — reading the rest of it