GTM – opt out not working

  • Resolved grizdev

    (@grizdev)


    2 years, 5 months ago

    I’ve been following the instructions on https://complianz.io/using-exceptions-in-tag-manager-based-on-consent-status/

    I am using Google Tag Manager for WordPress along with Complianz on a US website, and only have GA4 and UA tags firing in GTM. Both tags are set to fire on all pages, but I have a blocking trigger set as an exception for when the cmplz_statistics cookie has the value “deny”. And yet, the GA tags still fire.

    In GTM, I created a variable mapped to the 1st party cookie name “cmplz_statistics”.
    The UA and GA4 tags are set with a firing trigger of all pages, and an exception for the blocking trigger.

    I think I’m missing something basic and fundamental here, any tips would be great

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter grizdev

    (@grizdev)

    okay – just tried something, not sure if this is considered a “best practice” or not. Since my goal is to fire the Google Analytics tags by default until someone opts out, I created a companion trigger for when the cmplz_statistics is not set to “deny”. Instead of the built in GTM “all pages” trigger, I use this new, not denied trigger, with the denied trigger as the exception. It seems to work, but I’m not sure if this is a good idea or not.

    Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @grizdev,

    An easier approach is to use custom events; https://complianz.io/definitive-guide-to-tag-manager-and-complianz/ from #3 onwards if you used to GTM.

    However, setting statistics by default, but only opt-out when the user wants is a bit different.

    Right now it’s: Blocked before consent. Or opt-out.
    You want: Not blocked before consent, but opt-out.

    I need to see if I can do something similar in Tag Manager. regards Aert

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘GTM – opt out not working’ is closed to new replies.