All posts
Ray Iyer
Ray Iyer
Co-founder, Anglera

Measuring referral traffic from AI answer engines

How to track referrals from ChatGPT, Perplexity, and Google AI Overviews using GA4, Search Console, and server logs, plus the attribution gaps to stay honest about.

Measuring referral traffic from AI answer engines

There's no clean number for "AI traffic." Anyone who tells you otherwise is rounding off a lot of uncertainty.

What you can get is a defensible, partial view, stitched from three imperfect signals: referrer data, assisted conversions, and branded search lift. Here's how to build it, and exactly where to stop trusting it.

Start with what GA4 can actually see

When ChatGPT, Perplexity, or Copilot hand a user a link, some of those clicks carry a referrer or a utm_source tag.

In GA4, filter Session source/medium for chatgpt.com / referral, perplexity.ai / referral, and similar. Better yet, build a custom channel group with a regex that catches the major platforms in one view, instead of hunting through generic Referral traffic one domain at a time. Google shipped a native "AI Assistant" channel grouping in GA4 in late 2025, but it's not retroactive and it misses a meaningful slice of sources — most practitioners still layer a custom regex group on top of it.

Treat this number as a floor, not a ceiling. It only counts clicks that actually passed a referrer.

Where the trail goes cold

Say this part out loud to your team, because it changes how much weight the number should carry:

  • Referrer stripping. Copy a link out of an AI answer, paste it into a new tab, and no referrer survives the trip. That visit lands in GA4 as Direct. There's no reliable way to reattribute it after the fact.
  • Free-tier gaps. A lot of consumer ChatGPT traffic doesn't pass referrer data consistently, so it also folds into Direct.
  • AI Overviews look identical to organic. Google's AI Overviews and AI Mode results carry the same google.com referrer as a standard blue link. GA4 cannot separate "clicked an AI Overview citation" from "clicked result #3." The closest workaround is matching Google-referred sessions against pages you know were cited recently — inference, not measurement.
  • Search Console's new AI report is impressions-only. Google's Search Generative AI performance report, which launched inside Search Console in June 2026, finally breaks out how often your pages surface in AI Overviews and AI Mode. But it reports impressions only — no clicks, no CTR, no query-level data yet — and the surfaces are blended together rather than split apart. It tells you whether you're showing up. It doesn't tell you what that visibility is worth.

None of this is a reason to give up on the number. It's a reason to pair it with proxies that don't depend on a clean click.

Two proxies that hold up

Assisted conversions. Pull GA4's conversion path reports and look for sessions where an AI-referral touch appears earlier in a multi-session journey that later converts on Direct or branded organic. Buyer hits your PDP from Perplexity on Monday, buys from a Google search on your brand name Thursday — a last-click view credits Google. An assisted-conversion view credits the discovery channel that actually did the work. Segment this by SKU or category, not just site-wide: AI-cited traffic tends to concentrate on a narrow set of well-documented products.

Branded search lift. When a product or brand gets cited consistently in AI answers, more people search for that brand name directly afterward — the same logic advertisers have used for decades to value billboard and TV impressions that can't be clicked. Track branded query impressions and volume in Search Console (and branded search ad spend efficiency, if you run paid) on a rolling basis. Look for a lift that correlates with a period of increased AI citation, not a single spike.

SignalWhat it showsHow to measure itWhat it misses
GA4 referral / channel groupClicks that passed a referrerSession source/medium filter or custom regex channel groupCopy-paste clicks, free-tier stripping
GSC AI performance reportHow often you're citedSearch Console's AI Overviews/AI Mode reportNo clicks, no CTR, surfaces blended
Assisted conversionsMulti-touch influence on a saleGA4 conversion paths, segmented by categoryRequires session stitching to work
Branded search liftAwareness building into demandBranded query volume/impressions over time in GSCConfounded by other marketing activity
Server log analysisWhether AI crawlers can even read your dataFilter access logs by user-agent (bot names for major AI crawlers)Crawl activity, not human traffic — most crawls are indexing or training, not click-driven

That last row matters more than it sounds. Server logs will show AI crawlers hitting your catalog pages constantly — far more often than they ever send you a human visitor. That volume tells you whether your product data is legible enough to be picked up and cited. It does not tell you how many people clicked through. Conflating the two is one of the most common measurement mistakes right now.

Keep the number honest and small

Recent analysis of enterprise site traffic puts AI referral traffic at roughly 1% of total sessions in 2026 — a real jump from a year earlier, still a fraction of what organic search alone drives. Analytics Mania's guidance on GA4 tracking is blunt about the ceiling on this data: "not all AI-driven exposure results in trackable traffic, so what you see in GA4 will always be a partial view." Build your dashboard around that sentence.

Treat AI referral traffic as one line in a broader discovery report, next to organic search, on-site search, and marketplace traffic — not a channel that gets its own war room. Watch the trend line, not the absolute number:

  • Is the AI-referral segment growing session over session?
  • Do those sessions convert at a comparable rate to organic once they land?
  • Is branded search moving in the same direction?

If all three point the same way, you have a real signal, however incomplete the click-level picture stays.

Why this connects back to product data

Every one of these signals — a clean citation, an assisted conversion, a branded search — starts with a PDP that's complete enough to be quoted accurately and specific enough to answer the question the buyer actually asked.

Your PIM stores that data. Whether it's accurate, current, and structured well enough to survive being pulled out of context by an AI answer is a separate, ongoing job. Anglera does that work continuously, so when the referral finally shows up in your reporting, the product it lands on is ready to convert.

Ray Iyer

About the author

Ray IyerCo-founder, Anglera

Ray is a co-founder of Anglera, building the product-data infrastructure for agentic commerce — turning messy catalogs into structured, AI-readable data that buyers and answer engines can find. Previously product at Uber; Stanford CS.

See it on your own SKUs.

A 30-minute walkthrough on your categories and your supplier data.

Book a demo