Integrations overview | NookDocs

integrations is a key-value map where the key names the provider and the value is that provider's account ID. The platform injects the right <script> tag on every docs page — tenants with no integrations ship zero extra JS.

Every integration loads with strategy="afterInteractive" so it never blocks first paint. The exception is Osano (cookie consent), which loads beforeInteractive so it can gate other scripts if the reader hasn't consented.

Quick start

{
  "integrations": {
    "ga4": "G-XXXXXXXXXX",
    "posthog": "phc_abc123...",
    "plausible": "docs.example.com",
    "intercom": "abc123xy",
    "osano": "ABC-123-XYZ"
  }
}

Or edit from Configurations → AI & Advanced → Integrations in the dashboard.

Analytics (14)

Provider	Config key	What to set
Google Analytics 4	`ga4`	Measurement ID (`G-XXXXXXXXXX`)
Google Tag Manager	`gtm`	Container ID (`GTM-XXXXXXX`)
PostHog	`posthog`	Project API key (`phc_abc123...`)
Plausible	`plausible`	Tracked domain (`docs.example.com`)
Fathom	`fathom`	Site ID (`ABCDEFGH`)
Mixpanel	`mixpanel`	Project token (`abc123def456...`)
Segment	`segment`	Write key (`abcxyz123`)
Amplitude	`amplitude`	API key (`abc123...`)
Microsoft Clarity	`clarity`	Project ID (`abc123def4`)
Hotjar	`hotjar`	Site ID (`1234567`)
LogRocket	`logrocket`	App ID (`org/app`)
TrueStat	`truestat`	Site key (`ts_cd067fec0d8b204f35f1`)
Pirsch	`pirsch`	ID (`abc123`)
Heap	`heap`	App ID (`1234567890`)

All thirteen coexist on the same site without collision — ship GA4 + PostHog + Hotjar on the same page and each gets clean events.

Cookie consent (1)

Provider	Config key	What to set
Osano	`osano`	Customer / site ID (`ABC-123-XYZ`)

Support widgets (2)

Provider	Config key	What to set
Intercom	`intercom`	App ID (`abc123xy`)
Front Chat	`frontChat`	Chat ID (`abc123`)

Privacy + security

No server-side pipe. The platform doesn't proxy events through our servers — each script runs in the reader's browser using the account ID you provided.
Secrets. Analytics IDs are not secrets; they're public by design. Don't put anything sensitive in integrations.*.
CSP. If you enforce a Content Security Policy, allowlist each provider's script origin. Per-provider pages list the exact URL.
Consent. When osano is configured it loads before every other integration so consent decisions can gate downstream scripts.

Personalization (planned)

Intercom, Mixpanel, Amplitude, and PostHog support user identification (intercom('boot', { user_id, name, email })). When authenticated-user personalization ships, you'll be able to pipe reader identity into these integrations automatically — no code.

Schema reference — integrations — auto-generated field listing
Analytics dashboard — first-party events, independent of these integrations
Site settings — banner, SEO, redirects, footer, navbar