Consent Preferences Settings - Omitting other tags as well

[ravi_thati]

Hi Team,

As part of Consent Preferences settings, we have configured all tags under 2 categories and Only 1 tag as "Omit tags".
But when we looked at utag.js file, the 'ot' array has some other non-omitted tags also.
And because of this, these are tags are always loading even if user opt-outs the 2 categories in preferences.

Can you please suggest on
1. how to resolve this issue ?
2. how this "ot" gets set in utag.js ?
3. Do we have control to update/change it through an extension/anything?

Code in Utag.js referenced:
applyConsentState: function() {
try {
var i, lc = utag.loader.cfg,
cs = utag.gdpr.getConsentState(),
ot = {
"147": 1,
"201": 1,
"83": 1,
"239": 1,
"125": 1,
"266": 1, //This is the ONLY tag, we intentionally omitted.
"110": 1
};
...

[mitchellt]

Hi @ravi_thati - you're going to have to run the debugger and watch the variable to see what's happening and where. And be sure that your utag loader template is up to date for good measure.

[ravi_thati]

This variable is pre-populated in the utag.js file. I believe its defined by Tealium during the bundling of utag.js depending on our consent settings of the profile.
So, the problem, this variable contains tag ID's that I have not configured in Tealium.

Anyway, would try out debugging once and update here if I found anything. Thanks!

[kathleen_jo]

Looking forward to hear how the debugging went @ravi_thati! 

[dan_george]

@ravi_thati

Can you tell me the names of the other omitted tags? I'm sure the Collect tag is one of them, but are there others?

[ravi_thati]

@dan_george, good point.
To my surprise, all those Omitted tags are "Tealium Custom Container" tags (and few of them are in disable state ). We do have other Custom Container tags, but they are not omitted, so we can't say "All" Custom containers are omitted also. Any insight on why this might be happening ?

[dan_george]

@ravi_thati After some research and speaking with the lead developer, this is a bug. I have submitted through the appropriate request and we will work to prioritize. I've informed your AM so they can follow and keep you informed of when the solution is released.

[ravi_thati]

Thank you very much Dan. That would really help us as we couldn't find any work around for it so far.

[dan_george · Accepted solution]

@ravi_thati the fix for this issue was released last night. I have tested on my demo site that had the same issue and verified it's working as expected now.

Cheers,
-Dan