The Osano cookie consent manager is platform-agnostic, which means the code that allows it to function can be added to the <head> of any website and utilized without any additional configuration.
There are, however, some platforms that may require additional steps for installation which have been highlighted below:
Installing your Code
Access your Cookie Consent code within Osano
After creating and publishing your configuration within the Osano Cookie Consent admin (see CMP Setup Guide), 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.
Access your Website Editor
Log in to your website's administrative dashboard or editor.
Find Code Injection or Customization
This process will change depending on what tools you utilized to build your website.
In many cases, you can look for a section related to code injection or customization. This is often found in settings like "Site," "Design," "Theme," or "Customization."
Add Osano.js to Head <head> Section
Find the area where you can insert code in the <head> section of your website. This is typically labeled as "Header," "Tracking & Analytics," or similar.
Paste the Osano.js script within <script> tags:
<script>YOUR OSANO.JS HERE</script>
Important: The Osano.js should be placed without any async or defer attributes. Compliance cannot be guaranteed when using the above attributes.
Save Changes
Some site editors might require you to save your changes in the code editor.
Publish or Update Website
If your platform has a "Publish" or "Update" button, click it to make your changes live.
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!