Skip to main content
Didomi builds technology that lets organizations place customer consent at the core of their strategy by offering a powerful Consent Management Platform (CMP) that organizations can deploy on websites or mobile apps. Kameleoon reads consent policies within the Didomi platform, so you can run A/B tests and personalize the performance of a configuration variant (for example, notice format, content, banner vs. pop-in). Key benefits:
  • Automatically manage user consent through Didomi CMP with no additional setup needed.
  • Deploy different variants of the Didomi tag configuration through Kameleoon and automatically measure the difference in consent rates.
Kameleoon is also IAB TCF compliant

​
Integration with Didomi CMP

Kameleoon provides custom integration with Didomi CMP. Kameleoon automatically reads the consent policy within the Didomi platform for both Kameleoon’s experimentation and personalization modules. With Kameleoon’s integration, you can also run A/B tests to test a variant’s performance (for example, notice format, content, and banner versus pop-in).

​
Enable Didomi in Kameleoon

First, you need to add Kameleoon as a vendor in Didomi’s CMP.

​
Configure your Didomi notice

Follow this documentation provided by Didomi

​
Configure Didomi in Kameleoon

You need to trigger the Kameleoon snippet independently of Didomi and add it directly to the source code of the page to prevent flickering in your experiments and personalizations.
  1. Log in to your Kameleoon account.
  2. Click Admin > Projects.
  3. Click Edit on your project’s row.
  4. Click the Scripts tab.
The Scripts tab with the Global custom script and Variation selection script editors

​
Global custom script

The Global custom script insert lets you link Kameleoon to Didomi. Kameleoon executes any JavaScript code you add in this insert every time the page loads. This feature is often used to add a complex tracking code or integration to other solutions. To activate the bridge between Kameleoon and Didomi, click Edit next to Global custom script, then copy and paste the code below into the editor:
With this code, any time a visitor activates or disables Kameleoon’s consent from the Didomi pop-in, Kameleoon receives a notification and activates or deactivates the Experiment or Personalization module (depending on whether the visitor grants consent). Click Save changes to apply the changes to your configuration. The last step is setting up your project’s consent management policy to Consent required in both the For A/B tests and feature experiments and For personalizations sections. Read this documentation to find out more.
The Consent tab with the three consent policy sections
To set up the consent management policy on your project:
  1. Click Admin > Projects, click Edit on your project’s row, then click the Consent tab.
  2. In each of the For A/B tests and feature experiments and For personalizations sections, click Edit, select Consent required in Consent policy, then click Save changes.
Kameleoon will now collect and store data based on the consent provided by the users from Didomi CMP. With Kameleoon’s integration with Didomi, you can run different versions of your consent notice by creating an experiment through Kameleoon. Follow these guidelines. You’ll have to run a technical experiment. This experiment lets Kameleoon run the experiment before the visitor provides consent (which is necessary if you want to A/B test several versions of Kameleoon’s consent pop-in). Note that you can’t analyze an experiment’s results in Kameleoon’s reporting tool as Kameleoon doesn’t collect any data. However, Kameleoon will still send analytics data to your default analytics platform. Below, you’ll find an example of an experiment that A/B tests two versions of the consent notice: pop-in versus banner.

​
Pop-in notice version