Know who arrives from an AI, and what they buy

The script logs AI bot visits, not human visitor data, and it has no measurable effect on page speed. Identification happens only when a person gives you their email through your own forms, at which point the anonymous history that preceded it is merged into that record, the same way any CRM or marketing automation tool works. Installation takes under two minutes. On Cloudflare it is a single OAuth click, verified on both the apex domain and www, with no snippet to paste. On other stacks the script is a standard tag. If a Content Security Policy blocks it, Citeme detects that automatically and tells you, rather than leaving you with a month of empty charts and no explanation.

Citeme records conversions on your site with their declared value, purchases and signups, attributed over a 30 day window. That number is an estimate: it reflects what happened on the site, not what was eventually invoiced. CRM verified revenue is the stricter figure. When HubSpot, GoHighLevel or Attio is connected, deals that your team actually marked as won flow back into the Impact tab, counted per currency. Leads that came from AI are tagged automatically in the CRM, so the attribution survives inside the tool your sales team already lives in. The distinction matters when you present numbers. Estimated pipeline is for steering, verified revenue is for defending a budget.

It is a probable link, not a certainty, and the product says so. AI assistants rarely pass a clean referrer, so no tool can promise a deterministic chain from a specific typed question to a specific visitor. What Citeme does have is both halves of the picture. It runs your prompts against the nine surfaces it tracks and knows which answers cite which of your pages, and it sees the landing page and timing of the visit. Matching the two gives a strong probable attribution, and it gets stronger the more distinctive the landing page is. A visit to a niche comparison page cited in exactly one answer is close to certain. A visit to the homepage is a weaker signal, and it is presented as such.

Four, and conflating them is the most common mistake in AI analytics. A training crawl is a model harvesting content for a future version, valuable for long term presence but worth nothing this quarter. An AI search index pass is an engine building its retrievable index. A real time retrieval is an engine fetching your page to answer a question being asked right now, which is the signal that a citation is live. A human visitor arriving from an AI answer is the only one of the four that can buy anything. Most tools show a single line called AI traffic that mixes all four, which is why the numbers look impressive and convert badly. Citeme shows which bot came, why, and on which pages, with a live world map of the human visits.

No. Without a CRM you still get the full picture up to the conversion: which prompts earn traffic, which pages receive it, who those people are once they identify themselves, what they did across sessions, and the value of purchases and signups recorded on the site over a 30 day window. The CRM adds one thing, and it is the thing that ends arguments. Instead of a number Citeme computed, you get a number your sales team confirmed, per currency, on deals they marked as won. If you sell online and your conversions carry their real value, the site side may be enough. If you sell through a pipeline with a sales cycle, connect the CRM: that is where the case for a GEO budget is actually made.