In this article we will help you familiarize yourself with the concept of Cross Domain Consent Sharing ( CDomainCS) |
|---|
Relevant sections for this article
...
Cross Domain Consent Sharing (= CDomainCS) is a Business and Enterprise plan feature.
You can enable this feature at the Admin Interface under Configuration → CMP Settings:
...
As soon 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.
...
Improved consent sharing between subdomains
If you're using Usercentrics Cross Domain Consent Sharing (CDCS) your 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 section describes the needed steps to prevent this from happening.
Restrictions
| Note |
|---|
| 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> |
...
Restrictions
Usercentrics related restrictions
In order to make this feature work, the same Setting-ID has to be implemented in all (sub-)domains the consent information should be shared across. This is due to technical and legal reasons.
...
Browser related restrictions
CDomainCS does not work without sharing 3rd-Party local storage information across different browser tabs or if the user enabled special privacy settings within the Browser settings.
Safari and Any: CDomainCS does not work with Safari, since the browser does not share 3rd-Party local storage across different browser tabs. Due to this restriction, the feature can not share the iFrame's local storage across different tabs.
Firefox Browser: If the option “Delete Cookies” is enabled, the feature does not work, since Firefox clears the local storage for every new tab automatically, which prevents saving consents.
iOS browsers and iOS devices: Apple forces all browsers to use their built-in webkit, so CDCS does not work with them.
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.
| Info |
|---|
Cross Domain Consent Sharing is also available for TCF 2.0. |
...
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. |
...