AI traffic analytics
Measuring the sessions AI engines send to a store — and, where the data allows, connecting each visit back to the prompt and citation that drove it.
Last updated June 2026
The two data streams
Stream one is referrer data: when an AI answer contains a link and the user clicks it, the referring URL sometimes identifies the engine — chatgpt.com referrals appear in GA4, Perplexity sends referrers on some surfaces and not others, and Google AI Overviews clicks mostly blend into Google organic because they still route through google.com, as of mid-2026. See Google's GA4 channel documentation for how referral grouping works.
Stream two is prompt-tracking data: which prompts cited which PDPs in a given week. Pairing the streams produces probable attribution — "this traffic lift on the serum PDP correlates with ChatGPT starting to cite it on the 'best serum for curly hair' prompt." Probable, labeled as such, and still decision-grade.
Why it matters for ecommerce
A VP allocating budget needs a defensible answer to "is AI search worth investing in." AI traffic analytics produces that number — imperfect but directional — and watching it rise week over week is the evidence that PDP work converts to sessions, not just to visibility scores.
It also surfaces a conversion pattern worth knowing: AI-referred visitors often arrive deeper in the funnel than search-referred visitors, because the answer already did part of the education. Where referrers are measurable, conversion rates on AI referrals frequently run higher — a pattern eCommerce Insights has observed across tracked D2C catalogs to date, worth validating on your own data rather than assuming.
Attribution in practice: an example
A merino base-layer brand sees weekly AI-referred sessions rise from 180 to 440 over eight weeks (illustrative figures). Cross-referencing prompt runs, the team finds ChatGPT began citing the zip-neck midweight in January for "best merino base layer for skiing," and GA4 shows that PDP receiving most of the AI-referred sessions the same weeks. The attribution is not airtight — uncited influence and blended AI Overviews clicks are invisible — but it is specific enough to justify doubling down on the adjacent prompt cluster.
The honest limits
Three gaps to keep in reporting footnotes: engines influence purchases without sending clicks (the shopper reads the answer and searches the brand directly); referrer coverage varies by engine and changes without notice; and AI Overviews traffic is mostly indistinguishable from classical Google organic in standard setups. The metric is a floor on AI influence, not a ceiling — which is exactly how to present it to a board.
How eCommerce Insights handles it
Citation events from prompt tracking are timestamped per SKU, designed to sit next to GA4's referral data so the correlation work is a join, not a hunch. The ROI calculator turns the resulting estimates into a labeled, conservative revenue model.
Related terms
- Prompt tracking — the citation stream that pairs with referrer data.
- AI visibility — the upstream metric traffic eventually validates.
- Citation analysis — explains which citations drive the clicks.
- Share of voice (AI) — the competitive context for traffic share.
- Product AI visibility — the per-SKU view traffic data confirms.
Ask AI about AI traffic analytics
Have your preferred AI engine summarize this definition for your catalog.
Frequently asked questions
Can GA4 show me traffic from ChatGPT?
How do I attribute AI traffic to specific prompts?
Is AI referral traffic actually worth anything yet?
Why does my AI visibility rise but traffic stay flat?
Go deeper
- Track AI referral traffic in GA4 — the setup walkthrough.
- Prove AI search ROI to leadership — turning the data into a budget case.
- AI search ROI calculator — a conservative, labeled revenue model.
- SKU-level tracking — the citation timestamps that make attribution joinable.
See where every product in your catalog stands on this. Start a 14-day free trial — no credit card — or grade one PDP free in 30 seconds.