- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
04-03-2019 07:26 AM - edited 04-03-2019 07:26 AM
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
04-04-2019 08:48 AM
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.
04-05-2019 01:36 AM
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.
04-05-2019 06:49 AM
Hmm, that's odd then. I've never seen that behaviour before. I think someone from Tealium will need to look into this...
01-23-2020 07:11 AM
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?
01-24-2020 09:34 AM
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!
01-27-2020 12:19 AM
Thx @LordLingham
Been contact Support, and they have upgrade our consent manager to v2.0 and this have resolve the issues.
Copyright All Rights Reserved © 2008-2023