LLM Referral Tracking: See Which AI Engines Send You Paying Customers

Last updated: June 2026.

Here is the attribution gap nobody talks about. AI assistants now influence a measurable share of buying decisions: AI referral traffic grew 357% in a year and converts at 30 to 40% ↗. Yet if you ask a marketing team "how much revenue did ChatGPT bring you last month", almost nobody can answer. The tooling market has two halves that do not meet in the middle.

What existing tools do (and what they miss)

Half one: GEO and AI visibility platforms. Tools like Profound, Otterly, Peec and Hall monitor how often your brand appears in AI answers. They run prompts against ChatGPT, Perplexity and Gemini, track your share of voice against competitors, and tell you which prompts mention you. Genuinely useful, with two structural limits:

1. They watch the assistant, not your site. Brand mentions are upstream awareness. They cannot tell you whether the mention turned into a visit, a signup, or a paying customer.
2. They are priced for the enterprise. Entry tiers start around $39/month with meaningful features at $199+/month, and category leader Profound raised $96M at a $1B valuation selling to enterprise marketing teams. A solo founder or SMB monitoring "does AI send me customers" is not who these tools are built for.

Half two: web analytics. GA4 added a native AI Assistant channel in May 2026, and most privacy-first tools can segment AI referrers manually ↗. This watches your site, not the assistant. But it stops at the visit: GA4 counts the click, loses 40-60% of sessions to ad blockers and refused consent, and ties nothing to revenue without a configuration project. Most lightweight analytics tools stop at the pageview entirely.

The gap: nobody answers the question that matters: which AI engines send visitors who pay, and what are those visitors worth? That is a revenue attribution question, and it needs the visit data and the payment data in the same system.

What complete LLM referral tracking looks like

Here is the spec, whether you assemble it yourself or use a tool that ships it:

1. Automatic AI channel classification. Every session from chatgpt.com, perplexity.ai, claude.ai, gemini.google.com, copilot.microsoft.com and the rest of the referrer list classified as AI traffic, split by engine, with no regex homework. New engines added for you as they appear.

2. Crawl-side visibility. Human referrals are the second half of the story; the first half is whether AI crawlers can and do read your site. Complete tracking pairs referral data with bot data (which engines crawl you, what they read) and computes your crawl-to-refer ratio ↗: what each engine takes versus what it sends back.

3. Resistance to signal loss. AI-heavy audiences are ad-block-heavy audiences. First-party collection through your own domain, without cookies, keeps the consent banner away and the data complete where a third-party script goes blind.

4. Revenue attribution. Connect the payment provider (Stripe and friends) and every AI session inherits an outcome: trial, subscription, amount. Now "Perplexity sent 212 visits" becomes "Perplexity sent $1,840 in new MRR", and you know which engine deserves your GEO effort.

5. Campaign and link context. AI answers increasingly cite specific pages. Tracked links and per-page revenue tell you which content earns the citations that convert, closing the loop between content production and revenue.

This is the spec we built Datalenk against: AI engines as first-class channels, tied to payments, alongside every other channel you run, at web-analytics pricing rather than enterprise GEO pricing.

Setting it up in five minutes (the Datalenk version)

1. Add the lightweight script (or the first-party proxy for ad-block resilience).
2. Connect Stripe in two clicks.
3. Open the Channels report: AI engines appear as their own channel, split by engine, with visitors, signups and revenue per engine.
4. Optional: run the free AI Traffic Checker first to see whether AI crawlers can read your site at all .

(Not launched yet? Join the waitlist and we will email you when this takes five actual minutes.)

DIY alternative: the manual stack

If you would rather assemble it yourself today: GA4's AI Assistant channel for clicks + a custom channel group for unrecognized engines ↗ + server log analysis for crawler activity ↗ + a spreadsheet joining Stripe exports to session sources via UTM discipline. It works. It is also a weekly maintenance chore with attribution gaps at every join, which is exactly why we productized it.

FAQ

What is LLM referral tracking? Measuring the visitors that AI assistants (ChatGPT, Perplexity, Claude, Gemini) send to your site, by engine, ideally tied to conversions and revenue rather than just session counts.

How is this different from GEO tools like Profound or Otterly? GEO tools monitor your brand's presence inside AI answers (share of voice, prompt monitoring). LLM referral tracking measures what arrives on your site and what it is worth. They are complementary; the second one is the one that speaks in dollars.

Can GA4 do LLM referral tracking? Partially. Since May 2026 it classifies recognized AI referrers into an AI Assistant channel, but it sees only the click side, loses blocked and consent-refused sessions, and needs separate configuration to connect revenue.

Which AI engines should I track? Start with ChatGPT (~87% of AI platform traffic), then Perplexity (the most citation-driven), Gemini (fastest growing), Claude and Copilot. Track the long tail automatically rather than manually.