Do I need it?
With shared consent enabled, our system can track the user's consent across multiple domains and subdomains.
Let's say your website takes the user on a flow going from one domain to another. For example, a user first enters your website on its English version example.com and then is redirected to the Danish version example.dk. In this scenario, typically, your users will get prompted with the consent pop-up twice - first on the English domain and then again on the Danish one.
You can provide a better user experience to your website visitors by prompting the consent pop-up only once at the first entry point using the shared consent feature.
Criteria for this setup
The domains that need to share consent must be under the same consent solution.
Third-party cookies must be allowed in the user's browser.
How to enable shared consent
Navigate to the consent solution on which you want to enable the feature.
Go to the Settings tab and press the "Shared Consent" button.
It can take a few minutes to see the effect live on the website.
How does it work?
Typically our solution sets one single cookie in the user's browser after they've given their consent. Still, if shared consent is enabled, then we also place another cookie named CookieInformationConfig.
The cookie is a third-party cookie set by our domain policy.app.cookieinformation.com, making it possible for our script to track the consent across domains.
Is this legal?
Yes, it is legal because we only track the user's ID through initial consent. The tracking is not processing personal data.
Will that affect your compliance? No, it will not.
Tracking/syncing settings across a domain is currently only possible through the use of third-party cookies. This logic means it will not work if the browser doesn't allow setting these cookies or deleting them after a specific interval.