GTM Trigger Updates

Description

Hey All, the Consent Pro tutorial for GTM setup covers tags that make sense on All Pages. My client has a lot of tags triggered by links, page view or form submits.

How would these be handled as I can’t just add the custom “Consent Updated” trigger as it’s an OR conditional.

Any advice greatly appretiated.

NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.

Hey @Support-Luis, see you on a few ConsentPro threads. Not sure who could help with this. A more definitive list of what to do with different tags and trigger types than what’s in the tut video would be great. Another one I’m getting conflicting advice from online is the “UTM Attribution Script”.

Hey @hello6!

Apologies for the delay; I had to look into this a little more deeply.

Group triggers could be an option for this case, as they use the AND principle.

You can refer to this video on how to set it up

https://www.youtube.com/live/_hpszyzBkYc?si=YXOXLJX3fLiU9dyE

Let me know how it goes!

Hey @Support-Luis! thanks for this and it makes sense to me. I did however get the the below from Claude. On the first point, my understanding is that the tags won’t be scanned into Consent Pro without the “Consent Updated” trigger, but please confirm.

——

  1. It may not be necessary — if the Additional Consent Check alone is sufficient for these tags (which is what the Consent Pro docs imply), adding Trigger Groups adds complexity without benefit.

  2. The logic may still be off — a Trigger Group fires when ALL conditions are met, but consent-updated fires at a specific moment (when the user interacts with the consent banner). If a user accepts consent on the homepage and then later navigates to the Demo Thank You Page, the consent-updated event has already passed and the Trigger Group may never fire.

That second point is actually a significant problem — it could mean legitimate conversions don’t get tracked at all.

——

Hey @Support-Luis Can you advise on this? Thanks

Hey @Support-Luis, let me know if I need to direct this somewhere else. I need to get clarity as we’re sitting with an incomplete Consent Pro implementation.

Hey @Support-Luis, please advise or let me know who I can speak to - I need to get this completed.

Hey @hello6, I am so sorry, this thread slipped through my inbox.

On the first point, my understanding is that the tags won’t be scanned into Consent Pro without the “Consent Updated” trigger, but please confirm.

If the tags are not being picked up by the scan, you can remove the “Consent Updated” trigger and set them to fire on all pages. Consent Pro will detect which cookies came from GTM, so you can later add the Additional Consent Check.

For the other points mentioned by Claude, the Consent Updated tag fires on all pages after consent initialization, not only when the user interacts with the banner.

1 Like