Cross Domain Consent Sharing (= CDomainCS) is an Enterprise-Feature
You can enable this feature at the Admin Interface under Configuration → CMP Settings:
How does the feature work?
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.
Restrictions from Usercentric's side:
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 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 Browser: 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.
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.
Do you need further help?