AI traffic includes human assistant clicks, no-JS crawler requests, search visibility, preview fetchers, and spoofed bots. Leadstore separates them by confidence.
Why one traffic number is misleading
AI traffic is not one thing. A ChatGPT referral click, a GPTBot request, a PerplexityBot crawl, a Google Search click, and a spoofed user-agent are different signals.
AEO dashboards become more trustworthy when they label the source and confidence of each signal. That lets a user know whether the product is showing a verified crawler event, an observed pageview, or an inferred assistant referral.
Verified
Verified signals come from request-level evidence. Examples include server logs, Cloudflare logs, or Leadstore bot events with IP, rDNS, ASN, and bot signature verification.
This is the strongest layer for AI crawler proof because user-agent strings alone can be spoofed.
Observed
Observed signals are browser events. Leadstore Tag, GA4, and PostHog can all provide useful observed data.
Observed events are strongest for human behavior: pages viewed, campaigns, referrers, devices, languages, countries, and content performance.
Inferred
Inferred signals come from patterns such as referrer domains, UTM source names, and campaign values. For example, a visit with a chatgpt.com referrer is a strong assistant referral signal.
It is still not the same thing as proving that GPTBot crawled a page. Leadstore should keep that distinction visible.
Unavailable
Unavailable is an honest state. If a user has no tag, no logs, and no connected analytics source, Leadstore should not claim a metric it cannot support.
This is why Leadstore Tag is important: it reduces unavailable states and gives the dashboard a consistent first-party signal.
How this fits into the three Leadstore stages
■
Stage 1, account + site added: users get the audit reward before any tag or key - four core channel scores, top fixes, readiness, generated llms.txt and llm-data.json, and the Leadstore Tag snippet to install.
■
Stage 2, tag installed: users get the live telemetry reward with no key required - AI-crawler activity by engine, verified-bot counts, human traffic, top sources, top pages, devices and geography.
■
Stage 3, key connected: users add answer tracking on top of the audit and telemetry layers - Visibility Score, SAIV, Brand Monitor, share of voice, citations, competitors and hallucination checks.
Next step
Use the confidence model to decide which metrics are proof, which are observations, and which are directional signals.
