When ChatGPT or Perplexity cites you, some readers click through. Those visits arrive with AI referrer hosts and land in your analytics like any other source, if you know where to look. Measuring that AI-referred traffic, and tying it to conversions, is how you prove AI visibility is worth the investment.
Most AI-visibility tools stop at the citation: they tell you that you were mentioned. But a mention is only half the story. AI answers increasingly link out, and those links send real humans to your site. Knowing how many, from which engine, and whether they convert turns a vanity metric into a revenue number. It is the outcome side of the same loop that Search Console reconciliation opens on the input side.
Why AI referral traffic is its own channel
When an AI engine sends a visitor, the session carries a referrer from the engine's own domain: chatgpt.com, perplexity.ai, claude.ai, gemini.google.com, copilot.microsoft.com, and a growing list of others. That makes it a distinct acquisition channel, separate from Google organic and from direct traffic. It is easy to miss because analytics tools often bucket it into a generic "referral" or, when the referrer is stripped, into "direct." Once you name the AI hosts explicitly, a channel you could not see becomes one you can grow.
How to measure it in GA4
Isolate the sessions whose source matches an AI referrer host, then roll them up per engine and per landing page and attach your conversion events. That gives you sessions, conversions, and revenue for ChatGPT, Perplexity, Gemini, Claude, and the rest, page by page. One caveat: treat the number as a lower bound. Some engines open links without a referrer, so a share of AI clicks show up as direct traffic. What you measure is real; the true total is higher.
What AI referral traffic tells you
Read AI traffic against your AI visibility and four patterns emerge, each pointing to a different next move.
| Signal | What it means | What to do |
|---|---|---|
| Rising citations and rising AI sessions | The engine cites the page and readers are clicking through to it. | Working as intended. Keep investing in the pages and prompts that drive it. |
| Rising citations but flat AI sessions | You are cited, but the answer snippet does not compel a click. | Sharpen the on-page hook so the citation earns the visit, not just the mention. |
| AI sessions but low conversion | The engine is sending visitors, but the wrong ones or to a weak page. | Fix the intent match: align the landing page to what the AI answer promised. |
| High conversion from AI traffic | This page turns AI-referred visitors into customers. | Treat it as an exemplar. Mirror its structure on the pages that underperform. |
How to close the loop
Citations get you visibility, referral traffic proves people act on it, and conversions prove it pays. Attributing revenue to AI-referred sessions is what justifies the whole GEO investment, and it points your optimization work at the pages that actually convert. Keep reading: On-Page Optimization for AI · Google rankings vs AI citations
Frequently asked questions
Does ChatGPT actually send traffic to websites?
Yes. When an AI engine cites you and a reader clicks the link, that visit lands in your analytics as a session. AI engines send this traffic from their own referrer hosts, such as chatgpt.com, perplexity.ai, claude.ai, and gemini.google.com. It is a real, growing acquisition channel that sits alongside Google organic, not inside it.
How do I see AI traffic in Google Analytics?
In GA4, segment sessions by their source and isolate the AI referrer hosts (chatgpt.com, perplexity.ai, claude.ai, gemini.google.com, copilot.microsoft.com, and similar). Roll those up per engine and per landing page, then layer conversions and revenue on top. DiscoveredBy automates this: it connects to GA4, classifies AI referrers for you, and reports sessions, conversions, and revenue for each AI engine.
Why is my AI referral traffic under-counted?
Some AI products open links without passing a referrer (for example, ChatGPT increasingly opens links with noreferrer), so those clicks show up as direct traffic instead of AI traffic. Treat measured AI referral traffic as a lower bound: the real number is at least what you see, and often more.
Can I tie AI traffic to revenue?
Yes, and that is the point. Once AI-referred sessions are identified, you attribute your conversion events to them the same way you would any other channel. That turns "we got mentioned" into "AI engines drove this many conversions and this much revenue," which is the number that justifies investing in AI visibility.