General website installation of Osano.js cookie consent - applies to most common website installations.
Installing the Osano.js
After creating and publishing your configuration, the "Get Code" button will become active. This button will provide you with the osano.js. Once you have the Osano code, place it in the global <head> of your document.
Important: Osano will only be able to discover and block scripts that are loaded after it, therefore it must execute in the <head> before any other 3rd party or tracking content.
Important: The Osano.js should be placed without any async or defer attributes. Compliance cannot be guaranteed when using the above attributes.
Osano is platform-agnostic, which means the code can be added to the <head> of any site and utilized without any additional configuration.
Once the osano.js is in your site's <head>, it can take a few minutes to a few hours before the script has captured and reported cookies and scripts that exist across your sites.
Once you have collected enough reports from osano.js, you can work with your other business units to identify and classify all cookies/scripts/and local storage items. This exercise ensures that no "strictly necessary" scripts, cookies, or local storage get blocked.
We recommend users remain in "Listener" mode until you have added the osano.js into your site and have discovered and classified all relevant scripts and cookies.
In Listener mode, the consent manager will NOT block any scripts or beacons. It will NOT delete cookies. It will NOT display dialogs to your visitors. In other words, it will not alter your site in any way. You can use Osano in "Listener" mode and another CMP simultaneously if you migrate away from another provider. This way, there are no gaps in compliance.
After you have categorized each script and cookie appropriately, you can enable Permissive or Strict Mode and publish these changes.
You will now see the consent dialog on your website!