double view tracking with consent prompt activated

[MountainMaster]

Hallo,

I do currently have a problem with Tealium IQ. All tags are send twice.
This does happen when the "consent promt" is activated but is not enforces because of the loadrule.

Is this a known issue?
I can pm the affected URL. The Setup is Live till this friday.

Greetings

[BenStephenson]

Hi @MountainMaster 

Do you have any code explicitly calling utag.view()?

Tealium will automatically call a utag.view when it detects the page has loaded, and you can force another page view by calling that function from the site code (or code within an extension).

There is a configuration option to suppress the automatic page view call by setting 

window.utag_cfg_ovrd.noview = true;

in a preloader scoped JS extension.

[MountainMaster]

Hi @BenStephenson ,

Thank you for your answer.

There is no code explicitly calling utag.view(). It is defenitly a problem with the activated consent promt. The problem only occurs when the consent promt load rule is not matched and there is no consent cookie present.

The Opt In was only activated for a test and is now deactivated again.

[BenStephenson]

Hmm, that's odd then. I've never seen that behaviour before.  I think someone from Tealium will need to look into this...

[warren-li]

Is there any solution for this issues,

We too explain the same issues, where consent turn on and it will automatic trigger two view event.

We spot there is two line in JS that do utag.view, so we comment and tried remove the lines.

But this only reduces the two view event into one view event.

But thats not ideal, as we don't want any view event trigger when consent prompt is turn on.

We already have extensions set on preload to set 

window.utag_cfg_ovrd = window.utag_cfg_ovrd || {};

window.utag_cfg_ovrd.noview = true;
window.utag_cfg_ovrd.consentPeriod = 365;

but it seem the consent prompt is completely ignore it.

Any suggestion to resolve this?

[LordLingham]

Hi @warren-li 

This is likely due to an older version of consent manager running in the profile.

The original version had an issue which would sometimes cause the behaviour you are seeing - i'd recommend you reach out to support who will be able to upgrade your version of consent manager, which should resolve the issue for you - or if this isn't the cause of the issue, we'll be able to tell you what is!

[warren-li]

Thx @LordLingham 

Been contact Support, and they have upgrade our consent manager to v2.0 and this have resolve the issues.