Skip to main content

Integrations

Osano

Wire Osano into every docs page — add your customer / site id to `integrations.osano` and the script loads on next deploy.

GDPR / CCPA / LGPD cookie-consent manager. The only integration that loads before the page is interactive so it can gate other scripts.

Configure

integrations.osanostringpathrequired

Osano Customer / site ID. Script injects via <Script strategy="beforeInteractive"> and loads from https://cmp.osano.com.

{
  "integrations": {
    "osano": "ABC-123-XYZ"
  }
}

Where to find your customer / site id

Osano dashboard → CMP → pick your consent manager → copy the customer/site ID from the install snippet (format ABC-123-XYZ).

Or set it from the dashboard — Editor → Configurations → AI & Advanced → Integrations.

Gotchas

  • Osano loads beforeInteractive on purpose — so other scripts can check window.Osano.cm.consent before firing. Don't mix it with afterInteractive workarounds.

  • If you also ship GA4 / Mixpanel / PostHog, configure Osano to gate the Analytics consent purpose. Otherwise consent decisions don't propagate.

Loading behavior

  • Strategy: beforeInteractive — injected synchronously in <head> before hydration so it can gate other scripts.

  • CSP: if you enforce a Content Security Policy, allowlist https://cmp.osano.com in script-src.

  • Removal: delete the integrations.osano key (or blank it in the dashboard) and redeploy — the script disappears on the next page load.

Related

Was this page helpful?

Last updated August 7, 2026