AI Traffic
See which of your visitors were sent by an AI answer
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.
What it shows you
Where the measurement starts, what it can say, and what it cannot.
Someone asks an engine a question, and the answer names your site.
Nothing. The question and the answer happen inside the engine. No analytics product sees either one, so this page will not show you a transcript it does not have.
Measurement starts at the click. That is the whole reason the AI figure is a floor rather than a total.
The shape of the signal, not a specific visit. A click carries where it came from and there is no other signal to have. Across the window below, this site logged 6 pageviews with a chatgpt.com referrer, 3 from bing.com, 2 from gemini.google.com and 2 from claude.ai.
<script defer src="https://baselinelabs.ai/js/tracker.js" data-site="…"></script>
The script sends the page, the referrer and the campaign. No cookie, no IP address, first-party to your domain. Classification happens on our side in two tiers that never merge, so a certain match and a strong guess stay tellable apart. Those two counts are this site's real ones: 13 confirmed pageviews across gpt, claude and gemini, and 3 probable from copilot. They are never added into a single number.
The ordinary numbers too, so this replaces your analytics rather than sitting beside it. The AI cut is counted separately and is never folded into the row above.
AI-attributed pageviews, one cell per day
A second line on your thank-you page, baseline.convert({value: orderTotal}), credits the sale back to the first AI-classified pageview in that session, with a two-day lookback. Over this window the tracked site recorded no conversions at all, so the panel above reports zero rather than a demonstration figure.
16 AI-attributed pageviews against 2,376 is 0.7% of this site's traffic, and 22 of the 31 days recorded none at all. That is the measurable part, not the real one. Many AI clients, mobile apps most of all, send no referrer, so those visits land in the direct column and no analytics product, this one included, can tell you otherwise. The AI number is a floor, never a total. Read it as a floor, and trust the trend in it rather than the level.
What you'll get
How it works
Add your domain
Type the domain and we issue a site token. Nothing else to configure.
Paste one script tag
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.
Visits start arriving
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.
Read the AI cut
Filter to any date range, watch the daily chart, and see the per-engine breakdown of who is sending you people.
How AI referrals are detected, and why the number is a floor
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, so 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, which is 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.
Frequently asked questions
Find out how much of your traffic is already coming from AI
Start tracking freeAI Traffic
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.
A study is one business and its website. Traffic, visibility and everything else hangs off it, so start one and this dashboard follows.
Once the study exists, one install gives you both halves: the visits AI engines send you, and the AI bots that read 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.
So there is no number to show you here, which is a different thing from a number that came back zero. Nobody has been counted, rather than nobody having visited.
One install covers both halves: the visits AI engines send you, and the AI bots that read you.
-
Daily traffic
AI engines 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.
AI referrals, seen server-side Ad-blocker-proof Counted by your installed channel from the Referer and utm tag on the request itself, so a blocker, a consent banner or a no-JS client cannot hide it. Never added to the AI pageviews above - both are watching the same visit from different places.
Top pages
Top referrers
Track conversions
Optional. Paste this one line on your thank-you or order-confirmation page, with the real order value in place of 49.99, and each sale shows up above credited to the visit that brought the customer in - including visits that came from an AI answer.
A sale is credited to an AI engine when the same visitor first arrived from one within the two days before. Without this line the dashboard can count visits but never revenue.
baseline.convert({value: 49.99});What the AI bots came for
Bots seen
New here? How bot counts work
Pages they read
AI bots
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.
