Getting Started with Consent Management
Creating a consent management implementation is simple and takes just a few minutes.
Navigate to the "Consent Management" tab in Osano, and create a new site profile.
- In the site profile, you'll add the root domain names that your web site(s) are hosted on. If you own example.com, but your web site is hosted on www.example.com, you will want to enter only example.com, Osano automatically works with subdomains of your website with no additional configuration.
- Cross-Domain (only available for Enterprise accounts) - by flipping the cross-domain switch, you have the option to add multiple domains into your configuration settings, which enable consents to be chared across unrelated domains owned by the same entity. Simply add a domain, "tab," and add additional domains.
- URL Scanning (only available for Enterprise accounts) - click the (+) to add URLs to be scanned on a monthly basis for unclassified cookies and scripts related to a Consent Manager configuration.
Create Configuration and Publish
Keep Compliance Mode in Listener until you have added the osano.js into your site and have discovered and classified all relevant scripts. In Listener mode, the consent manager will not block any scripts or beacons, it will not delete cookies, and it will not display dialogs to your visitors, in other words, it will not alter your site in any way. You can use Listener mode at the same time as another CMP if you are migrating away from another provider. This will ensure no gaps in compliance.
Use "get code" to copy your osano.js and paste it into your website's <head>. Ensure that the osano.js is the first thing that loads on your site.
In Listener mode, depending upon the traffic to your site, you will need to wait anywhere from a few minutes to a few hours before the script has captured and reported all of the cookies, scripts, and local storage items that exist across your sites. Most sites will have a full sampling within an hour; higher volume sites may have a sufficient sampling in just a few minutes.
Once you have collected enough reports from osano.js, you can work with your other business units to identify any unknown cookies/scripts/and local storage items to ensure that no "strictly necessary" scripts, cookies, or local storage are blocked by categorizing them appropriately in "Script Classification."
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.
Compliance Mode Definitions
- Listener Mode - Osano will gather script and cookie information for categorization, but the consent dialog will not appear on your webpage, and no blocking will occur.
- Permissive Mode - The consent dialog will appear on your website, and all uncategorized scripts will be identified and allowed regardless of consent given. All categorized scripts will be accepted or denied based on user selection. Compliance can be reached in Permissive Mode, but is less certain and sustainable than Strict.
- Strict Mode - The consent dialog will appear on your website, and all uncategorized scripts will be blocked until they have been classified. (Recommended - Most compliant)
With the Consent Manager Configuration screen, you will find the "Stylizing" tab. The Styling tab allows you to customize certain aspects of your Consent Manager's appearance.
Use the "Preview for Different Compliance Laws" to generate a preview of your consent dialog in different geographical locations.
*** NOTE: You cannot change which consent dialog the end-user sees as Osano automatically displays the correct dialog to each end-user based on their geotargeted location (I.P. Addresses). The dialog shown will be that which is most compliant in the user's location. ***
From here, you can customize dialog type, placement, and coloration. You have the option to customize your consent management overlay by choosing one of the Osano pre-generated themes or by setting all colors individually. If there are specific customizations that you would like to employ on your consent manager overlay, you can do this using CSS. You can find a full list of Osano Classes HERE!
Scripts and Script Classification
Once you have placed your Osano.js in the <head> of your site in "Listener" mode, Osano will begin alerting you to and displaying identified scripts. These scripts will appear in the "Scripts" section of the Consent Manager. It can take anywhere from a few minutes to a few hours for scripts to populate.
Once scripts are identified, you must classify them as one of the following:
Be sure to classify each script before saving and publishing out any new changes.
*** NOTE: You CANNOT switch compliance mode from "Listener" to "Permissive" or "Strict" without at least one script classified. For compliance's sake, we recommend you classify as many scripts as possible before switching out of "Listener" mode. ***
Cookies can be categorized in the same way as scripts. Classification rules can be set for cookies as well.
Once Cookies are identified, you must classify them as one of the following:
Cookie Disclosures are used to disclose or list out cookies your website is using to the end-user so that they are aware of what is in use and why it is in use. In this section, you can manually add the following:
- Category (tied to the script/cookie categories above)
- Cookie Name
- Cookie Provider
- Expiration Date
- Description of the Cookie
Once added, these disclosures will appear to the end-user on your webpage in the "drawer" under their associated categories. You are not required to include cookie disclosures, but it is recommended practice for both CCPA and GDPR.
This section of Osano allows you to view a log of consents for a particular configuration. Using an Osano_UUID or a public IP address, you can search for a particular user's consent logs over a period of time. This data is encrypted and anonymized. For more information on Consent Data, contact Osano support.