05-15-2018 04:37 AM - last edited on 05-18-2018 03:02 PM by TealiumJustin
Seems like there is a problem with the cookie consent Preference window when it is displayed on site. Even after changing the preferences and clicking on Submit wont help in restricting the tags to load. Tags are still loading on the page. May I know when this will be fixed?
05-16-2018 08:51 AM
Apologies but where do we connect it. I have not seen any configuration like that. It's only about cookie getting saved after submit and when next time, the page loags, utag.js file will check for that cookie.
I did ask the tealium support about the same issue and they replied back telling that this is an on going issue at their end and they are trying to fix it.
05-22-2018 06:45 AM
Hi @mitchellt so am I seeing it right, that an manual loadrule has to be added to all tags to ensure the Tags to respect the Consent Cookie?
I kind of thought this would be automatic or the "key feature" of the built in consent promt. Whats the purpose of the "Tags to Omit" option when you could just not add the loadrule?
05-23-2018 12:37 AM
That is the not the case at all. It is just we need to add load rule to load the consent cookie window and it will take care of all the tags. When you click on submit, a cookie is created and that is checked and then tags are loaded. It is already mentioned in both cookie consent and cookie preference documentation provided by Tealium.
Also, the issue of preferences not getting saved even after clicking on Submit is an issue from tealium side and they are trying to reslove it, I have got a separate mail about this issue from them.
And yes, when you add tags in omit section, it will load irrespective of the selections made in preference window. I would suggest, dont add the tags, which you want to load all the tags, under categories section. Just add them in omit section. In that way, user will not be able to give his preference for those tags.
05-23-2018 01:56 AM
@nitishlamba thank you for your response.
unfortunately there is also a bug event when the conset change is saved correctly.
i have an open ticket regarding this issue. #40996
only two days left. 😏