To track ChatGPT traffic in GA4, start with the built-in AI Assistant channel in the default channel group, which Google Analytics now uses for visits from assistants such as ChatGPT, Gemini and Claude. If an assistant you care about isn’t covered, add a custom channel group with a regex on Source and place it above Referral. Either way, treat the result as a floor: some AI visits arrive without a referrer and land in Direct.
A buyer who asks “best CRM for a 20-person startup” and clicks through to your pricing page is a qualified visit, but by default it may sit in Referral next to a partner blog. This guide covers three ways to isolate AI referrals in GA4, the reports that complete the picture, and what GA4 can’t tell you.
Key takeaways
- GA4’s default channel group now includes an AI Assistant channel for visits from assistants such as ChatGPT, Gemini, DeepSeek, Copilot and Grok.
- Google AI Overviews and AI Mode are excluded from the AI Assistant channel and stay in Organic Search.
- A custom channel group with a Source regex covers assistants that the default list may miss, and it can be applied to past data.
- Referrer data is incomplete, so any AI traffic figure in GA4 is a minimum, not a total.
- Clicks are only part of the story: many AI answers mention your brand without anyone clicking.
Why AI traffic hides in Referral, Direct and Unassigned
Before the AI Assistant channel existed, a visit from chatgpt.com usually showed up as Referral, mixed with every other site that links to you. That still happens for any assistant GA4 doesn’t recognize.
Other AI visits never carry a referrer at all. Links opened from desktop or mobile apps, copied and pasted URLs, and strict referrer policies can all strip it, and GA4 then files the session under Direct. Nothing in GA4 can recover that source after the fact.
A third group can fall into Unassigned. ChatGPT adds utm_source=chatgpt.com to links in its answers, according to OpenAI’s publisher FAQ. A tagged source with no medium may not match any channel rule, and Unassigned is the value GA4 uses when nothing matches.
Option 1: Use GA4’s built-in “AI Assistant” channel
The fastest route needs no setup. Google’s default channel group documentation defines AI Assistant as the channel for users arriving “from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok”. When the referrer matches Google’s list of assistants, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant).
To see it:
- Open Reports > Acquisition > Traffic acquisition.
- Keep the primary dimension on Session default channel group.
- Look for the AI Assistant row, then add Session source as a secondary dimension to split it by assistant.
What it includes and what it excludes
The help page names example sources rather than a full list, and links to a downloadable list of the sources GA4 recognizes. Check that list for the assistants your buyers use. If one is missing from your reports, Perplexity for example, its visits keep landing in Referral.
The exclusion matters more. Per the same page, the AI Assistant channel “excludes Google’s AI Overviews and AI Mode”. Clicks from those features are counted in Organic Search, with no separate flag in GA4. Our guide to Google AI Overviews traffic covers how to read their impact in Search Console instead.
Option 2: Build a custom channel group with regex
A custom channel group lets you define AI traffic yourself, catch sources the default list may miss, and keep a definition you control. Google’s custom channel groups guide gives the steps, and notes that custom groups can be applied to reports retroactively.
- Go to Admin > Data display > Channel groups.
- Click Create new channel group. This starts from a copy of the default group.
- Name it, for example “Channels with AI”.
- Click Add new channel, name it “AI assistants”, then + Add condition group.
- Choose the dimension Source, the match type matches regex, and paste the regex below.
- Click Save channel.
Copy-paste regex for AI sources
.*(chatgpt|openai|perplexity|claude\.ai|gemini\.google|copilot\.microsoft|deepseek|grok\.com|mistral\.ai|meta\.ai).*
It matches sources such as chatgpt.com, chat.openai.com, perplexity.ai, claude.ai, gemini.google.com, copilot.microsoft.com, chat.deepseek.com, grok.com, chat.mistral.ai and meta.ai, while leaving google.com and bing.com alone. The leading and trailing .* make it work whether GA4 evaluates the pattern as a full or partial match. Channel definitions aren’t case sensitive.
Test it before you rely on it. In a Traffic acquisition report, filter Session source with the same regex and scan the matched values for anything that isn’t an assistant. Assistant domains change, so review the list every few months.
Put it above Referral
GA4 assigns each session to the first channel it matches, so order decides the outcome. Click Reorder, drag “AI assistants” above Referral, click Apply, then Save group. If you leave it below Referral, chatgpt.com visits will keep landing in Referral and your new channel will look empty.
Standard properties allow two custom channel groups, so spend one deliberately.
Option 3: An Exploration report for AI landing pages
Channels tell you how much AI traffic arrives. An Exploration tells you where it lands.
- Go to Explore and start a Blank exploration.
- Add the dimensions Session source and Landing page + query string.
- Add the metrics Sessions, Engaged sessions and Key events.
- Add a filter: Session source matches regex, using the regex above.
- Drag Landing page into rows and Session source into columns.
In our CRM example, you might find that most AI visits land on a comparison or pricing page rather than the homepage. Those are likely the pages assistants cite, and the ones that deserve the most care.
Beyond GA4: Search Console, Bing and UTM tags
GA4 sees visits. Other tools see the other side of the funnel.
| Tool | What it shows for AI | What it doesn’t show |
|---|---|---|
| GA4 AI Assistant channel | Sessions from recognized assistants | AI Overviews, AI Mode, visits with no referrer |
| GA4 custom channel group | Sessions matching your own regex | Visits with no referrer |
| Search Console | AI Overviews and AI Mode, counted inside the “Web” search type | A separate AI filter |
| Bing Webmaster Tools AI Performance | How often your pages are cited in Copilot and Bing AI answers | Clicks |
utm_source=chatgpt.com |
ChatGPT links that kept their UTM tag | Untagged or stripped links |
Google’s AI features documentation confirms that AI Overviews and AI Mode appear in the Performance report under the “Web” search type. Bing’s AI Performance report, in public preview since February 2026, counts citations rather than clicks.
Why traffic is only half the story
Many AI answers are complete on their own. A buyer can read a shortlist of three CRMs, pick one, and never click. If you’re on that shortlist, GA4 records nothing. If you’re not, GA4 won’t show you what you lost.
That is why AI traffic and AI visibility need separate metrics. Traffic tells you which answers led to a visit. Visibility tells you how often you are mentioned at all, next to which competitors, and which sources the assistant relied on. Our article on AI share of voice explains how to measure the second half, and tracking your brand across AI assistants shows how to set it up. When you’re ready to improve the numbers, see how to rank in ChatGPT.
Measure the answers behind the clicks with Citegram
Citegram does not connect to GA4 and does not measure traffic, clicks or conversions. It covers what GA4 can’t see: what the assistants say.
- Add the prompts your buyers ask, such as “best CRM for a 20-person startup”.
- Run them in the real apps. The Chrome extension asks each prompt in ChatGPT, Gemini, Perplexity, Claude, DeepSeek, Grok and Google AI Overviews, in background tabs, using the accounts already signed in to your browser. There’s no API key, and questions count toward your own plan usage.
- See whether you’re mentioned and where. Citegram records whether your brand appears, its position, and the sources and links each answer cited.
- Compare with your GA4 landing pages. If a page shows up in your AI landing page exploration, check whether assistants cite it for your prompts. If they cite a competitor’s page instead, that’s your gap.
- Track it over time. Reports show share of voice per brand and per assistant, the most cited domains, and trends over repeated runs.
Answers come from your own accounts, so personalization, memory and location can affect them. Run prompts more than once before drawing conclusions.
FAQ
Why does ChatGPT traffic show as direct in GA4?
Some ChatGPT visits arrive without a referrer, for example when a link is opened from an app or copied and pasted. GA4 then has no source to read and records the session as Direct. That’s why AI traffic figures in GA4 are a minimum, not a full count.
Can I see which prompts sent the traffic?
No. GA4 receives the referring domain, not the conversation, so prompts are never visible in your analytics. To understand which questions mention you, run the prompts yourself in each assistant and record the answers.
Does GA4 track Google AI Overviews clicks separately?
No. Google’s documentation says the AI Assistant channel excludes AI Overviews and AI Mode, and those clicks are counted in Organic Search. In Search Console, they are included in the “Web” search type of the Performance report.
How much traffic does ChatGPT send to websites?
It varies widely by industry, content type and how often assistants cite your pages. Rather than relying on someone else’s average, measure your own baseline with the AI Assistant channel or a custom channel group, knowing it undercounts.
Measure the answers, not just the clicks
GA4 shows the visits AI sends you. Citegram shows the answers behind them, including the ones nobody clicked. The free plan tracks one prompt across all major assistants, forever. Pro adds unlimited prompts for $10 a month. See pricing.


