/ /

Missing consent banner

Updated 2 months ago

If you have already generated the osano.js and placed it in the <head> of your website but do not see the consent banner on your site, it is likely that your script is in Discovery/Listener Mode. This is the default compliance mode when you first publish a configuration.

image.png

When your script is in Discovery/Listener mode, only monitoring occurs. Osano will not display visually and there will be no active blocking happening on the page.

To see the dialog on your site, you'll need to change to "Strict" or "Permissive" mode and publish that out. 

PLEASE BE SURE YOU UNDERSTAND THE DIFFERENCE BETWEEN PERMISSIVE AND STRICT MODE BEFORE PUBLISHING!

Compliance Mode Definitions

  • Discovery/Listener Mode

    • Osano will gather script and cookie information for categorization, but the consent banner will not appear on your webpage, and no blocking will occur.

  • Permissive Mode

    • The consent banner will appear on your website, and all managed scripts/cookies will execute as expected. However, all uncategorized scripts/cookies and ignored items will be identified and allowed regardless of consent given.

  • Strict Mode (Most Compliant)

    • The consent banner will appear on your website, and all managed scripts/cookies will execute as expected. However, all uncategorized scripts/cookies and ignored items will be identified and blocked from running/loading.

image.pngWe typically recommend not publishing into Permissive mode until you have the majority of your scripts/cookies classified and we strongly recommend not moving into Strict mode until all discovered items have been classified. If you move into Strict mode without classification rules in place, your site is likely to break.

To read more about classifying scripts and cookies, see Classification Categories and Classification Rules.

Was this article helpful?
Subscribe to receive updates on this article