AI traffic attribution is the practice of identifying which website visits, signups, and revenue originate from AI assistants and answer engines — ChatGPT, Perplexity, Claude, Copilot, Gemini — rather than from search engines or social media. Because many AI tools strip or obscure referrer data, this traffic is frequently misclassified as “direct.”
The difficulty is technical. When a user clicks a link in an AI answer, the visit may carry a referrer header (identifying, say, perplexity.ai), a UTM parameter the engine appends (ChatGPT tags many outbound links with utm_source=chatgpt.com), both, or neither. Behavior differs by engine, by surface (web app versus mobile app), and over time as engines change their link handling. Visits that arrive with no referrer and no UTM land in the analytics “direct” bucket, indistinguishable from a typed-in URL — which is why a site can receive substantial AI-driven traffic while its dashboard shows none.
Attribution approaches form a ladder. The baseline is configuring existing analytics — custom channel groups in GA4 that match known AI referrer domains and UTM sources — which recovers traffic that self-identifies. A step up is first-party detection: a script on the site that classifies each session using referrer, UTM, and other request signals, catching cases generic channel groupings miss. The most useful layer ties attribution to outcomes — connecting AI-sourced sessions to signups, activations, and revenue — because visit counts alone cannot say whether AI answers send buyers or the merely curious.
AI traffic attribution is distinct from AI visibility monitoring, its complement: visibility tools ask engines questions and record which brands get mentioned, measuring presence in answers; attribution measures what happens after the click, on your own property. Mentions without traffic suggest visibility that is not converting into action; traffic without mentions usually means your monitoring prompts do not match what users actually ask.
Channel decisions follow measurement. If AI-sourced visits are invisible — filed under “direct” — a founder will systematically under-invest in the content and community presence that answer engines reward, and misattribute those conversions to other channels. The reverse error costs money too: chasing AI visibility without attribution means never learning whether the engines send buyers or tourists. For SaaS specifically, the interesting question is rarely traffic volume (AI referrals are typically modest) but conversion quality: AI-referred visitors arrive pre-qualified by an answer that already explained the product. You can only discover that — and act on it — if the attribution exists.
AI referral traffic is website traffic that arrives through links in AI-generated answers — when an assistant or answer engine cites or recommends a site and the user clicks through. It is typically identified by referrer domains such as chatgpt.com or perplexity.ai, or by UTM parameters some engines append to outbound links.
Dark traffic is website traffic whose true source analytics tools cannot identify, so it is lumped into the “direct” bucket. Common causes include stripped referrer headers and links opened from apps, messaging tools, email clients, documents — and, increasingly, AI assistants. It inflates “direct” visits and hides which channels actually drive results.
Generative engine optimization (GEO) is the practice of making a brand or website more likely to be cited, quoted, or recommended in answers produced by AI systems such as ChatGPT, Perplexity, Gemini, and Google's AI Overviews. It adapts SEO thinking for engines that synthesize answers rather than rank lists of links.
In practice
SubredditSignals does this with one line of first-party tracking code: it detects visits from each AI engine — by referrer and by UTM — and ties them to signups and revenue, not just pageviews.
Set up AI traffic attribution