You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am implementing Complianz for a client who is using Wordpress and Tag manager. I followed your documentation step by step and integrated GTM through your app, disabling it everywhere else.
While the events (e.g. cmplz_event_statistics) fire correctly depending on user choices, the Consent State on GTM is not updated and remains 'denied' all the time regardless. This is a serious issue. Please see attached screenshot.
This renders the app pretty much not usable with any Consent mode on GTM. The suggested method using 'cmplz_...' events as triggers is just doesnt' work with Google tags with built in consent in the way Google recommends.
Are you planning on fixing Consent Mode update after user interaction? Or is the current setup by design?
There's plenty of apps out there who work seamlesly with GTM at this point.
Looking forward to hearing from you.
The text was updated successfully, but these errors were encountered:
Hi there,
I am implementing Complianz for a client who is using Wordpress and Tag manager. I followed your documentation step by step and integrated GTM through your app, disabling it everywhere else.
While the events (e.g. cmplz_event_statistics) fire correctly depending on user choices, the Consent State on GTM is not updated and remains 'denied' all the time regardless. This is a serious issue. Please see attached screenshot.
This renders the app pretty much not usable with any Consent mode on GTM. The suggested method using 'cmplz_...' events as triggers is just doesnt' work with Google tags with built in consent in the way Google recommends.
Are you planning on fixing Consent Mode update after user interaction? Or is the current setup by design?
There's plenty of apps out there who work seamlesly with GTM at this point.
Looking forward to hearing from you.
The text was updated successfully, but these errors were encountered: