How to Track AI Traffic in GA4: ChatGPT, Gemini, Claude, Perplexity

To see AI traffic in GA4, use the built-in AI Assistant channel (live since 13 May 2026) and add a custom channel group with a regex on sources like chatgpt.com, perplexity.ai, claude.ai, gemini.google.com and copilot.microsoft.com. Skip the second step and you lose Perplexity plus all historical data before May 2026.

The same story with every other client. The owner opens analytics, sees organic down and Direct up, and concludes the brand got stronger. In reality ChatGPT delivered the highest-intent visitors of the quarter — and none of them showed up in any report.

This is not a rounding error. According to Adobe Digital Insights, in March 2026 AI-assistant traffic converted 42% better than all other traffic — after converting 38% worse a year earlier. That is not an incremental gain, that is a reversal. A channel you do not measure is a channel you do not invest in.

Why AI traffic is still invisible

The problem has three layers, and each needs a different fix.

Layer 1 — referrers get lost. When someone clicks a link inside a chat, the browser often does not pass the origin. Analysts estimate that 35% to 70% of AI sessions arrive with no referrer at all and land in Direct / None. Mobile apps, copy-pasted links, desktop clients — all of them strip the source.

Layer 2 — before May 2026, GA4 simply did not know these sources. It dutifully filed chatgpt.com under Referral, next to forums and aggregators. No dedicated channel meant no line in the report.

Layer 3 — AI Overviews are not referrals at all. If the user came from an AI Overview inside Google Search, GA4 reports plain Organic Search. There is no native way to split it from a classic blue-link click.

"Things change fast: the data says AI search results can shift by 40–60% within a single month. So if you want results — keep checking."
— Nikolay Shmichkov

What the new AI Assistant channel does

On 13 May 2026 Google added a native AI Assistant channel to the GA4 default channel group. By early June it had rolled out to most properties. No setup needed — it appears in Traffic Acquisition on its own.

Good news: ChatGPT, Gemini, Copilot, Grok and Deepseek now get their own line. Bad news — three limits Google does not advertise:

• Perplexity is not included and still falls into Referral. It is one of the highest-intent AI sources you have.
• No backfill. The channel does not reclassify history — everything before 13 May 2026 stays in Referral and Direct.
• It does not rescue referrer-less sessions. No referrer, no channel: that traffic remains Direct.

The takeaway: the built-in channel is a convenient window, not a measurement system. You still need your own channel group.

How to build a custom channel group, step by step

Fifteen minutes, property admin rights required.

1. GA4 → Admin → Data display → Channel groups.
2. Click Create new channel group. Name it, for example, "SEO + AI".
3. Add a new channel called AI Traffic. Condition: Source → matches regex.
4. Paste the regex:
   .*(chatgpt\.com|chat\.openai\.com|openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|edgeservices\.bing\.com|deepseek\.com|grok\.com|meta\.ai|you\.com).*
5. The critical part. Drag AI Traffic above the Referral channel. GA4 evaluates rules top-down: if Referral fires first, your whole setup is useless.
6. Save. Unlike the native channel, a custom group recalculates historical data.

Watch the operator. GA4 channel groups offer two similar conditions: partially matches regex (behaves like "contains") and matches regex (requires the whole string to match). The pattern above is wrapped in .*(…).*, so it works with either. And never add a bare bing.com — it would drag all Bing organic into the channel. The Source dimension holds the hostname only, with no path, so patterns like bing.com/chat never match.

Data will not appear instantly — the channel group takes up to 24–48 hours to reprocess. And in the Traffic Acquisition report, switch the dimension from the default channel group to your custom one: a custom group does not replace the default, it lives alongside it.

This source list covers over 99% of measurable AI referral traffic as of mid-2026. Review the regex quarterly — the chatbot landscape moves faster than Google's docs.

How to dig AI traffic out of Direct

The regex only catches sessions that passed a referrer. The rest — up to 70% — sit in Direct. You cannot fully recover them, but you can estimate them three ways.

UTM tags on content AI cites. If you publish on external sites, forums or PR outlets, tag your links. The model copies the URL whole, tags included.

A "suspicious Direct" segment. Build a GA4 segment: channel = Direct, landing page = a deep internal page (not the homepage), new user. A direct hit on a mid-blog article nobody has ever seen is almost always a chatbot. Compare that segment against the periods when you were growing AI visibility.

Server logs. The most honest source. Logs show both crawlers (GPTBot, PerplexityBot, ClaudeBot) and referral hits. If your host gives you access logs, that is the only way to see the whole picture.

What to look at so you do not fool yourself

Here is the trap business owners fall into. In absolute numbers AI traffic is still tiny — Conductor puts it around 1% of total site traffic on average. It is easy to glance at that number and dismiss the channel.

The mistake is looking at the wrong metric. Look at the money.

What your AI Traffic report should actually show:

• Conversions and revenue, not sessions. If 1% of traffic drives 5% of leads, you do not have a small channel — you have an under-invested one.
• Landing pages. This is literally the list of content AI decided was worth citing. It is your content plan: write more of that.
• Platform split. ChatGPT takes around 75% of all AI referrals (some studies say up to 92%), Gemini is a confident second. If you skew toward Perplexity, you are being cited for freshness and sourcing rather than brand.
• Month-over-month trend. Absolute numbers say little; the trend says everything.

"Traffic from AI search converts 4x better than Google. And there is a good reason: AI takes away almost the entire top of the funnel — and there were never many sales up there anyway."
— Nikolay Shmichkov

▶ How to track AI search visibility (SEO and GEO)

GA4 is not the only source

GA4 only shows people who reached your site. But half the value of AI search is being mentioned — even without a click. Complete the stack:

• Google Search Console — through 2026 Google is rolling out separate AI Overviews and AI Mode metrics. Impressions are partly blended with regular search, but the trend is readable.
• AI visibility trackers (SE Ranking, Semrush AI Toolkit, Ahrefs Brand Radar) — they show which prompts cite you and whether your share is growing.
• Logs and robots.txt — make sure you are not blocking GPTBot and PerplexityBot. A blocked crawler means zero AI visibility, and no analytics setup will fix that.

If you are serious about AI visibility, start with our guide to GEO optimization for GPT and the breakdown of how to get cited in AI Overviews.

FAQ

Do I need to configure anything for the AI Assistant channel to appear?

No. It is on by default since May 2026 and shows up in standard acquisition reports. But it excludes Perplexity, does not backfill history and does not recover referrer-less sessions — so you still need a custom channel group.

Why is my AI Assistant channel near zero when my content clearly gets cited?

Three reasons: the referrer was stripped (traffic went to Direct), you are cited without a link, or you are cited inside AI Overviews — which is Organic Search, not a separate channel. Check the "Direct + internal landing page + new user" segment.

Can I track AI traffic in Google Ads?

No, this is an organic channel. Ads inside AI answers are still in testing and have no separate reporting.

Is a channel worth 1% of traffic worth investing in?

Look at conversion and revenue, not sessions. If 1% of sessions delivers 4–5% of leads, it is the cheapest acquisition channel on your site. And the trend is steep: AI referrals grew more than 8x year over year.

How do I separate AI Overviews traffic from regular organic?

Natively in GA4 — you cannot. Indirectly: watch Search Console's AI Overviews reporting and the widening gap between impressions and clicks (the "Great Decoupling").

What to do this week

Do not park this in the backlog — setup takes one evening, and data only accumulates from the moment you switch it on.

1. Check whether the AI Assistant channel appears in your GA4 Traffic Acquisition report.
2. Create the custom channel group with the regex above and move AI Traffic above Referral.
3. Build a report: AI Traffic channel → conversions, revenue, landing pages.
4. Audit robots.txt for blocked AI crawlers.
5. In a month, compare AI channel conversion against organic. You will probably be surprised.

Need help with analytics setup and AI search visibility — get in touch and we will look at your case.