ChatGPT is sending you customers. Your analytics calls it “Direct.”
VisitorType finds the visits AI answers send you — verified, attributed, and ready for your report. Then fires the right tags for humans, crawlers, and agents. One snippet, five minutes, no cookies.
Mention trackers ask the AI. We measure your traffic.
Trusted by 50+ websites measuring their AI traffic — and growing
We run VisitorType on visitortype.ai. Here is what 30 days looked like.
of visits were human. The rest were crawlers, assistants, and agents — the traffic most analytics either miscounts or never sees.
checkable “AI bot” claims failed IP verification — scrapers wearing a trusted name. Tools that read the user-agent alone count them as real AI traffic.
live ChatGPT fetches — real people asking an assistant about us, mid-conversation. Every one of them a buying signal invisible to GA4.
Figures from our own container, 30 days to 2026-07-20. Your numbers will differ — that is rather the point.
The web grew a second audience, and your stack can't see it.
Your best traffic is filed under “Direct”
Someone asks ChatGPT for a recommendation, gets your link, and buys. GA4 records that as Direct — no source, no campaign, no credit. The fastest-growing acquisition channel is the one channel you cannot report on.
You can’t justify what you can’t measure
You’re being asked to invest in AI visibility, llms.txt, and GEO — and then to prove it worked. Without attribution, every euro spent on being citable is an act of faith, and every client report has a hole in it.
And the numbers you do have are polluted
Crawlers and agentic browsers get counted as people, while impostors wear a trusted bot’s name. On our own site, roughly two thirds of checkable AI-bot claims came from outside the vendor’s published IP ranges.
Invisible traffic isn't free. You're paying for it.
Fire your ad pixels for verified humans only — one trigger, no code. Independent studies put invalid ad traffic at 15–30% of paid clicks; drag the slider to your own estimate.
Stop paying for bots — start freeDetect. Target. Measure.
See exactly which AI platforms send you people — ChatGPT, Perplexity, Gemini, Claude, Copilot and more — which pages they land on, and how that channel moves week over week. The visits your analytics buries in Direct, itemised.
Every claimed agent is checked against the vendor’s published IP ranges, refreshed daily. Impostors are flagged, not counted. That’s the difference between a number you report to a client and a number you hope is right.
GTM-style rules on top of the classification: fire ad pixels for humans only, serve canonical facts to AI search bots, push the AI source into your own analytics. Versioned configs, no deploys, no code changes.
<script async src="https://visitortype.ai/tms.js" data-container="AITM-XXXXXXX"></script> // then, in plain English rules: // if visitor_type is ai_search → inject canonical facts // if visitor_type is human → fire analytics pixel // if agent_name is ChatGPT-User → count an assistant referral
From install to your first AI-aware rule, in two minutes
Fair questions.
Why doesn’t my analytics show ChatGPT traffic?＋
Most AI assistants send visitors without a referrer your analytics recognises, so the visit lands in “Direct” — indistinguishable from someone typing your URL. VisitorType reads the signals your analytics discards (referrer patterns, UTM fusion, and the assistant fetches that precede the visit) and attributes the visit to the platform that sent it. You can also push that source back into GA4, so your existing reports finally show the channel.
How is this different from AI visibility tools like Profound, Peec, or Otterly?＋
Those tools work from the outside: they ask AI models questions and report whether your brand is mentioned. Useful — but they can’t see your website. VisitorType works from the inside: a snippet on your site measures what those mentions actually send you — verified visits, the pages they land on, and the conversions they turn into. Run a visibility tool to win mentions; run VisitorType to prove the mentions pay. They’re complementary, and we’re the half with first-party data.
How is this different from Google Tag Manager?＋
GTM assumes every visitor is a human in a browser. VisitorType classifies each visit first — human, AI crawler, AI search bot, assistant fetcher, or agentic browser — and makes that classification available to every trigger. Same mental model (tags, triggers, versions, publish), new audience dimension.
AI crawlers don't run JavaScript. How can a snippet see them?＋
It can't — that's exactly why there's a second pipeline. Your backend or edge reports requests to the server-collect API (copy-paste adapters for Next.js, Cloudflare Workers, and Express included). The snippet catches assistants and agentic browsers; the server-side reporter catches the crawlers.
Will it slow down my site?＋
The snippet is ~3 kB, loads async, and makes a single request. Tags fire after classification, and a failing tag or unreachable API never breaks the page. Server-side reporting is fire-and-forget and adds zero response latency.
Can I block AI crawlers with it?＋
Blocking belongs in robots.txt or your WAF — and our detection data tells you exactly who to name there. What the tag manager does is subtler: serve each audience differently. Many teams want AI agents reading more (accurate, structured facts), not less.
Can my AI assistant manage it for me?＋
Yes. Every account gets an MCP server endpoint. Connect Claude, ChatGPT, Cursor, or any MCP client with an API key and ask it things like “which AI agents hit my pricing page this week?” or “create a tag for Perplexity visitors and publish it.”
Is there a free plan?＋
Yes. Create a free account and you get the core platform — classification, the AI Channel report, rules, and the MCP server. Paid plans (€59 Pro / €149 Business) add capacity and higher limits. Existing early-access accounts keep their grandfathered Pro-level access.
Your site already has AI visitors.
Find out who they are — and decide what they see. Free to start.
No credit card · 5-minute install · cookieless & GDPR-friendly by design