How to see ChatGPT and Perplexity referral traffic
On this page
AI referral traffic is the segment of human visitors who land on your site after clicking a link or citation inside an AI assistant’s answer. Someone asks ChatGPT for the best project management tools, ChatGPT names yours and links it, the person clicks, and that click arrives on your site carrying a referrer like chatgpt.com. It is a small slice of total volume today, under 1% for most sites, but it converts far better than the average visit because the assistant has already pre-qualified the person before they ever reach you. The volume is also climbing fast: Adobe measured traffic to US retail sites from generative AI sources jumping 1,200% between July 2024 and February 2025, with those visitors browsing 12% more pages per visit and bouncing 23% less than other sources.
The problem is that this traffic is genuinely hard to see. Assistants often send no referrer at all, so the visit gets bucketed as Direct. Analytics tools bury the referrers that do arrive inside a long list of other domains. And most guidance blurs two completely different things: AI crawlers fetching your pages to train or ground a model, and AI-referred humans arriving from an answer. This guide gives you the exact hostnames, the GA4 setup, and the measurement traps, so you can actually see and separate both.
AI crawlers and AI referrals are two different signals
An AI crawler is a bot that fetches your pages; an AI referral is a human who arrives after reading an answer. Conflating them is the single most common mistake in this area, and it produces numbers that mean nothing.
When GPTBot, ClaudeBot, PerplexityBot, or Google-Extended requests a URL, that is a server-side event. It usually never touches your JavaScript analytics because bots do not execute your GA4 tag, so it shows up only in raw server logs or a log-based tool. That crawl activity tells you whether AI systems can read your content. If you want to understand who is fetching your pages and how to verify them, start with how bots identify themselves in our guide to GPTBot and the major AI crawlers, and the broader techniques for spotting bot traffic in your server logs.
An AI referral is the opposite: a real browser, a real person, a real session that fires your analytics tag and carries a referrer pointing back to the assistant. This is demand, not indexing. The crawl number tells you if you are eligible to be cited; the referral number tells you whether being cited is sending you people. You need both, and you need to keep them in separate columns. A platform that maps AI-referral traffic to a distinct channel while keeping crawler hits in their own bucket, like the AI-referrals view in Lume, removes the guesswork of trying to split them by hand.
The referrer hostnames that identify AI assistants
Each assistant sends visitors from a specific set of hostnames, and knowing them exactly is the whole game. When an AI referral does pass a referrer, it matches one of the domains below. Match on these and you capture the traffic; miss one and it silently falls into Direct or Referral without a label.
| AI assistant | Primary referral hostname(s) | Notes |
|---|---|---|
| ChatGPT | chatgpt.com | Legacy chat.openai.com still appears; iOS/Android apps may send com.openai.chat or no referrer |
| Perplexity | perplexity.ai, www.perplexity.ai | Its Comet browser and mobile apps often arrive refererless |
| Google Gemini | gemini.google.com | Older answers may carry bard.google.com |
| Microsoft Copilot | copilot.microsoft.com | Copilot inside Bing can also surface as bing.com or www.bing.com |
| Claude | claude.ai | Citations in Claude answers link out with this referrer |
| Grok | grok.com, x.com | In-app clicks from X frequently strip the referrer |
| Meta AI | meta.ai | In-app assistant traffic is largely refererless |
| DeepSeek | chat.deepseek.com | |
| You.com | you.com | |
| Brave (Leo / Search) | search.brave.com | |
| Mistral Le Chat | chat.mistral.ai | |
| Poe | poe.com | Aggregator fronting several models |
One critical exception belongs in its own line. Google AI Overviews and AI Mode clicks do not arrive as a separate AI referrer. They come through as ordinary google / organic traffic, because the click still originates on a Google search results page. You cannot isolate AI Overviews referrals in standard GA4 today; you can only track the standalone assistants above. If your strategy depends on Overviews, treat it as part of your organic search work and focus your citation efforts there, which is exactly what getting cited in AI Overviews and ChatGPT is about.
Why so much AI referral traffic hides in Direct
AI referral traffic gets misfiled as Direct whenever the assistant fails to pass a referrer header, and this happens far more often than with normal web links. GA4 assigns a session to Direct when it arrives with no identifiable source, which is exactly what a missing referrer produces. There are three concrete causes.
First, native apps. A large share of ChatGPT, Perplexity, Gemini, and Meta AI usage happens inside a phone app rather than a browser tab. When a link opens from an app, there is frequently no HTTP referrer to send, so the visit is indistinguishable from someone typing your URL directly.
Second, referrer policies and privacy stripping. Some assistants set a restrictive Referrer-Policy or route clicks through a redirector that drops the original source. The browser then hands your server an empty referrer.
Third, in-app browsers and link previews. When a link opens in an embedded webview, referrer behavior is inconsistent across platforms and often blank.
The practical consequence is that your reported AI referral number is a floor, not a ceiling. Real AI-driven demand is higher than the labeled sessions suggest, and a chunk of your “Direct” growth over the past year is very likely uncredited AI traffic. This is also why looking only at referrers misses part of the picture, and why server-side signals matter. Watching which pages AI systems crawl, then correlating that with Direct spikes on the same URLs, gives you a second line of evidence that a page is earning AI attention.
Set up an AI referrals channel in GA4
You can make GA4 report AI assistants as their own channel with a custom channel group, so every AI referral is labeled consistently across your reports. This is the durable version; a report-level filter is the quick version.
For the persistent setup, go to Admin, then Channel groups, and create a new custom channel group. Add a channel called “AI referrals” and give it a condition where Source matches this regex:
^(chatgpt\.com|chat\.openai\.com|openai\.com|perplexity\.ai|gemini\.google\.com|bard\.google\.com|copilot\.microsoft\.com|claude\.ai|grok\.com|meta\.ai|chat\.deepseek\.com|you\.com|search\.brave\.com|chat\.mistral\.ai|poe\.com)$Order that channel above Direct and Organic Search so AI sessions are claimed before they fall through to a broader bucket. New channel groups apply going forward and to recent data, but they do not rewrite your entire history, so set this up early.
For a fast look without changing configuration, open Reports, then Acquisition, then Traffic acquisition, add a filter or comparison on Session source, and paste the same domains. You can also build an Exploration with a segment on those referrers to slice AI-referred users by landing page, conversions, and revenue. Landing page is the most actionable dimension here, because it tells you which content the assistants are actually citing, which feeds directly back into your generative engine optimization work.
A few things to keep clean. Add www. variants where a platform uses them, keep the list updated as new assistants launch, and remember that GA4’s default channel grouping will not catch any of this on its own. Out of the box, GA4 files chatgpt.com under Referral with no AI label at all, which is why almost nobody sees their AI traffic until they build the group above.
Turn AI referral data into decisions
Seeing the traffic is step one; the point is deciding what to do with it. Once your AI referrals channel is populated, three questions become answerable.
Which assistants send you people? For most sites ChatGPT dominates AI referrals by a wide margin, but the mix varies by audience and topic, and you should not optimize for a single engine on the assumption that the rest do not matter. Check your own split before you allocate effort.
Which pages get cited? Sort AI referrals by landing page. The URLs that already earn AI clicks show you the format and depth these systems prefer, and they are your template for the next round of content. If a page you care about earns crawls but no referrals, the content is reachable but not compelling enough to cite, which is a content problem, not a technical one. Our playbook for optimizing a site for AI search covers the structural moves that make a page more citable.
How valuable is this traffic? Compare conversion rate and revenue per session for your AI referrals channel against organic and direct. Many sites find AI-referred visitors convert several times better than their average, because the assistant has already done the persuading. That ratio is the argument for investing in AI visibility, and it is the number worth reporting to stakeholders. If you own SEO for the business, this data belongs alongside your organic reporting, and our resources for SEO teams frame how the two fit together.
Because AI referrals and AI crawls tell different stories, the strongest setup keeps them side by side rather than merged into one “AI traffic” figure. Lume does this by classifying every request, separating verified AI crawlers from AI-referred human sessions, so you can see both the demand arriving from assistants and the bots fetching your pages without stitching two tools together.
Frequently asked questions
What is AI referral traffic?
AI referral traffic is human visitors who reach your website by clicking a link or citation inside an AI assistant’s answer, such as ChatGPT, Perplexity, Gemini, or Copilot. It is measured in browser analytics as sessions carrying a referrer from those assistant hostnames. It is distinct from AI crawler activity, which is bots fetching your pages and usually does not appear in your analytics at all.
What referrer does ChatGPT traffic show?
ChatGPT referral clicks typically arrive with the referrer chatgpt.com, and some older or edge-case sessions still show chat.openai.com. Clicks from the ChatGPT mobile app frequently carry no referrer, so a share of genuine ChatGPT traffic lands in the Direct bucket instead.
Why does my AI traffic show up as Direct in GA4?
AI assistants often send no referrer header, especially from native apps, restrictive referrer policies, and in-app browsers. With no referrer, GA4 cannot attribute the session to a source and files it as Direct. This means your labeled AI referral number is a floor; the true figure is higher.
Can I track Google AI Overviews referrals separately?
No. Clicks from Google AI Overviews and AI Mode arrive as ordinary Google organic traffic, because the click still originates on a Google search results page. Standard analytics cannot isolate them today. You can only track the standalone assistants like ChatGPT, Perplexity, Gemini, Copilot, and Claude by their referrer hostnames.
Is AI referral traffic the same as AI crawlers hitting my site?
No, and treating them as one number is the most common mistake. AI crawlers such as GPTBot and PerplexityBot are bots that fetch your pages and show up in server logs, telling you whether AI systems can read your content. AI referrals are humans arriving from answers, telling you whether being cited sends you people. Keep them in separate columns.
How do I know which pages AI assistants are citing?
Segment your AI referrals channel by landing page. The URLs receiving AI referral clicks are the pages assistants are currently citing and linking. Pages that get AI crawls but no referrals are readable but not being cited, which points to a content and structure fix rather than a technical one.