davidkrogstrup

Hi Thomas

Sounds great – thanks for the update ??

My client has currently switched from Cookiebot to Cookie Information – so for now the problem has been solved that way.

Thanks again for all of your kind help.

Hi @duracelltomi

I just want to check in with you to see if there are any news on our issue? ??

Thanks for your update Thomas ??

If my client needs to launch the site before this issue is resolved, I′ll consider changing to another consent management platform.

I wish you a Merry Christmas and a Happy New Year ??

Hi @franz92

I did test the beta of the new GTM4WP version, which did not solve the problem. And since Thomas has reported, that he is able to reproduce the issue on his own test-server (when using Cookiebot), I assume that the final version of the plugin does not currently solve the issue.

Hi Thomas

Thanks a lot for your update – I really appreciate your dedication to trying to solve this issue even though this is not paid work ??

My clients new website is scheduled to launch on Monday 17th January – so I just hope and pray that you will be able to solve the issue before ??

But I′m happy to know that you have been able to reproduce the issue on your dev website, since I guess that′ll help you solve this issue faster.

Hi Thomas

Okay – just let me know if you need me to do, add or change anything on the site.

Hi @franz92

Thanks for your contribution. Let′s see what Thomas makes of this… ??

Hi @duracelltomi

I just wanted to check in quickly… how are things on your end regarding this issue? Are you still investigating? ??

“Wait for update” has now been changed to 100 miliseconds ??

I understand what you are saying and it makes sense that consent mode in some way is causing issues here.

But actually I have from the beginning changed the default consent state in the Cookiebot tag template to “granted” instead of “denied”:

But maybe this isn′t working in reality… ??

PS: I have never seen an option for turning off consent mode in Cookiebot anywhere (which is kind of frustrating)

Cookiebot settings has been reverted. Here is an updated GTM share preview URL:

https://tagassistant.google.com/#/?id=GTM-WN38ZLZ&url=https%3A%2F%2Fbof.octotest.dk%2F%3Fgtm_debug%3D1637690026948&source=TAG_MANAGER&gtm_auth=RUshyB8gtrClO8k2kK4TRg&gtm_preview=env-10

Just a thought… could it maybe have an impact, that the test-domain (bof.octotest.dk) has been added as a test-domain in Cookiebot instead of a regular domain?

Hi Thomas

Maybe it would be easier if I just gave you read-only access to the GTM container?

But to answer your questions:

– Cookiebot is added in GTM using the official tag template
– Cookiebot is loaded via the Consent initialization trigger
– I am not using the new consent related options in GTM

@ludyamano Thank you very much for explaining your solution in detail. For now I′ll wait to try it until Thomas has completed his investigation of the issue.

@duracelltomi What do you think of ludyamano′s suggestion… should we try that? Or do you want to investigate further why Cookiebot seems to create this issue in the first place?

@duracelltomi Cookiebot is now paused on the test site. Also, I′ve removed the cookiebot-variable condition for the 2 ecom triggers for the GA3 ecom events.

This means that ONLY the GA3 ecom events will fire at the site right now.

But it seems that the ecom data is comming correctly through now… so probably it is Cookiebot, that is conflicting with your plugin somehow…?!?

@duracelltomi My confusion is complete now… ??

Today I don′t experience what I did the other day. Now the ecom data is missing from the ecom events no matter if I′m logged into WordPress or not.

Also, the test-site is now running on the v1.14 beta3 version – but still the ecom data is missing in the GA3 ecom events (even though the ecom data is provided in the datalayer).

Do you have any other ideas for trouble shooting – or can I provide you with other information or accesses in order to assist you in this process?