The contents of utag.data doesn't necessarily go anywhere, so it's not usually problematic for it to contain a record of the current cookies.
However, if you've got a tag (such as Tealium Collect) that's picking up the whole of the UDO and sending it, then you can remove those variables as part of an extension. If you want to suppress just the cookie data from a specific tag, then create a tag-scoped JS extension thus:
for(var k in b){
if(k.indexOf("cp.") === 0){
delete b[k];
}
}
This will iterate over the tag payload and delete any keys that were derived from cookies automatically.
If you want to keep utag.data clean in the meantime, then run the code above in an After Tags extension, replacing the two references to b with a reference instead to utag.data.
I don't necessarily recommend doing this, but if you want to outright disable the feature entirely, then you could edit the master loader template (the backend template from which utag.js is derived) and locate the following code:
RDcp: function(o, b, c, d){
b = b || utag.loader.RC();
And add the following line:
RDcp: function(o, b, c, d){
return;
b = b || utag.loader.RC();
And that will stop those data items from ever being added to the UDO. However, it'll also break Privacy Manager, and indeed anything else that might look for cookies in utag.data, so I would only suggest doing that if you have a solid reason why you shouldn't be seen to be reading cookie data..
... View more
Expand/CollapseMenu
