Consent status doesnt change after acceptance

Hi @digihivecz,

What are you trying to achieve exactly? At the moment, you’re applying a template for Consent Mode, while you’re using a version of the plugin that doesn’t support Consent Mode.

Kind regards, Jarno

H, thanks for quick reply. Thats the thing. Is there a template without consent mode? I havent found it anywhere and still need implementation via GTM.

Hi @digihivecz,

I assume that you intend to fire GTM tags based on the provided consent in Complianz, correct?

If so, you can follow the instructions in this article under (Step-by-step) Firing tags based on consent in Tag Manager.

Kind regards, Jarno

Thanks, it finally makes sense now. If I have a tag that is triggered for instance by on site purchase, do I have to create a trigger group with ig. cmplz_statistics and my trigger? I have done so, but unfortunately it doesnt send any data to GA. If I revert to my original trigger it does. The goal is to not trigger this tag before consent is given.

Edit: I have tried the exception mode but the trigger fires regardless.

• This reply was modified 10 months, 1 week ago by digihivecz.
• This reply was modified 10 months, 1 week ago by digihivecz.
• This reply was modified 10 months, 1 week ago by digihivecz.

To verify, I have also set a test tag that should fire when statistics cookies get disallowed but it doesn`t. It gets back following upon closer inspection:

Filters (all filters must check to fire the tag):

• check – (Advanced) Cookie – Statistics = deny
• failed check – gtm.dom equals Denied Statistics (which is the exception trigger name)

As per the documentation

Event Denied Statistics is a trigger that fires on (Advanced) Cookie – Statistics?equals?deny where (Advanced) Cookie – Statistics is a 1st party cookie variable. Hence everything seems to be set up correctly.

• This reply was modified 10 months, 1 week ago by digihivecz.
• This reply was modified 10 months, 1 week ago by digihivecz.
• This reply was modified 10 months, 1 week ago by digihivecz.
• This reply was modified 10 months, 1 week ago by digihivecz.
• This reply was modified 10 months, 1 week ago by digihivecz.

Hi @digihivecz,

I’d say you could make a trigger that only fires if a cookie cmplz_statistics (called “(Advanced) Cookie Statistics” in the demo container) exists and equals the value allow.

For example, here I made a pageview trigger which fires if the cmplz_statistics cookie exists with ‘allow’ as it’s value.

Kind regards, Jarno

I have to use 2 triggers one with consent second with my trigger (purchase)- I used exception as in documentation and both versions- allow or deny launch the tag anyways unfortunately disregarding the denial of statistics cookies.

• This reply was modified 10 months, 1 week ago by digihivecz.
• This reply was modified 10 months, 1 week ago by digihivecz.

Hi @digihivecz,

I am unable to advise on specific tag configurations, although it seems to me that you can add another condition to the same trigger that you were already using, and apply a check for the cmplz_statistics cookie “allow” as mentioned above.

Kind regards, Jarno

@jarnovos

Are you saying that consent mode will NOT work unless we get the premium version of Complianz? I too have followed the steps in the consent mode for 7.0 and the simplified Guide – as it gives the impression that Google consent mode is configurable if we use your Compliance.io template – however my consent does not update either when I accept my banner.

Hi @drmsl,

Your assessment is correct. The Premium version of Complianz allows you to enable Consent Mode during the Wizard, and this is what adds the necessary code to update the Consent Mode parameters based on the consent choices as provided in Complianz.

Kind regards, Jarno