Eulerian

This section describes how to control what tags are embedded on your website when using Eulerian for managing tags.

Events and variables used by Eulerian are detailed in this documentation.

Please note that Eulerian can only be used for the GDPR regulation. You can contact us at [e-mail] if you have a specific query to use Eulerian for other regulations.

Overview

The key idea of the integration is that Didomi pushes consent information into Eulerian by firing calls to indicate when tags that require consent for a specific category/vendor can be loaded. You should then configure Eulerian to only fire tags after consent has been collected for each category/vendor.

Categories in Eulerian are linked to Didomi vendors. When we speak about categories, we speak about Didomi vendors, which correspond to an Eulerian category.

On your side, the integration relies on linking your tags to categories for vendors that do not support the IAB framework to make them fire only once consent is collected. Tags that do not require consent must be linked to a noconsent category that will be triggered on every page load automatically.

For instance, after a user gives consent to the vendor google, the SDK will push the category google to Eulerian with the status allowed. The tags setup in Eulerian and linked to the google category can then be fired.

Make sure that our SDK is setup

Before continuing, please read our section on setting up our SDK to learn how to do the initial setup of your tag. It is particularly important that our tag gets embedded before all the other tags on your page.

Configure the Didomi / Eulerian integration

Step 1 - Enable the slave mode for the Consent Management Platform

First, contact Eulerian's support and request them to enable the slave mode for the Consent Management Platform. This will allow Didomi to interact with Eulerian for sharing the consent status fo the user.

To know more, please read the section 'ACTIVATE THE MASTER/SLAVE MODE OF THE EULERIAN CMP' of their documentation: https://eulerian.wiki/doku.php?id=en:modules:collect:gdpr:master-slave_cmp

Step 2 - Enable the Eulerian integration

Enable the Eulerian integration in the Integrations tab of your consent notice.

Eulerian integration in the Didomi Console

Embedding the Didomi SDK through Eulerian

We recommend not embedding the Didomi SDK through Eulerian. By being directly on your pages, the Didomi SDK can load faster and also ensures that IAB vendors can detect a CMP on the page as soon as possible.

Embedding the Didomi SDK through Eulerian will result in less consents being passed to vendors and a lower consent rate from their perspective.

Step 3 - Add the Eulerian collector script into your page

Didomi uses the Eulerian collector to send data. The collector script is not included by default in Eulerian. To access it you need to copy and paste the collector script in your page.

To access this script, go to your Eulerian dashboard into Collection > Configuration > Site-centric > First-party data > EA_collector configuration and copy the asynchronous version from the Eulerian website. Add the EA_collector script onto your website.

Step 4 - Add the categories into Eulerian

You need to create categories that will be linked to a vendor and used to decide when to load each tag in Eulerian. Vendors that do not require consent need to use a specific category called noconsent (More information below).

To create a category, go to Activation > Consent Manager > Show list of consent managers.

Add a category with the name corresponding to the vendor you want to condition. To know more about the name to use, please read this section.

You need to create a category for every vendor tag that you need to condition on the user consent status.

For instance, to load a Google vendor tag, create a category with the following condition:

• name equals didomi:google

• Link your Google vendor tag to this category

With this category configured, your tag will be fired when the page loads AND consent has been given on a previous page for the vendor Google or when the user gives consent to Google in the banner.

Vendors

The vendor name is only pushed in the list of categories if the user has given consent to it and to every purpose required by that vendor.

Vendor IDs are prefixed

• iab: for IAB vendors (ex: iab:1)

• didomi: for Didomi vendors (ex: didomi:google)

• c: for custom vendors (ex: c:vendor-id)

Make sure to include the prefix in your Eulerian category.

How to find your vendor ID?

To find your vendor ID, in your Didomi account, go to Consent notices -> Open your notice -> Regulation -> Edit vendors and Purposes: copy the SDK ID.

Copy the SDK ID to have your vendor ID

Create a category for tags that do not require consents

Vendors/tags that do not require consent need to have the noconsent option (last row) activated. IAB vendors need to have this option activated as well as they will automatically collect the consent status from Didomi through the IAB TCF API.

Step 5 - Link your categories to your tags

Once you have all your categories created. You can create and link your tags to the categories/vendors.

To create a tag, go to Activation > TMS > Tag Management System.

When you create your tag, link this tag to the category related.

Don't forget to activate your tag once it is created

Step 6 - Activate the slave mode of the Consent Manager

To activate the slave mode, go to your Eulerian dashboard in Activation > Consent Manager > Show list of consent managers

Once you are on the page, create a new consent manager (slave/asservi) and use didomi_eulerian as cookie name. Make sure this consent manager is enabled and is the only one enabled.

Be aware that this step will activate the slave mode and block by default, all the categories. Make sure to test in your staging environment first.