- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
05-25-2018 03:24 PM
We are seeing some undesirable behavior with our Consent Manager prompt, and I am asking if anyone else using consent manager is seeing this same behavior.
We have set a display rule for the prompt to only display on our EU sites. So, it will not display on our non-EU sites, which are on the same root domain (different subdomains). This is working properly.
However, when a visitor first visits one of our non-EU sites, even though the prompt is not shown, the CONSENTMGR cookie gets created anyway, under the root domain. And so when the visitor subsequently visits the EU property, since that cookie exists, the consent prompt is not displayed.
So, the prompt works properly if the EU site is opened first. But does not work properly if a non-EU site is opened first, and then the EU site is opened.
If there are any users out there who have Consent Manager configured to load on some sites and not others, based on load rule, can someone out there verify if they see the same behavior? And has anyone yet found a workaround to this?
05-29-2018 03:27 PM
A quick update, for anyone else who may be having this same issue. Tealium support confirmed that indeed, Tealium adds a cookie with a consent value of TRUE whenever the load rules for the consent manager are not met.
So, in our case, we are using load rules to only use the consent manager in the EU. But the cookie is being stored with consent of TRUE in the US, when the load rule of region=EU is not met.
We are still working with Tealium support to identify resolution, and I will post here once resolved. In the interim, I would appreciate any create workarounds from the community.
05-29-2018 05:59 PM
The cookie defaults to the value of utag.cfg.domain. utag.cfg.domain by default is the top level domain. A quick workaround would be to overwrite the domain value to include the subdomain and this will no longer set the consent cookie at the top level domain, but instead at the subdomain level.
I hope this can work for you in the interim while a more permanent fix is put into place.
05-31-2018 02:54 PM
06-01-2018 06:47 AM
Thank you for the update @Krasner. Keep them coming!
Copyright All Rights Reserved © 2008-2023