AI Traffic
One line in your page head, and every visit is recorded with where it came from — including the ones that arrived from ChatGPT, Perplexity, Gemini and the rest of the answer engines. First-party, no cookies by default, no IP addresses stored.
Start tracking freeTakes about a minute to install. No credit card.
Pageviews classified back to the answer engine that referred them, kept separate from your ordinary search and direct traffic.
Pageviews, visitors, sessions, top pages and top referrers over any window you pick — this replaces your analytics rather than sitting beside it.
Drop a second snippet on a thank-you page and conversions are tied back to the traffic source, so an AI referral can be valued rather than just counted.
A live share link anyone can open without an account, a PDF mirror of the dashboard, and a CSV of the raw events with the classification as its own column.
Type the domain and we issue a site token. Nothing else to configure.
A single deferred <script> in your <head>, carrying your site token. It works on any stack — WordPress, Shopify, a static site, a framework, anything that serves HTML.
Data appears within about a minute of the script loading. The page tells you it is waiting, then switches itself to the dashboard when the first pageview lands.
Filter to any date range, watch the daily chart, and see the per-engine breakdown of who is sending you people.
The script sends raw signals only: the page, the referrer, and any campaign parameters on the URL. Classification happens on our side, against a maintained map of the referrer hostnames and UTM patterns the answer engines use. Nothing is decided in the browser, which means the whole history can be re-classified when an engine changes how it links out — old data improves instead of going stale.
Matches come back in two tiers and they stay separate all the way to the dashboard. Confirmed is a referrer we can attribute with certainty. Probable is a strong pattern that could in principle be something else. Merging the two into one blurred "AI traffic" total would look tidier and be less true, so we do not.
The important caveat, stated plainly: the AI number is a floor, never a total. Many AI clients — especially mobile apps — send no referrer at all. Those visits land as direct traffic and no tool on the market can tell you otherwise. Your real AI traffic is higher than what any analytics product, this one included, can attribute. Treat the figure as the measurable part, and the trend in it as the useful signal.
Conversions are attributed by session rather than by their own hit, because a thank-you page carries no referrer. A conversion is credited to the first AI-classified pageview in its session, with a two-day lookback. Attributing on the conversion row itself would report roughly zero for every real site — an easy mistake and a very misleading one.
Bots are a separate problem. Crawlers do not run JavaScript, so this dashboard cannot see them by design. To find out which AI crawlers are actually visiting you, the server-log analyzer reads a slice of your access log, identifies the known AI bots in it, and compares what they did against what your robots.txt says they may do. Nothing from that upload is stored.
First-party, cookieless analytics that does one thing the others don't: shows you which visits came from ChatGPT, Perplexity, Gemini and the rest of the AI answer engines.
One line in your <head> and you'll see every visit — including the ones AI answer engines send you.
The same install also reports the AI bots that read you — bots don't run JavaScript, so that half needs server-side code the install page will give you.
Paste this one line into your site's <head> — visits show up here within a minute of the script loading.
No cookies by default — a first-party fallback cookie is set only if localStorage is unavailable. This page checks for your first visit every 30 seconds.
—
AI numbers are a floor, not a total — many AI apps (especially mobile) send no referrer at all, so real AI traffic is higher than what any tool can attribute.
Drop this on a thank-you or confirmation page to tie revenue back to the traffic source — including AI engines.
Conversions are attributed to the session's first AI-classified pageview (2-day lookback).
baseline.convert({value: 49.99});
A user agent is a claim, not a proof. We store no IP addresses, so anything can call itself GPTBot — and signature checks are reported by your own channel, never re-run by us.
Nothing server-side is reporting for this site yet, so we can tell you who AI sent — but not how often AI read you. That half needs code on your server; the tracker in the browser can never see it.
Add bot tracking Or analyze server logsAsk me about your projects, reports, brand mentions, backlinks, or anything on the platform.