_ga _gid _gat before consent

Hi @capte,

The Google Analytics tags which create those cookies are being fired from your GTM container, but they currently do not wait for consent to be obtained; and as a result the cookies are also set without consent.

There are a number of approaches to solve that:

1) Google Consent Mode (Premium, Recommended)
When using the Complianz Premium plugin, you can follow the steps under “Configuring Google Tags with Tag Manager” in this article to implement Consent Mode V2 for GTM. Google will then restrict or allow Google tag functionalities based on the provided consent in Complianz.

2) Fire tags based on consent using Complianz triggers/events
By following the steps in this article under (Step-by-step) Firing tags based on consent in Tag Manager, you can configure your Google Tags to fire on a Complianz consent event/trigger (such as Statistics consent), instead of your current trigger, which does not wait for consent to be obtained.

3) Block Google Tag Manager entirely before consent
If you’d rather block Tag Manager entirely before consent, thereby blocking all of the tags that it contains as well, you can implement the GTM script manually as described here: https://complianz.io/how-to-set-google-tag-manager-after-consent-and-is-it-needed/

Kind regards, Jarno

Hi, @jarnovos,

@capte asked about an event, for me, making it is the same… I have events like ‘purchase’ or ‘view_cart,’ but they start before consent. I think that this is about JavaScript priority.

1. I have Premium, but I don’t see Complianz settings the same as in your article article look: https://nimb.ws/g3IlY4. I know it is in Slovak, but you have to see that these settings are completely different… only Google Tag is the same.
2. I don’t know how to set triggers for your Complianz event because it is before your statistical event. Events like ‘view_cart’ and ‘purchase’ start before consent and have denied cookies, even if the user has already approved them. https://nimb.ws/vL5B8R
3. When I stop use complianz to add GTM tag on me web consent mode disappears and consent update dosen’t work.

But, I have issues that you mentioned in your answer. The G-Tag for Analytics fires behind this event of mine, and GTM reports an error on this tag. I had set up the G-Tag trigger for your event ‘cmplnz_event_statistic,’ but here is an error, and analytics doesn’t measure.

“This Google tag should have been loaded before the gtag(‘event’) command was called. Use an on-page gtag(‘config’) command or a Google tag in Tag Manager to load G-GTSMD9VWVX when the page loads.”

Can you provide guidance on ordering the priority of your JavaScript?

Hi @omaluj,

I don’t think this has anything to do with JavaScript priority, but I would start by verifying that you don’t have any other implementations of GTM on the page aside of the Complianz implementation.

If you are using Consent Mode, the idea is to fire the tags on a trigger like All Pages instead of a Complianz consent event; so that Google Consent Mode can determine which functionalities of these tags are allowed to fire based on consent. Please see: https://complianz.io/consent-mode-for-7-0/

But even when using Consent Mode, you could still create additional conditions on a tag before it fires, e.g. an additional condition requiring that a cookie called cmplz_marketing exists & contains the value allow.

In any case, the WordPress Forums (and the thread posted by this user) concerns the Complianz Free plugin. Please reach out via complianz.io/support/ for further questions about the Premium plugin.

Kind regards, Jarno

Thanks that works 3) Block Google Tag Manager entirely before consent ! ??