Help
HOMEPAGE | HELP GUIDES | HELP | TROUBLESHOOTING

Troubleshooting

Fixes for the most common problems.

The banner doesn't show

  1. Is the script on the page? View the page source and search for cdn.okito.com/js/ (with the Webflow app, cdn.okito.com/wf/). Check the key matches your website. The script runs only when loaded over HTTPS from cdn.okito.com as in the installation code (older code with app.okito.com works too, but a Content-Security-Policy must then allow it; see CSP), not from a copy on another address. The early blocker (blocker.js) alone shows no banner: the Okito script must be there too (with Google Tag Manager it isn't in the page source; check the Okito tag in GTM's Preview). A Webflow site connected before the app's versioned loader needs Update Okito script once; see Webflow.
  2. Is an ad blocker or privacy browser active? Turn it off, or test in a private window without extensions.
  3. Did you already choose? The banner doesn't show again after a choice. Open a private window, or clear the site's storage.
  4. Is the domain right? The banner only loads on the website's domain and its subdomains, so a live website's banner does not load on localhost. Check the domain in Websites; to test locally, see Staging sites and local testing.
  5. Where consent is not required: with No banner, keep measurement on, visitors outside the opt-in regions see no banner. Test with a VPN in an opt-in region (for example Germany).
  6. Plan limits: if the website reached its monthly pageviews, the banner is paused until next month or an upgrade.
  7. Content-Security-Policy: allow https://cdn.okito.com. See CSP.

Two banners appear

Okito is installed twice (theme + plugin + GTM), or another consent tool is active (for example Shopify's own banner or another WordPress plugin). Keep one installation and one consent tool.

  • Check the load order: the Consent Mode snippet and the Okito script must be above your Google tags.
  • Open the page with ?okito_debug=1. A yellow box names the tag that ran first. See Debug mode.
  • If the tag comes from your own domain, see Google tag gateway.
  • In advanced mode Google tags load before consent by design, with a denied state; they send only cookieless pings until the visitor accepts. If you want them blocked, use basic mode.

A tag doesn't run after Accept All

  • Check that its cookies are in the category the visitor accepted (Cookie Manager).
  • If you marked the script, check data-cookie-category is spelled right (necessary, functional, analytics, performance, advertisement, or a name used by other consent tools such as marketing).
  • If a service is switched off, its scripts stay blocked even when the category is on.

Something on my site stopped working

A blocking rule may be too broad. Open Script Blocking, find the rule that matches the script, and narrow its patterns or change it to allow the script.

Changes in Banner Builder don't show

Click Save Banner, then reload your site in a private window. If you use a caching plugin or CDN that caches your HTML, clear it.

Verify installation fails

The page must be reachable over public HTTPS, without a password, and must contain the Okito script in its HTML (not only added later by JavaScript). See Verify your installation.

Still stuck?

Contact Okito support. For missing consent mode or TCF signals on Google tags, contact Okito before Google: Google support asks for proof that you contacted your CMP first.