Technical Guide
AI engines are now a meaningful traffic source for SaaS and ecommerce sites — and most analytics tools are blind to them. This guide explains why GA4 misclassifies AI referrals as Direct, how document.referrer actually works for AI traffic, and how to connect AI engine visits to real revenue events.
In January 2026, Similarweb reported that ChatGPT had surpassed 180 million monthly active users, with a growing share actively clicking through to external websites from AI-generated answers. Perplexity, which positions itself explicitly as a research engine with citations, generates outbound clicks as a core product feature. Claude and Gemini are following the same model.
For SaaS founders and ecommerce operators, this creates a specific problem: a new traffic channel with potentially high purchase intent is arriving at your site and your analytics tool is recording it as Direct traffic. You cannot optimize a channel you cannot see.
According to SparkToro research on AI referral patterns, sites in technical niches — developer tools, B2B SaaS, specialized equipment — are seeing AI engine referrals represent 5–15% of inbound traffic, and the share is growing month over month. For the average consumer site the share is lower, roughly 1–3%, but still non-trivial given the conversion quality.
A user arriving from a Google search result may be researching broadly. A user arriving from a ChatGPT citation arrived because an AI explicitly recommended your product in response to a question like "what is the best analytics tool for Stripe businesses?" That recommendation narrows intent dramatically. Early adopter data from Attrifast users shows AI-referred visitors converting to paid customers at 2–4x the rate of organic search visitors.
Estimated distribution of AI-originated web referrals, early 2026. Based on aggregated referrer data across Attrifast-tracked sites and corroborating Similarweb AI traffic reports.
ChatGPT dominates referral volume. Perplexity punches above its user-count because citations are a core product feature. Claude and Gemini are growing fastest quarter over quarter.
When a user clicks a link inside an AI chat interface, the browser sends an HTTP Referer header to the destination server — the same mechanism that has powered web analytics since the mid-1990s. On the client side, your JavaScript can read this as document.referrer.
https://chatgpt.com/or chat.openai.com for older linkshttps://perplexity.ai/consistent across all citation typeshttps://claude.ai/present on all outbound clickshttps://gemini.google.com/distinct from google.com organicIf the AI engine sets a Referrer-Policy of same-origin or no-referrer on its outbound links, the browser will not send the referrer header to cross-origin destinations. ChatGPT and Perplexity currently use unsafe-url or origin-when-cross-origin, which preserves the referrer. This can change at any time.
Some AI engines route clicks through intermediate redirect pages for security or tracking. If that redirect page lacks a Referrer-Policy that passes the original referrer, the destination site sees the redirect URL as the referrer instead. This is the most common cause of Perplexity AI traffic appearing as Direct in some analytics tools.
GA4 maintains a list of 'referral exclusions' — domains that should not start new sessions. Google's own domains are excluded to prevent organic search sessions from being overwritten by subsequent Google clicks. AI engine domains are not on this list, but GA4's session model often fails to attribute the correct source when a user visits multiple pages within the same session, defaulting to Direct.
The same 100 visitors, two different views. GA4 collapses everything into Direct. Proper AI traffic attribution breaks out each source and ties it to revenue.
AI traffic from ChatGPT, Perplexity, and Claude is invisible. You cannot act on data you cannot see.
Each AI source is visible with its own conversion rate and revenue contribution.
GA4, Plausible, Fathom, and Attrifast — how each handles AI engine referrers and revenue attribution.
No
No
All AI traffic appears as Direct/(none)
Yes
No
Shows referrer domain but no revenue data
Yes
No
Shows referrer domain but no revenue data
Yes
Yes
AI source → session → Stripe payment linked
Attrifast captures document.referrer at the start of every session and stores it server-side with a privacy-safe session token. When a Stripe payment completes, it joins the payment record back to that original session — including its AI engine referrer. Here is the full setup flow.
Paste a single 4 KB script tag into your site's <head>. No configuration needed — the tracker automatically reads document.referrer on every page load.
One-click OAuth connection. Attrifast matches browser sessions to server-side payment events using a privacy-safe session token — no cookies, no PII stored.
ChatGPT, Perplexity, Claude, and Gemini referrals appear as distinct channels. Each row shows visitors, conversion rate, and revenue generated.
Click any AI source to see the exact pages visitors landed on, their conversion rate versus your organic average, and total revenue attributed.
Within 24 hours of installation, AI traffic sources appear as named channels: ChatGPT, Perplexity AI, Claude AI, Gemini. Each row shows sessions, conversion rate, revenue generated, and revenue per visitor. You can sort by revenue to immediately see which AI engine produces the highest-value customers for your business.
No consent banners are required. Attrifast is cookieless by design and GDPR-compliant without needing to ask users for permission — important for technical audiences who are most likely to dismiss consent dialogs.
SEO took years to become a mature discipline. Social media analytics tooling lagged platform growth by two to three years. The pattern repeats: new traffic channels emerge, attribution tooling follows slowly, and early adopters who build measurement infrastructure first gain durable advantages in understanding and optimizing their traffic mix.
AI-generated content optimization — sometimes called GEO (Generative Engine Optimization) — is emerging as a discipline precisely because traffic from AI engines behaves differently from traditional search. Knowing your current AI traffic baseline and which AI engines send the highest-value visitors gives you the data foundation to run structured experiments: which content formats get cited, which product pages earn AI recommendations, and which AI engines reward which types of businesses.
You cannot optimize what you do not measure. The businesses that set up AI traffic attribution analytics in early 2026 will have 12–18 months of historical data when the rest of the market starts paying attention.
ChatGPT monthly active users (Jan 2026)
Higher conversion rate vs organic search for AI referrals
Of traffic for B2B SaaS sites now from AI engines
Yes. When a user clicks a link inside ChatGPT, the browser sends a standard HTTP Referer header containing "chat.openai.com" or "chatgpt.com". Perplexity sends "perplexity.ai", Claude sends "claude.ai", and Gemini sends "gemini.google.com". These referrers are readable via document.referrer in JavaScript, the same way Google referrals work.
GA4 has a hard-coded referral exclusion list that strips referrers from known domains (like google.com) to avoid self-referrals. AI engine domains are not on GA4's "known referrers" list, so their traffic hits GA4's session-start logic without a recognized source. GA4 then classifies it as Direct/(none). GA4 also loses the referrer when a user clicks through a multi-page AI chat interface.
Based on Similarweb data from late 2025 and early 2026, AI engine referrals represent 1–5% of total web traffic for the average SaaS or ecommerce site, up from near-zero in 2023. For developer tools and B2B SaaS, the share is higher — anecdotally 5–15% — because technical users are more likely to use AI assistants for product research.
Yes. Perplexity sends clicks through with a "perplexity.ai" referrer intact. The main challenge is that Perplexity caches some pages inside its UI, which can strip referrer data for a small percentage of clicks. Direct click-throughs from Perplexity's answer citations are fully trackable via document.referrer.
You need a tool that captures the referrer at session start and then links that session to a downstream payment event. Attrifast does this server-side using a session token: when a Stripe payment completes, it joins the payment record to the original session referrer without relying on cookies. GA4 cannot do this natively.
Yes, claude.ai sends a standard Referer header on outbound clicks. Attribution for Claude traffic works identically to ChatGPT attribution — capture document.referrer at page load and store it with the session. The domain to look for is "claude.ai".
Source: Digiday — 'In Graphic Detail: The state of AI referral traffic in 2025', based on Conductor data
Every numbered citation in this article links to its primary source below.
Connect Stripe and get ChatGPT, Perplexity, and Claude broken out as distinct revenue channels — in 2 minutes, no cookies, no engineering.
Start free trial →Loved by 500+ users