Consent Management - fire Tags after Accept

[PavelKrejci]

Hi all,

is there an in-built functionality to fire certain tags (e.g. web analytics) after clicking on "accept" in the standard Tealium Consent manager? The target is not to track the "Accept" click, but to have a standard page view call also for the initial pageview.

At this moment with the standard settings, we track only the second pageview, not the initial one with the consent layer window.

Thanks
Pavel

[michaelbenefiel]

The Explicit Consent Prompt notifies your visitors about tracking their activity on your digital property and to acquire their consent. By default:

• If a customer opts-out, the website will suppress all tracking activity and cookie storage that is not directly relevant to the digital experience.
• If the customer opts-in, the website can track user behavior (commonly using third-party services).
  • These tags will fire if you've opted in and click the confirmation button on your prompt.

However, the Consent Manager code can be fully customized and its code is accessible from the TIQ interface. For example -- if you're looking to fire the tags after they've opted in, but want to delay the tags from firing until the second page view of the session, you could update the logic to trigger when utag_main__pn equals 2. (utag_main__pn tracks the number of pages viewed during a current session).

I'd recommend giving our consent management overview a read to familiarize yourself with all the features of our consent management tool. 

Mike

[PavelKrejci]

Hi @michaelbenefiel, thanks for the quick reply!

When you say:
"If the customer opts-in, the website can track user behavior (commonly using third-party services).

• These tags will fire if you've opted in and click the confirmation button on your prompt."

Does it mean the tags should fire right after a user clicks on the "Accept" button? Because, at the moment, this is not our case. Also, I haven't found any info about that in the documentation or any fields to be configured.

Does it mean we have to modify the consent JS script or configure some click "Accept" button extensions?

Thanks
Pavel

[tculetto]

Hi Pavel,

The behaviour will depend on which version of the consent manager you are using. The V1 version (the default version) doesn't queue the pageview or other events before consent is given. So you would need to manually add a utag.view() call on the event listener linked to the accept button in the JS script.

However if you update to our 2.1 version of the consent manager this tracking call is automatically queued and sent.

To check if you have that version, look in your template section and the version 2.* should have 4 templates prefixed by "Consent Manager". if you don't have it please ask support to configure it for you.

Version 2 would have the header in the Consent Manager Central template

//tv:2.0.0

Version 2.1 (generated from a new install) would have 

//tv:2.1.0

Hope this helps,

Thomas

I'd recommend upgrading for this purpose.