No ecom data for gtm4wp.orderCompletedEEC event sent to GA3

@duracelltomi Are you still planning to look further into this issue and try to solve it… or should I try to find another solution? ??

I have an idea but it needs some more time.

GTM4WP generates the ecommerce purchase data layer when the data layer is generated in the head section of the page. Since the purchase event is now decoupled from the GA pageview tag, it is now safe to move this code into the body to be fired a bit later.

Do you have any test site where you can update GTM4WP to a dev version that needs testing on your end as well?

Yes, I should be able to install a dev version of GTM4WP on the https://bof.octotest.dk site.

Could you try this?

https://github.com/duracelltomi/gtm4wp/releases/tag/1.14beta3

This is the 3rd beta of the new plugin version, it includes many more changes than that, you can read the changelogs here:
https://github.com/duracelltomi/gtm4wp/releases

@duracelltomi I think I have found the source of the bug…

On this page – https://www.screencast.com/t/wQP3AjjhFys – I had previously unchecked all options, because I didn′t need any of them.

But I have earlier on another instance had a problem, when unchecking all these options… so I had the idea to try and select them all.

And after changing this, now I seem to get ecom data with all my ecom events for GA3.

Does this make any sense to you?

PS: I have not updated to the new version!

Hi,

This is very strange, those options shouldn’t have any effect on ecommerce tracking with WooCommerce.

From this what is more likely that perhaps there was some sort of page cache issue (?)

You are right… it wasn′t that I had selected all options under “Basic Data > Posts” that suddenly made the ecom data work correctly.

I′ve just discovered that whenever I′m logged into WordPress backed while testing, then all ecom events works just fine. But as soon as I logout of WordPress no ecom data is received in the GA3 ecom events.

Could this be caused by some page cache plugin, that is automatically disabled while someone is logged into WordPress?

Usually cache plugins exclude cart and checkout pages so normally it should work but in your case everything points into the direction that you experience cache issues.

I agree that my problem points in the direction of some sort of cache issue.

But still, my problem is not isolated to pages like cart and checkout – but seems to be present on ALL ecom pages on the site, including category and product pages.

How would you recommend me going forward here… should I ask my clients webdeveloper to try and change to another cache plugin?

What plugin do you use?

I am facing similar issues (see thread I started).

@franz92 Hmm, this issue only seems to get weirder and weirder…

I′ve talked with my clients webdeveloper and currently the cache plugin of the site (which is Litespeed) is not even activated on the site.

So something else must trigger this problem… ??

@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?

That is bad news ??

I will go through your site again tomorrow.

Hi @davidkrogstrup

Sorry for the delay.

As I mentioned earlier, my problem was identical to yours.

What worked here was changing the Ecommerce Event configuration. Instead of using the Data Layer, I set up my ecommerce event to use a new custom variable. You can see my configuration here.

My custom variable grabs the ecomm data from Data Layer. You can see how my variable is configured here, and the code I used bellow:

function() {
  var ecommerceData = {
    'ecommerce': {{Ecommerce}}
  };
  return ecommerceData;
}

Everything working fine since then. I don’t have a clear understanding of why this works, but it works for me.

Hope it helps.

@davidkrogstrup could you disable your consent tool just on your test site? (bof.octotest.dk)