Complianz not firing first?

It doesn’t matter that Complianz loads later. The plugin blocks services where required on the server side, and loads last on the client side, for performance reasons. When tracking with GTM, you need to configure GTM to listen to Complianz events.

For more information on how to do this, see this article:
https://complianz.io/definitive-guide-to-tag-manager-and-complianz/

Thanks Rogier.

I have followed this up to 3.2/3.3 – i’m not sure what tag to attach the triggers to. I have tested using the GA tag but this doesn’t seem to fire.

• This reply was modified 2 years, 9 months ago by grombleton.

Hi @grombleton,

For Google Analytics, that would be cmplz_event_statistics. Did you follow all instructions mentioned in the article?:
https://complianz.io/definitive-guide-to-tag-manager-and-complianz/

Kind regards,
Leon

Hi Leon

I have followed the instructions, at least I feel I have! I attached the triggers to my GA tag, which is the Google Analytics – Universal Analytics configuration.

Hi @grombleton,

It looks like the Analytics tag is currently being fired both on the “All Pages” trigger, as well as the “cmplz_event_statistics” trigger. That results in the tag being fired both on the initial pageload without consent, and once more after providing consent for Statistics in the cookie banner.

I assume that if you set the Analytics tag to only fire on the “cmplz_event_statistics” trigger, that would result in the Analytics tag waiting until consent has been obtained.

Kind regards,
Jarno

Hi Jarno

Thanks for that, definitely worth a try. If the Analytics tag is only firing on _statistics, what tag would cmplz_event_functional and cmplz_event_marketing fire on?

Hi @grombleton,

While I’m not sure if I fully understand the question, I hope the below explanation helps to clarify;

When the page/cookie banner loads and no consent had been obtained yet, the event “cmplz_event_functional” is emitted (as this category is “always active”). So, if you have any tags in GTM that are set to trigger on “cmplz_event_functional”, these will fire when the banner loads, without consent being required.

Events such as “cmplz_event_statistics”, “cmplz_event_marketing” are emitted when consent for those categories has been obtained in the Cookie Banner. So at that point, your GTM tags that have their firing trigger set to one of these events will be fired.

Kind regards,
Jarno

• This reply was modified 2 years, 9 months ago by jarnovos.

Hi @jarnovos @grombleton,

I see a duplicate implementation of GTM as well, one is in the header and can be removed. Including the iframe pixel, which loads when javascript is disabled.

This leaves only the GTM code from Complianz. This UA tag should be triggered with a cmplz_event_statistics custom event which thus equals ‘cmplz_event_statistics”

https://snipboard.io/gIxWoO.jpg

regards Aert