Cookie Consent: Things to Know and Best Practices
Websites
There are very few updates to the website screen for Cookie Consent. The Geolocation Rule is displayed so that you can quickly view and navigate between the content settings and templates used in a domain. Clicking the domain name name will take you to the website details.
Scan Results
If this is the first scan of the domain, you will see and overview of the scan with options to view Cookies, Tags, Forms, Pages, and Storage. If you have multiple scans of your domain, you will see an All Scan summary showing the total number of tracking technologies encountered. The cookies are broken into New Cookies (not previously scanned) and Old Cookies (previously scanned) cookies and classified by cookie category. The number of Tags and Forms are also displayed and classified by type. You can view the results of any single scan using the Show drop down menu in the results.
Branding
You can override certain Template settings for a particular domain such as cookie policy URL, color scheme, and logo. You can use this feature when you would like to use the same layout and legal text across a number of domains, but have specific branding requirements applicable to singular domains.
Login Settings
Login settings are unchanged in Cookie Consent.
Categorizations
The Categorization has replaced the previous drag and drop Cookie List page. This page summarizes information found by scanning domains, such as cookies, SDKs, hosts, and categories.
Cookies
The Cookies tab allows you to filter based on lifespan, status, and category. You can also search for specific cookies, domains, or hosts. Cookies can be manually assigned to categories in this tab. You can also add any additional cookies not found during scanning that you wish to disclose.
SDKs
The SDK tab displays the SDKs found by scanning different applications. You can search and filter SDKs and categorize them. You can also manually add any SDKs you wish to disclose.
Hosts
All of the third party hosts with cookies on your websites are shown in the Hosts tab. You can search for specific hosts and edit the display name, policy URL, and Id of these hosts. This eliminates the need to create sub-groups while disclosing the cookie host used on your websites.
Categories
In the Categories tab, you can review, edit, and create categories for cookies and SDKs. The central management of categories ensures consistent categorization of cookies and SDKs across all of your domains. This also you to quickly update the cookie category description and apply the changes to all of your Templates.
Geolocation Rules
Geolocation Rules allow you to control what site visitors will see based on their location. A Default Geolocation Rule has been created in your environment and is automatically assigned to new tenancies. You can also create additional Geolocation Rules in this tab. Your newly created Geolocation Rules can be assigned as the default Geolocation Rule.
This feature allows your Legal Team to set policy for your company once and be enabled automatically. Role based access can be enabled to control who can edit Geolocation Rules.
You can configure consent settings by defining the Template and Consent Model to use in specific grographic regions. You can also determine if consent records will be collected and the behaviors that will close the cookie banner. If you are using IAB TCF, you will need to decide which IAB vendors you use by selecting a vendor list. By default, the Global IAB Vendor List is assigned as the Vendor Version List.
Assigned Domains and Applications
In the Assigned Domains and Assigned Applications tabs, you can quickly view the domains and applications to which the selected Geolocation Rule is being applied. You can also assign the Geolocation Rule to additional domains or applications.
Templates
The Templates tab is where you will configure the user interfaces for your websites, applications, and Connected TV services. There are preconfigured templates for designed to comply with common compliance laws and frameworks, such as GDPR, CCPA, and IAB TCF. After selecting a Template, you will be able to customize the compliance solution.
Banners
The Banner is the first element site visitors will see. The Banners tab allows you to customize the styling, content, and behavior of the Banner. Any behaviors that close the banner have been moved to the Geolocation Rules tab, as they affect how consent is given.
Preference Center
The Preference Center tab can be used to customize the styling and content of the Preference Center. You can include a link to the Preference Center on your website, which is typically placed in the footer. The Advanced Settings can be used to show groups of cookie categories that can be opted in or out of individually.
Cookie List
The Cookie List serves as your third layer of notice. In the Cookie List tab, you can edit the cookie table names, what information is displayed, and the style.
Vendors
The Vendors tab has not been changed significantly for Cookies Consent except for adding Global IAB Vendor List as the default vendor list. The purpose of these settings is to determine which IAB vendors to use and if they establish a 'legitimate interest' as a legal basis for processing. You can allow a vendor to use 'legitimate interest' selecting the vendor and clicking the Activate button.
Integration
The Integration tab provides you with a tables of your cookie banner scripts and mobile scripts. You can select the individual domain or application to implement your solutions. The tab will provide step-by-step instructions to implement the script. To publish a script, click the Publish button. This will present you with the Test CDN and settings related to how language will be determined. When testing is complete, click next to download or copy the production script.
Test Script versus Production Script
The Test Script and Production Script are similar, but differ in a few key details. When a cookie is writen, it is written to a specific domain, such as .example.com or www.staging-example.com. A cookie written in .example.com is sent in any requests for the root domain. However, if you were on a different domain, like www.staging-example.com, you would not be able to write a cookie on .example.com. Therefore, if you use a production script on the staging domain, the cookies used by OneTrust would not be written and the consent would not be stored. To resolve this issue, the Test Script writes cookies to the domain it is currently on and allowing it to behave like the Production Script.