How to track AI traffic from ChatGPT & Claude
A growing share of your visitors no longer start at Google. They ask ChatGPT, Perplexity or Claude a question, get an answer with links, and click through to your site. Those are real, high-intent visits — and in most analytics tools, you can’t see them. This guide explains why AI traffic is invisible by default, and how to track it as its own channel.
Why AI traffic hides in your analytics
When someone clicks a link inside an AI assistant, one of two things usually happens. Either the referrer is stripped entirely — so the visit lands in your direct bucket, next to people who typed your URL — or it shows up as a bare domain like chatgpt.com buried among dozens of other referrers you never group together.
Analytics tools built for the search era assume traffic comes from search engines, social networks and links. They don’t have a concept of “AI assistant” as a channel, so a fast-growing, high-converting source gets scattered into noise. You can’t optimize for what you can’t measure.
What counts as AI traffic
AI traffic is any visit referred by a large-language-model assistant. The ones that matter today:
- ChatGPT — by far the largest, and its links convert unusually well
- Perplexity — an answer engine that cites and links sources heavily
- Claude — increasingly used for research with web access
- Gemini — Google’s assistant, folded into more surfaces over time
These visitors arrive with intent: they just asked a question and were recommended you. That makes AI traffic worth isolating, not lumping into “direct.”
How to track it as its own channel
The manual route is to build referrer rules — grouping the assistant domains into a custom channel in whatever tool you use. It works, but it’s brittle: the domains change, new assistants appear, and you have to maintain the rules by hand in a UI that wasn’t built for it.
The simpler route is to use analytics that treats AI as a first-class channel. Satsu classifies referrals from ChatGPT, Perplexity, Claude and Gemini into a dedicated AI channel automatically, split per assistant, right next to organic and direct — with no cookies and no consent banner. If Satsu is installed, AI traffic simply appears; there’s nothing to configure.
What to do with the data
Once AI traffic is its own channel, you can answer questions that were invisible before: which assistants send you the most visitors, which of your pages get cited inside them, and whether the content you publish is actually surfacing in the tools people now ask first. That’s the feedback loop for the next era of organic traffic — and it starts with being able to see the channel at all.
Start free and see your AI traffic in minutes — no card, no cookie banner. Or read how Satsu compares to Google Analytics.