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

Last checked: October 27, 2026.

AI assistants now send visitors who buy: in Adobe's US retail data, those visits converted better than other traffic every month from September 2025 to July 2026 ↗. Yet "how much revenue did ChatGPT bring us last month" is still a hard question for most teams, because the tools that answer it come in two halves that rarely meet.

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 one structural limit: 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.

Half two: web analytics. GA4 added a native AI Assistant channel in May 2026, and several privacy-first tools classify AI referrers too ↗. This watches your site, not the assistant. But it usually stops at the visit or at the purchase event recorded on the site: GA4 misses visitors who block it or refuse consent, and it does not see the renewals that happen later in your billing system.

The gap: the question that matters is which AI engines send visitors who pay, and what are those visitors worth over time? 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, measured on the server. Human referrals are the second half of the story; the first half is whether AI crawlers can and do read your site. This half is invisible to page tags, and the reason is structural: crawlers do not execute JavaScript. A tracking snippet, any tracking snippet, is invisible to GPTBot. So a tool that lives only in a <script> tag will never show you a single crawl, no matter what its landing page implies. The only way to see bots is to observe the request itself, server-side, and then verify it (see point 6). Get that, and you can pair crawls with referrals and read your crawl-to-refer ratio ↗: what each engine takes versus what it sends back.

3. Resistance to signal loss. First-party collection through your own domain, cookieless by default, loads where a third-party script is often blocked.

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. Page-level context. AI answers cite specific pages, not sites. Revenue per landing page tells you which content earns the citations that convert, closing the loop between content production and revenue.

6. Verification, because user agents lie. A user agent is a string anyone can send. Counting GPTBot in a log file counts the scrapers impersonating it too. Real crawler data is checked against the engines' published IP ranges (OpenAI, Anthropic and Perplexity publish theirs) or reverse DNS (Google, Bing, Apple), and the forgeries are labeled as forgeries rather than folded into your totals ↗.

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.

Setting it up (the Datalenk version)

1. Add the script. One line in your <head>. Cookieless by default, so nothing is written to the visitor's device; what needs your visitors' consent waits for it. Ad-block-heavy audience? Point a CNAME at us instead and it collects through your own subdomain.
2. Connect your payments. In Stripe, you create a restricted, read-only key and paste it in. We deliberately did not build a "connect with Stripe" OAuth button: this way we can read your charges and subscriptions, and we can do nothing else, we cannot charge a customer or refund one, and you revoke the key from your own dashboard whenever you like. A dozen other providers (Paddle, LemonSqueezy, Polar, PayPal, RevenueCat, Gumroad and friends) connect by signed webhook, and anything exotic goes through one POST /api/v1/payment or a CSV import.
3. Drop the server beacon. This is the step that buys you the crawler half. A few lines in your middleware or edge function post each request's user agent and IP to Datalenk with your workspace token. That is what makes AI crawlers visible at all, because they never run the script from step 1. We verify each hit against the engines' published IP ranges and reverse DNS, so what you see is real crawls, not scrapers wearing GPTBot's name.
4. Open the Channels report. AI engines appear as their own channel, split by engine, with visitors, signups and revenue per engine. Next to it, the AI crawler view: which engines read you, how often, verified.

Steps 1 and 2 take a few minutes and give you revenue by AI engine. Step 3 is a code change, so it takes as long as your deploy pipeline does, and it is the difference between knowing what AI sends you and knowing what AI takes from you.

See which AI engines actually pay you. 14-day trial, card required, cancel in two clicks. Start your trial, or check the pricing first.

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, misses ad-blocked sessions, and ties revenue only through the purchase events your site sends.

Which AI engines should I track? Start with the engines that already appear in your referrers, usually ChatGPT first, then Perplexity, Gemini, Claude and Copilot. Track the long tail automatically rather than manually.