Hi the case was more complex than I thought. As you can see in comment #18 the add_to_cart event was triggered before consent which lead sometimes to some problems for my client.
I ended up with configuring GA4 tag for cookie_consent_update trigger. For commerce events I've created a patch that moves events in dataLayer array after all consent is set.
kewin.nammert → made their first commit to this issue’s fork.
kewin.nammert → made their first commit to this issue’s fork.
For anyone who is struggling with the above problem. For me events sometimes were sent without consent info. In the gtm configuration, just create a trigger group (per tag sending data to GA4) containing cookie_consent_update trigger and desired trigger for the tag.
Hey that you for the report. We added such possibility. From now on you can use webform tokens in custom template.
kewin.nammert → made their first commit to this issue’s fork.
Hello thanks for the issue! Our organization uses its own standards. I have added configurations to the module.
kewin.nammert → made their first commit to this issue’s fork.
kewin.nammert → made their first commit to this issue’s fork.
kewin.nammert → made their first commit to this issue’s fork.
kewin.nammert → made their first commit to this issue’s fork.
I understand. In that case, is there any way to solve the problem of sending e.g. ecommerce events from google_tag module after consents load. I see a similar problem in #18. gtag('consent', 'default'... is probably set too late no? I wonder if there is a way to set consents before gtm.init.
Referring to the google documentation . The consent default event should execute before the gtm implementation script hence the problem with the consent not being set on the consent initialization trigger. To avoid that you can delay all tags trigger on consent_update which is not ideal. It's better to adjust the patch.
As a company we would like to contribute to the module. Are you looking for co-maintainers?
kewin.nammert → made their first commit to this issue’s fork.
I've noticed that moving labels from nested #attributes to the main array fixes the problem, but I'm not sure that's a good solution. If it is I can do the MR. Somehow passing the values as Markup which shouldn't be escaped doesn't have an effect either. Any ideas why?
I wasn't able to able to fix this problem by myself because I don't have access to the javascript source files.
kewin.nammert → made their first commit to this issue’s fork.
Hi, any plans for a D10 release? I've tested the patch and it looks fine.
kewin.nammert → made their first commit to this issue’s fork.
wotnak → credited kewin.nammert → .