AI assistants pass regular referrer headers on most clicked citations, so GA4 already records your ChatGPT and Perplexity traffic — it's just scattered across the referral bucket. Finding it takes one filtered report; making it permanent takes one custom channel group. Here's both, plus the blind spots GA4 can't cover.
Quick check: find AI referrals in two minutes
- In GA4, open Reports → Acquisition → Traffic acquisition.
- Change the primary dimension to Session source / medium.
- In the search box, try each of these sources:
| Source | Assistant |
|---|---|
chatgpt.com | ChatGPT (older visits may show chat.openai.com) |
perplexity.ai | Perplexity |
gemini.google.com | Google Gemini |
claude.ai | Claude |
copilot.microsoft.com | Microsoft Copilot |
you.com | You.com |
Anything you find is a human who saw your site cited in an AI answer and clicked through — the end result the whole GEO effort is aimed at.
Make it permanent: a custom "AI" channel group
Searching source names works, but you want AI traffic as a first-class channel next to Organic Search and Direct:
- Go to Admin → Data settings → Channel groups and click Create new channel group (this copies the default group — custom groups don't alter your existing data).
- Add a new channel, name it
AI Assistants, and define the condition as Source matches regex:
.*chatgpt\.com.*|.*openai\.com.*|.*perplexity\.ai.*|.*gemini\.google\.com.*|.*claude\.ai.*|.*copilot\.microsoft\.com.*|.*you\.com.*
- Drag the channel above Referral in the priority order — channel rules apply top-down, and you want AI sources claimed before the generic Referral rule catches them.
- Save. In any traffic report, switch the dimension to your new channel group and
AI Assistantsappears as its own row, trendable over time.
Review the regex monthly: new AI surfaces ship constantly, and each arrives with a new referral domain.
Build an AI traffic report you'll actually look at
With the channel group in place, two views earn their place:
- Explore → Free form: dimension = Landing page, metric = Sessions, filter = your AI channel. This shows which pages AI assistants cite — your GEO scoreboard. Pages winning AI citations are the pattern to replicate; pages you expected to be cited but aren't are the ones to restructure (run them through the AI-Readiness Audit to find out why).
- Same report, compare engagement: AI-referred visitors arrive pre-qualified — an assistant already matched them to your content. If their engagement beats your site average (it usually does), that's your evidence that GEO traffic is worth the effort.
The blind spots GA4 cannot see
Two big ones — worth understanding so you don't misread your numbers:
1. Missing referrers. Mobile apps and desktop clients of AI assistants frequently open links without a referrer header. Those sessions land in Direct. If Direct traffic climbed in the same period your content started getting cited, some of that is unattributed AI traffic. Treat GA4's AI referral count as a floor.
2. Crawlers are invisible. GA4 only records browsers that run its JavaScript. GPTBot, PerplexityBot, ClaudeBot and every other AI crawler fetch your pages without executing scripts — so the crawling side of the AI pipeline (the part that determines whether you can be cited) never appears in GA4 at all. That data lives in your server access logs. Paste a log file into the AI Bot Log Analyzer and it counts hits per AI bot with per-path breakdowns, entirely in your browser; the full log-checking guide covers where to find your logs on common hosts.
Reading the two datasets together
The full picture needs both sources, and the combination is diagnostic:
- Crawler hits but no referrals: AI systems read you but don't cite you — a content problem. Your pages aren't extractable or authoritative enough to be chosen. Start with answer-first structure.
- Referrals but few crawler hits: you're being cited from search-partner indexes rather than direct crawls — fine, but check nothing is blocking the crawlers that would deepen your coverage.
- Neither: the pipeline is broken at the access layer. Check robots.txt, then work through why your site isn't in ChatGPT answers.
- Both, growing: your GEO flywheel is turning. Double down on the landing pages winning citations.