Google Tag manager Script still inserted when deny all

Hi @roffalf,

The article proposes loading Tag Manager itself by default, and firing the individual tags in GTM based on the obtained consent in Complianz by using the Complianz events as the firing trigger of these tags.

You can either create the Complianz triggers manually as described in the article, or import them by following these instructions: https://complianz.io/importing-tag-manager-container/

After which you can create configurations like in the below example, whereby my Google Analytics 4 tag loads on “Statistics” consent, and the TikTok Pixel script on “Marketing” consent.

But if desired, you could instead block the GTM script entirely, before consent on a specific category is obtained (https://complianz.io/how-to-set-google-tag-manager-after-consent-and-is-it-needed/).

Kind regards, Jarno

Thanks for your reply.

I will try and block it completely.
As far as I know, in Germany you need consent before the IP can be shared with a third party (in this case Google), so I have to block that script completely if someone clicks “deny all”.

Regards

Ralf