Consent Management Platform (CMP) implementation overview
This guide provides an overview of the key steps for implementing Didomi, including auditing your website, creating a consent notice, managing vendors, configuring tags, and optimizing consent collect
Table of Contents
It serves as a roadmap, pointing you to detailed documentation links for each step. While designed for standard implementation projects, additional steps may be required for advanced setups, such as premium features, mobile application integration or CTV.
1. 📊 Audit your website
This step is optional. It is a helpful addition, but not required to set up Didomi on your site.
Run your compliance report: Didomi automatically generates a compliance report for your main domain. If you wish to get more reports, you can run it manually and our bot will scrap random pages according to the number set in the report settings.
Visualize results: Learn how to identify the trackers present on your site and evaluate their compliance.
2. 🎨 Create Your Consent Notice in Didomi
Create a Consent Notice in the Didomi Console: Follow step-by-step instructions to design and customize your consent notice.
3. 📂 Manage Your Vendor List
Didomi includes several available partners (Facebook, Twitter, and WhatsApp). Default purposes are automatically assigned to those existing vendors and cannot be directly modified or removed.
If you prefer not to use this list of purposes or vendors:
Create a Custom Purpose: Learn how to define specific purposes for collecting and processing user data that are unique to your business needs.
Create a custom Vendor: Set up custom vendors not already included in Didomi’s vendor list.
Create Categories for Your Purpose: Organize your purposes and vendors into meaningful categories for better user navigation and clearer consent choices.
Create a Required Purpose for Necessary Cookies: Ensure cookies essential for site functionality are categorized appropriately and marked as required.
4. 🔧 Configure Tag Management
To ensure tags are fired and cookies are deposited only if the user has given consent, you need to properly configure your tag setup.
Use Google Tag Manager: Configure tags dynamically through GTM.
Hardcoded Tags: If tags are directly integrated into your HTML, you can use Didomi’s SDK to control the loading of scripts based on consent.
Direct Integration
Understand IAB TCF Integration: Share user consent status automatically with IAB vendors selected in the Didomi console. This means you won’t need to manage tags to prevent them from firing before user consent through your CMP.
Configure Google Consent Mode: Enable Google services to respect user consent for advertising and analytics.
Understand Google Advertising Products as a Vendor: Gain insight into managing Google’s advertising products within the IAB framework.
5. 🚀 Deploy
Deploy Didomi script on every domain you want
CMP Web SDK: Explore technical documentation for integrating and customizing the web SDK.
6. 🏆 Optimize Banner Format
The best performing format is the pop-up banner appearing in the center of the page, blocking navigation while no consent choice has been made.
Consent notices with a “Continue Without Agreeing” link instead of the “Disagree” button may increase your consent rate.
For creative inspiration on cookie banners, explore our article featuring innovative examples and best practices: Didomi's Creative Cookie Banners.
Data Privacy Benchmark: Understand industry benchmarks to measure and improve your consent collection practices.
Consult with a legal advisor before finalizing your banner format. In some countries, such as Italy, pop-ups are discouraged.
7. Consent Management
Ensuring Vendor Tags Respect User Consent: Didomi’s CMP ensures that vendor tags and SDKs are only triggered when both the vendor and all associated purposes receive user consent.
Consent Re-collection: Consent is recollected every time new vendors or purposes are added.
Modify the Legal Basis for Your Purposes and Remove Legitimate Interest: Adjust purposes or remove legitimate interest where applicable to align with user consent choices and compliance.
Delete first-party cookies from the browser:
Integrate a script to remove first-party cookies from the browser when a user initially accepts cookies but later changes their preferences to refuse them.
Place the link to your consent banner in the footer of your website to ensure it is easily accessible. Please avoid adding it to the privacy policy, as it may be too difficult for users to locate. Paste this code where you want to visualise the link to re-open the notice:
<a href="javascript:Didomi.preferences.show()">Consent choices</a>
8. 🔍Check your implementation
Check Implementation and Cookie Behavior: Ensure your consent notice functions correctly by verifying its behavior, cookie compliance, consent updates, and vendor requests.
Last updated