In this article we will help you familiarize yourself with the concept of Cross Domain Consent Sharing ( CDomainCS) |
|---|
Relevant sections for this articleOverview
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
In this article we show you how to Here you can find out if you're using version 1 or version 2. |
...
Activation procedure (V1)
...
Cross Domain Consent Sharing (= CDomainCS) is a Business and Enterprise plan featureavailable in the following plans: Business, Enterprise, Advanced as well as Premium Add-on.
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.
| Info |
|---|
For Cross Domain Consent Sharing to work, implement the same Usercentrics CMP script using one Settings-ID on all domains that should share consents. |
Improved consent sharing between subdomains
If you're using Usercentrics Cross Domain Consent Sharing (CDCS) your Modern browsers are causing that website visitors might still see the CMP again when switching to another subdomain , for example mywebshop.com to checkout.mywebshop.com. Modern browsers are causing this behavior as they block the shared iframe provided by Usercentrics (s. Browser related restrictions). The following linked section in the documentation describes the needed steps to prevent this from happening: Improved consent sharing between subdomains.
| Info |
|---|
This solution will improve user experience for most browsers, however currently not for Safari users. We're actively working on this case to offer you a solution for Safari users too. |
Download the file cross-domain-bridge.html (right click → save as ...)
Upload this file to your webserver. It should be reachable from your main domain that is included in all of your subdomains. For example:
https://mywebshop.com/cross-domain-bridge.htmlBefore the Usercentrics CMP script tag, set the new location of the Cross Domain Bridge via the
window.UC_UI_DOMAINS.crossDomainConsentSharingIFrameproperty.
A complete example might look like this:
| Code Block |
|---|
| <html>
<head>
<script>
window.UC_UI_DOMAINS = {
crossDomainConsentSharingIFrame: 'https://mywebshop.com/cross-domain-bridge.html',
};
</script>
<script id="usercentrics-cmp" data-settings-id="XXXXXXXX" src="https://app.usercentrics.eu/browser-ui/latest/loader.js" async></script>
</head>
<body>
</body>
</html> Please note that there are still existing Safari browser restrictions that remain with this improved consent sharing. |
...
Restrictions
Usercentrics related restrictions
...
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
...
...