VisitorType
| 开发者 | stitchengineer |
|---|---|
| 更新时间 | 2026年7月25日 16:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Browser snippet injection — fires your tags, catches AI assistants and agentic browsers, measures engagement (time on page, scroll), and detects humans referred by ChatGPT, Perplexity, and Gemini (including visits GA4 buries in "Direct").
- Server-side tracking — reports every request in the background (zero added latency), so AI crawlers that never execute JavaScript are captured too.
安装:
- Install and activate the plugin.
- Create a container in your VisitorType dashboard and copy its ID (AITM-XXXXXXX).
- Go to Settings → VisitorType, paste your host URL and container ID, save.
- Visit your site once, then open the Analytics tab in your dashboard.
屏幕截图:
常见问题:
Why do I need a VisitorType account?
The account is what makes the analytics trustworthy and actionable: claimed bot identities are verified against vendor-published IP ranges refreshed daily, your data is available in one dashboard across all your sites (not trapped per-install), and you can fire different tags per visitor type — ad pixels for humans only, clean analytics, canonical facts for AI. The free plan is enough for a typical site.
Does this slow down my site?
No. The snippet is ~4 kB and loads async; server-side reporting is fire-and-forget (non-blocking) and adds no latency to page rendering.
Do I need a cookie banner for this?
The snippet sets no cookies. It uses a per-tab session identifier and honors GPC/DNT. See the privacy documentation in your dashboard; consult your own legal advisor for your site.
Where is the data stored?
In your VisitorType account. Events auto-delete after your plan's retention period.
I use a caching plugin and bots don't show up — why?
Full-page caches (WP Rocket, LiteSpeed, W3TC, WP Super Cache, CDN HTML caching) answer anonymous requests before WordPress runs, so the plugin's server-side reporting only sees requests that reach PHP — typically cache misses and logged-in users. Your own tests work (logged-in users bypass the cache) while real crawler visits hit the cached copy. For complete coverage on a cached site, capture at the edge with the VisitorType Cloudflare Worker (see the Server-side docs in your dashboard). The plugin's settings screen warns you automatically when it detects a known caching plugin.
I installed the plugin but some pages track humans and others don't
Your CDN or page cache is probably serving HTML cached BEFORE the plugin was activated — those copies contain no snippet. Purge the cache once (e.g. Cloudflare → Caching → Purge Everything) after activating or updating the plugin; freshly cached pages include the snippet and track normally.
Humans are recorded inconsistently — why?
Two usual causes: a "delay JavaScript execution" page-speed feature holding the snippet until first interaction (exclude tms.js from it), or visitors with Global Privacy Control enabled — VisitorType honors GPC by design and records nothing for those visitors.
更新日志:
- Warn on the settings screen when a full-page caching plugin is detected, with guidance for edge capture (page caches blind PHP-level server-side reporting).
- Initial release: snippet injection, server-side collection, settings page.