Privacy-first analytics that also reports AI crawler traffic — which assistants read a page, and how often.
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 in the snippet.
Or set it from the dashboard — Editor → Configurations → AI & Advanced → Integrations.
Gotchas
The domain is filled in for you. TrueStat reports against a property, and the platform states this site's own address — your custom domain when you have one, the
.nookdocs.sitesubdomain otherwise. That matters when a site moves: stated explicitly, traffic keeps landing on the same property instead of silently starting a second one. Override it only to report against something else —"truestat": { "siteKey": "ts_…", "domain": "acme.com" }, or the TrueStat domain field that appears in the dashboard once a key is entered.This integration covers the browser script only. TrueStat's server-side AI-crawler tracking runs in your own application's proxy/middleware and is not something a docs host can install for you.
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