Privacy-first analytics, with optional server-side reporting of the AI crawlers that read your docs.
Configure
integrations.truestatstringpathrequiredTrueStat Site key. Script injects via <Script strategy="afterInteractive"> and loads from https://truestat.io.
{
"integrations": {
"truestat": "ts_cd067fec0d8b204f35f1"
}
}Where to find your site key
TrueStat dashboard → the site → Install → the data-website-id and data-domain in the snippet.
Or set it from the dashboard — Editor → Configurations → AI & Advanced → Integrations.
Gotchas
Both the site key and the domain are required. They are the
data-website-idanddata-domainfrom your install snippet, and neither is guessed: the domain is the property your numbers are filed under, which is usually your main site rather than the docs host. Without both, the script is not loaded at all.Serving TrueStat through your own domain? Put that origin in TrueStat endpoint — the
srcfrom your snippet without/js/t.js, e.g.https://p.acme.com. It moves both the script and the crawler reports onto your domain.AI crawlers need the server. A crawler does not run JavaScript — GPTBot fetches the page and leaves — so the tag never sees it. Turn on AI crawler tracking and the platform reports those requests from its own servers instead, using the same site key.
Loading behavior
Strategy:
afterInteractive— injected after page interactivity, so it never blocks first paint.CSP: if you enforce a Content Security Policy, allowlist
https://truestat.ioinscript-src.Removal: delete the
integrations.truestatkey (or blank it in the dashboard) and redeploy — the script disappears on the next page load.
Related
Schema reference —
integrations— auto-generated field listing