How to Measure AI Search Traffic in Analytics

A client site starts getting cited in ChatGPT responses. Perplexity is linking to their pricing page. Gemini is pulling their FAQ into AI overviews. None of this shows up in their GA4 report as anything other than "direct" or a thin referral line. The agency has no way to quantify the impact, and the client has no reason to keep paying for GEO work they can't see.

Measuring AI search traffic isn't optional anymore — it's the answer to "is this working?"

Why AI Traffic Underreports in Standard Analytics

The fundamental problem: most AI search interactions don't send a referrer header.

When a user asks ChatGPT a question and clicks a cited link, the click originates inside a chat interface. The OpenAI application may strip the referrer (common behavior for cross-origin navigation) or send no referrer at all. The session lands in GA4 as direct. The same issue affects Perplexity on some click paths, Gemini in its embedded answer format, and Microsoft Copilot in most cases.

This means AI search is systematically underreported in every GA4 account right now. The true number is higher than what you can measure, and any methodology you use will produce a floor, not a ceiling.

That said, significant AI traffic does show up as referrals — enough to build a measurement framework around.