In this article we will help you familiarize yourself with the concept of Cross Domain Consent Sharing ( CDomainCS) |
|---|
Overview
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Cross Domain Consent Sharing (= CDomainCS) is a available in the following plans: Business, Enterprise, Advanced and as well as Premium Add-on plan feature.
You can enable this feature at the Admin Interface under Configuration → CMP Settings:
...
How does the feature work?
As soon as CDomainCS is activated, our CMP injects an additional iFrame into the website and stores the consent information not only in the websites local storage but also in the iFrame's local storage. While the user switches to another (sub-)domain, the iFrames local storage is checked and if consent information is found, the consent information from the iFrame is stored into the local storage of the new (sub-)domain.
...
There is no workaround to circumvent these restrictions since it is a functionality of the browser itself or based on custom privacy settings of a single user to protect his/her personal data.
Different root domains restriction
From Chrome version 115 and going forward, CDomainCS does not work between different root domains (ex. a.com → b.com) because of restrictions that Google have imposed on third-party storage possibilites. This means, that our current implementation of CDomainCS now effectively only works between root domains and their subdomains (ex. sub.a.com → a.com → othersub.a.com).
Read more about the updates that Google have made to Chrome here: https://developers.google.com/privacy-sandbox/3pcd/storage-partitioning
| Info |
|---|
Cross Domain Consent Sharing is also available for TCF 2.02. |
...
Summary
| Tip |
|---|
After reading this article, you should be able to understand the technical as well as the legal concepts of Cross Domain Consent Sharing. |
Related Posts
...
...