How to test
- When page is loading for the first time you should see a banner. Accept this consent
- Navigate back to the Domain page
- Moving back and forth you don’t get the banner anymore. Presumably you have stored consent for two different pages, which should be displayed in the consents window (although this would look the same if you made the same choices)
- You can clear a page’s consent using the Reset consents to start over.
Banner
The most important element of information given to the user is the consent banner that is displayed in the bottom right corner of the screen.
It summarizes what the user needs to know to be well informed without hindering the user experience and interaction with the website.
Navigate
When the user navigates to another page of the website, the banner is closed and consent is stored. Click on the button below to navigate to the different page. The banner will be hidden and the list of consents by vendor shown below will be updated.
To DomainPreferences manager
Click on the button below to open the Didomi preferences manager to give/remove consent and see what vendors the website is using.
We recommend putting a link to open this preferences manager on all pages of your website.
Reset
If you have closed the banner and want to show it again, click on the reset button below to remove all your consent information.
Consents
The consent string is the central part of the IAB framework: it encodes all the consent information for the user, by purpose and by vendor.It is generated by Didomi from the consent collected and shared in real-time with third-party vendors on the website to guarantee that the consent information flows freely and efficiently.
Here is your current consent string for this page:
You could copy TCF string and decode it here: TCF IAB String decoder
Configuration object
To separate consent from the domain we can define storage names for consent tokens in the configuration object embedded in the website page.In this page we have
didomiConfig with cookies object that defines custom token names: didomiTokenCookieName and iabCookieName .
The user consent will be stored under these names and will be separated from the domain level consent status.
<script type="text/javascript">
window.didomiConfig = {
website: {
apiKey: "03f1af55-a479-4c1f-891a-7481345171ce",
name: 'Didomi',
vendors: {
iab: {
version: 2,
all: false,
include: [4],
},
},
},
cookies: {
didomiTokenCookieName: 'custom_cookie_name',
iabCookieName: 'custom_iab_cookie_name',
},
};
</script>