Getting started
VisitorType works like a classic tag manager — containers, tags, triggers, versions — with one big difference: every visitor is classifiedbefore your rules run. You can fire one tag for humans, another for AI crawlers, and a third for AI agents browsing on a customer's behalf.
Visitor types
| Type | Who it is | Examples |
|---|---|---|
| human | A person in a normal browser | — |
| ai_crawler | Bots collecting training/index data | GPTBot, ClaudeBot, CCBot, Bytespider |
| ai_search | AI search engine crawlers | OAI-SearchBot, PerplexityBot, DuckAssistBot |
| ai_assistant | An assistant fetching a page for a live user | ChatGPT-User, Claude-User, MistralAI-User |
| ai_browser_agent | AI driving a real browser (detected via signals) | agent mode, computer-use, headless automation |
| bot | Classic non-AI bots | Googlebot, Bingbot, AhrefsBot |
Five-minute setup
1. Create an accountand a container for your site. You'll get a public id like AITM-XXXXXXX.
2. Add the snippet to every page (see Installing the snippet):
<script async src="https://visitortype.ai/tms.js" data-container="AITM-XXXXXXX"></script>
3. Create a trigger (e.g. visitor_type equals ai_crawler) and a tag that uses it.
4. Publish. Nothing goes live until you publish a version — saving a tag never changes your site.
5. Watch the Analytics tab fill with classified traffic, or connect your AI and just ask it.
The AI Channel report & attribution
Every container has an AI Channeltab: which AI platforms (ChatGPT, Perplexity, Gemini, Claude, Copilot…) send you visitors, which pages they land on, and the 30-day trend — the visits most analytics files under “Direct.” To attribute conversions, create a trigger with condition event_name equals “signup” (any name you choose), wire a tag to it, and call aitm.track(“signup”) at the moment of conversion — the report joins those goal fires back to the AI platform that started the session. A CSV export and the ga4_ai_source tag template (pushes the source into your own GA4) round out the reporting loop.
Recommended: add server-side tracking
The snippet catches humans, AI assistants, and agentic browsers. But most AI crawlersdon't execute JavaScript — to see those, add the 5-line server-side reporter described in Server-side tracking.