Problem with using GTM4WP simultaneously

Thinking error by me:

GTM4WP can continue to do the full job (incl. container implementation). It’s up to the trigger configuration in GTM (using trigger groups) to fire tags or not based on the complianz events.

Am I right now?

Hi @ewerkstatt,

You are right: as we integrate with GTM4WP you can configure this plugin to your liking as Complianz will implement the GTM code. You can then use custom events like cmplz_event_functional and cmplz_event_0, etc. to fire tags based on provided consent.

For a detailed tutorial, please refer to this article: https://complianz.io/definitive-guide-to-tag-manager-and-complianz/

Let me know if you need any further assistance.

Kind regards,
Leon

Yeah, I know, thank you, Leon. But I have to do it the other way:

* GTM4WP implements the container as well as the dataLayer for ecommerce. Thus nothing different from the time before the GDPR.
* complianz provides the consent-events, which I use in trigger groups for firing tags based on certain clicks or form submissions or whatever “fancy” triggers I have set up.

It is currently not possible to use complianz for implementation of the container together with an active GTM4WP, although GTM4WP can be configured to only provide the dataLayer.

The tutorial is okay to begin with, but it stops when it should approach the more advanced usage of the GTM.

BTW: my wish for the roadmap is something which allows to avoid the creation of excessive trigger groups. That is to be able to use the less elaborate trigger exceptions instead of many trigger groups one has to create.

E.g. events like:
cmplz_event_0_denied, complz_event_marketing_denied, etc., which are “true” before the user gives the consent or denies it, and set to “false” in case of a given consent.

Similar to what cookiehub provides … and this could be a feature of the premium version.

What do you think?

Hi @ewerkstatt,

If GT4WP is active, and the integration enabled in Complianz. You can’t implement the GTM code with Complianz, as it is expected to be implemented and configured in GTM4WP.

You can now use the custom events described in the article to configure triggering the tags, which in return communicate with the data layer variables configured in GTM4WP.

I understand what you mean with the extended events. I see what I can do in the short term, but won’t be a premium addition but available jin Free.

Let me know if you have any questions,
regards Aert

Hi Aert,

yes, I’ve seen that. It’s only that GTM4WP allows to disable their own container implementation (for using only the dataLayer provided by them). And in this single case it would be fine to use the container implementation of complianz.

But it is clear for me that it would be too much for your plugin to monitor certain settings in other plugins. Therefore I recommend to leave it entirely to us, the users, to decide this (maybe just give a warning, but not to disable). If someone decides to use both implementations of the same container, then it’s up to him/her.

Hi @ewerkstatt,

Thanks, we will revisit the integration.

regards Aert