AI traffic tracking system in GA4 showing a dedicated AI Assistants channel for ChatGPT, Claude, and Perplexity referrals
A dedicated AI Assistants channel in GA4 pulls ChatGPT, Claude, and Perplexity out of the generic Referral row.

A client asked me a simple question a few months ago: how much traffic is ChatGPT actually sending us? I opened their GA4, and I could not answer it. Not because the traffic was not there, but because GA4 buries it. AI visits hide inside the generic Referral row, split across a dozen domains, and a big chunk lands as Direct with no label at all.

So I built a system that catches AI referrers, isolates them into their own channel, and turns them into a report a client actually reads. Below is the exact setup, step by step, with the regex I reuse for every account. If you want the short version of why this matters, here it is.

TLDR

GA4 does not track AI traffic on its own. Create a custom channel group named AI Assistants, add one high-priority channel, and paste a single Source matches regex that catches ChatGPT, Claude, Perplexity, Gemini, and Copilot. Pair it with an Exploration for historical data, then ship a monthly report. Setup takes about 30 minutes. What you measure is a floor, not a total, but a floor you can see beats a number you are guessing at.

Why GA4 Hides Your AI Traffic

GA4 was built before AI assistants became a real referral channel, so it has no idea what to do with them. Three things go wrong by default. First, AI referrers get dumped into the catch-all Referral channel, mixed in with every other site that links to you. Second, they are split across many domains, so chatgpt.com, chat.openai.com, and perplexity.ai each show as separate rows instead of one story. Third, and most frustrating, many AI tools strip the referrer entirely, so those visits arrive as Direct with no source at all.

The fix is not a plugin or a paid tool. It is a custom channel group plus one reusable regex. Once it is in place, every standard report shows AI traffic as its own line.

Before and after comparison of GA4 channel reports, with AI traffic hidden inside Referral on the left and isolated into an AI Assistants channel on the right
Before: AI visits buried in Referral. After: a clean AI Assistants line you can report on every month.

How to Track AI Traffic in GA4, Step by Step

This is the full setup. You need edit access to the GA4 property. The whole thing takes around 30 minutes the first time, and about 10 minutes on every account after that once you save the pattern.

1
Create a custom channel group

In GA4, go to Admin, then Data display, then Channel groups. Click Create new channel group and name it AI Assistants. This is the container that will hold your AI classification rules. It applies going forward from the moment you save it, so the sooner it exists, the more history you build.

GA4 Admin panel showing the Channel groups screen with the Create new channel group button
Admin, then Data display, then Channel groups, then Create new channel group.
2
Add a high-priority AI channel

Inside the new group, add a channel and drag it to the top of the list. Priority matters. GA4 classifies each session using the first rule it matches, so if your AI channel sits below Organic Search or Referral, some AI sessions will be swallowed before they reach it. Name the channel AI Assistants so it reads cleanly in reports.

GA4 channel group editor with a new AI Assistants channel placed at the top of the priority order
Place the AI Assistants channel at the top so it classifies sessions first.
3
Paste the AI referrer regex

Set the condition to Source matches regex and paste a single pattern that catches every major AI referrer at once. This is the one piece I save and reuse on every new account. Here is the pattern:

GA4 condition: Source matches regex
.*(chatgpt|openai|perplexity|claude|gemini\.google|copilot|edgeservices|bard\.google|you\.com|phind|poe\.com|neeva).*

That single line groups chatgpt.com, chat.openai.com, perplexity.ai, claude.ai, gemini.google.com, copilot.microsoft.com, and the other common AI sources into one channel. Review it every quarter, because the tools and their referring domains keep changing.

GA4 channel condition editor with Source matches regex selected and the AI referrer regex pattern pasted in
Condition set to Source matches regex, with the reusable AI pattern in place.
4
Build an Exploration for the history

Custom channel groups do not backfill, so the group only sees traffic from today forward. To read what AI engines have already been sending you, build a free-form Exploration that pulls the full account history. Add Session source as a dimension, filter it to the same AI domains, and layer in Landing page and Engagement rate. This shows which pages AI favors and which tool sends your most engaged visitors.

GA4 free-form Exploration report filtered to AI referral sources, showing landing pages and engagement rate by tool
An Exploration reads full history, so you recover the AI data the channel group cannot backfill.
5
Ship a monthly report the client reads

The data only matters if someone acts on it. I send the same format every month: total AI sessions, share by tool, top AI landing pages, and one insight. Not a dashboard, a story. The goal is that a founder can read it in two minutes and know what to do next. That is what turns tracking into strategy.

Monthly AI traffic report template showing total AI sessions, share by tool, top landing pages, and a single insight
The monthly template: total sessions, share by tool, top landing pages, one insight.

What the Data Actually Shows

Once the system is running, the patterns show up fast. Across the accounts I have set this up on, a few things stay consistent.

5x
One client saw AI traffic convert at nearly 5x their organic rate
10 min
Deployment time per new account once the regex is saved
Quarterly
How often I review the regex as AI tools change

The 5x number is the one that changes behavior. When a client sees that visitors arriving from AI answers convert far better than their average organic visitor, they stop treating AI search as a novelty and start building content for it. One client rebuilt their entire content plan around it after a single monthly report.

The Honest Caveat

What you measure is a floor, not a total. Plenty of AI traffic never passes a referrer and lands in Direct with no label. This system captures the AI sessions that do identify their source, which is a large and growing share, but never all of it. That is fine. A floor you can see beats a number you are guessing at, and the trend line is what drives decisions.

If you want to close more of that gap, the next layer is optimizing the content itself so AI engines cite it in the first place. Tracking tells you what is already working. The optimization work is what grows the number. For that side of the equation, read Claude SEO: How This AI Tool Is Changing SEO in 2026 and How to Audit Content for Answer Engine Readiness.

Tracking vs Optimization: Where This Fits

JobWhat it answersWhere to start
AI traffic trackingHow much AI traffic am I already getting, and from where?This guide
Answer engine optimizationWhy are AI engines citing my competitors and not me?AEO readiness audit
Generative engine optimizationHow do I earn more citations across ChatGPT, Claude, and Perplexity?SEO vs AEO vs GEO
Hiring helpWho can run all of this for my business?Top AI SEO experts

If you are still deciding which discipline you actually need, SEO vs AEO vs GEO breaks down the difference, and if you would rather hand the whole thing off, the top AI SEO experts in India for 2026 covers who does this work well.

Frequently Asked Questions

Yes, but not by default. GA4 buries AI visits inside the generic Referral channel and labels a large share as Direct with no source. To isolate AI traffic you need a custom channel group with a Source matches regex condition that groups chatgpt.com, perplexity.ai, claude.ai, gemini.google.com, and copilot.microsoft.com into a dedicated AI Assistants channel.
Use a single Source matches regex condition such as .*(chatgpt|openai|perplexity|claude|gemini.google|copilot|edgeservices|you.com|phind|poe.com).* which catches the main AI assistant referrers in one pattern. Review it quarterly, because AI tools and their referring domains change frequently.
Many AI assistants strip the referrer when a user clicks through to a website, so GA4 receives no source information and files the visit under Direct. This means any number you measure is a visible floor, not the true total. A custom channel group captures the AI sessions that do pass a referrer, which is still far more accurate than guessing.
No. A custom channel group only applies going forward from the moment you create it. To analyze historical AI traffic you pair the channel group with a free-form Exploration report, which can read the full account history and reveal which pages AI engines have already been sending visitors to.
Review the regex every quarter. New AI assistants launch, domains change, and search products rebrand, so a pattern that was complete three months ago can miss emerging sources. A quarterly review keeps the AI Assistants channel accurate without constant maintenance.

Getting Started

The setup is genuinely quick, and it changes how a business sees AI search overnight. Build the channel group, save the regex, add the Exploration for history, and send one monthly report. Within a month you will know exactly which AI engines send you traffic, which pages they favor, and how well that traffic converts.

If you want this built for your account, or you want a full AEO audit that grows the number instead of just measuring it, you can reach me on Upwork, connect on LinkedIn, or visit The Digital Geek for agency-level engagements.

Anshul Rana, AI SEO, AEO and GEO Specialist
Anshul Rana
SEO, AEO & GEO Specialist | Top Rated Plus on Upwork
I am an SEO, AEO, and GEO specialist with 8+ years of experience helping businesses get found on Google and AI search platforms like ChatGPT, Claude, Gemini, and Perplexity. I hold the Top Rated Plus badge on Upwork (top 3% of freelancers) with a 100% Job Success Score, and I have worked with 1,000+ websites across India, Australia, the US, and the UK. I specialize in technical SEO, answer engine optimization, generative engine optimization, schema markup, and local SEO.