• Resolved freyrh

    (@freyrh)


    I am trying to set things up so that when using GTM Consent Mode, I can make a tag fire when the Google consent type changes. The idea was to have 3rd party pixels load and fire after a user presses accept on the website. I know there is an option to trigger scripts from within the plugin, but I’d rather do it inside GTM as the website ecosystem I’m working with spans multiple domains and servers, and managing the pixels on a per-install basis might lead to desynced configs.

    Problem: When I make a custom trigger to fire on cmplz_event_statistic or marketing, and I’m using Consent Mode to manage a tag that has that trigger, the tag won’t fire because the gtag consent update is initiated AFTER the complianz event so Consent Mode perpetually blocks the tag from firing as the consent isn’t actually set at the time the trigger activated.

    Is there a way to get this working in a simple and straightforward manner that still uses Google Consent Mode to manage the tag firing.

    • This topic was modified 9 months, 2 weeks ago by freyrh.
    • This topic was modified 9 months, 2 weeks ago by freyrh.
    • This topic was modified 9 months, 2 weeks ago by freyrh.
Viewing 1 replies (of 1 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @freyrh,

    Note that Consent Mode is a feature in the Premium plugin; and we may only discuss the Free plugin on these forums.

    In any case, when using Consent Mode to handle consent for Google Tags, we recommend using a trigger such as “All Pages” instead of events such as cmplz_event_marketing, so that Google can update the tag functionalities based on the consent updates they receive via Complianz.

    Kind regards, Jarno

Viewing 1 replies (of 1 total)
  • The topic ‘Trigger tag AFTER GTM Consent has changed’ is closed to new replies.