How to configure e-commerce events ?

Hi!

Which ecommerce plugin are you using? Because it’s way easier to just use a Google Analytics plugin for that platform, and then just run CAOS in compatibility mode. Then CAOS will make sure that plugin will use the optimized Google Analytics JS library.

Hope that helps!

Sorry for the delay.

Before I was on Zaraz (CLoudflare) for Google Analytics including e-commerce.

Since I switch to CAOS last week, I saw you were proposing to use Woommerce Google Analytics Integration and I’m trying to make it work

Hey!

No problem. No, I meant which e-commerce plugin (for WordPress) are you using? E.g. WooCommerce, Easy Digital Downloads, etc.

If you’re on WooCommerce, then yes, WooCommerce Google Analytics Integration is the way to go.

Hi,

Yes woocommerce. I hadn’t understood.. I’ve got a question with your plugin’s compatibility mode.

So, configured WooCommerce Google Analytics Integration as per your instructions.

However, I just saw that many of your powerful options (tracking code, tracking code position, Allow tracking) are disabled when enabling Compatibility mode.

Is there any way your plugin can “take the lead” with WooCommerce Google Analytics Integration and I can get these configurations setting back ?

• This reply was modified 1 year, 1 month ago by 19ash82.
• This reply was modified 1 year, 1 month ago by 19ash82.
• This reply was modified 1 year, 1 month ago by 19ash82.

Nope. Unfortunately not.

The other plugin’s tracking code simply will not listen to “Allow tracking when…”, etc.

If this plugin had millions of users I’m sure that other plugins would implement compatibility with CAOS, but unfortunately, that’s not the case ??

If that were the case, then yes, it could be possible. Because what needs to be done, is that the other plugins honors CAOS’ settings. Not the other way around, unfortunately.

Thanks for your answer.

Do you plan to integrate e-commerce events one day ?

I’m sure that would be a huge hit ??

I’ve researched it before, but it was too much maintenance. I’ll research it again. Who knows, now with GA4 it might actually be a cool thing to add.

Hello,

as this aligns with my current situation, I would like to join the discussion on this topic. Unfortunately, I didn’t understand which documentation to follow for CAOS. The docs don’t provide information on the settings required for WooCommerce Google Analytics integration. I’m also unsure whether it’s possible to use Gtag locally with the WC integration.

Currently, despite having set up CAOS, I still see a URL requesting the analytics code from https://www.googletagmanager.com/gtag/js?id=G-ML1J4XXXXX. Must CHOAS run in compatibility mode? The plugin pages seems to indicate that.
“Warning!?Please make sure that CAOS’?Basic Settings?match your Google Analytics plugin’s configuration.”
Which parameter exactly does it point to?

Since “Allow tracking…” is greyed out in compatibility mode, does the cookie banner and the Cookie Name of the cookie solution accepted and the Gtag blocked before consents?
On further inspecting the dev tools its seems that the Gtag cookie won’t be set even when the user consents. There is nothing to configure with WooCommerce Google Analytics integration. It seems once compatibility mode is active the Gtag is blocked completely or not identified at all.

• This reply was modified 8 months, 3 weeks ago by mike8040.
• This reply was modified 8 months, 3 weeks ago by mike8040.
• This reply was modified 8 months, 3 weeks ago by mike8040.

Hi Mike,

Currently, despite having set up CAOS, I still see a URL requesting the analytics code from https://www.googletagmanager.com/gtag/js?id=G-ML1J4XXXXX. Must CHOAS run in compatibility mode? The plugin pages seems to indicate that.

If WC GA Integration is installed, all you have to do in CAOS is enable its Compatibility Mode. That’ll make sure that WC GA Integration loads CAOS’ local file.

“Warning!?Please make sure that CAOS’?Basic Settings?match your Google Analytics plugin’s configuration.”
Which parameter exactly does it point to?

The Google Analytics Measurement ID. Everything else is greyed out, because CAOS can’t control it. Since Compatiblity Mode is enabled and it’s WC GA Integration that’s adding the tracking code to your pages.

I hope that explains it. If you need more help, please share your site’s URL so I can take a better look.

Hey there,

thanks a lot for your response and explanation. So to understand it correctly. I only have WC GA Integration enabled and CAOS is enabled with its Compatibility Mode and the general and ecommerce tracking should work?
Unfortunately that was not my finding. Once compatibility mode was active no tracking was available. I took care that the cookie banner was no interfering, but that did not resolve the issue. The cookie was not even set looking in the dev tools application tab. Right now I have CAOS disabled again. Because of Adult content I can’t share the URL here.

Hi again! You can send me the URL using this contact form. Then I can try and debug the issue.

Hi. Thanks for the prompt response! Just send you the details.

//Edit: Hey there, quick update. It comes down to WC GA integration is my take. They complete crashed it against the wall with version 2.0.0. I just updated to 2.0.1 and some real time data is available again, but is still not working properly. The classic site tracking data is broken. Console say:
wcgai.trackClassicPages is not a function

Some users seem to already reported that in their forum.

Changelog of their 2.0.1
Fix – Resolve Google Analytics not loading if gtag already exists on the window object.

So I’m sorry. I guess this is all not COAS related but a deep WC GA issue.

//Edit: Maybe it helps anyone. I rollback to WC GA integration 1.8.4 and classic and ecommerce tracking is working again. Also COAS does it Job well and serves the gtag locally like communicated. It was all down to broken functions with the plugin by WooCommerce.

• This reply was modified 8 months, 3 weeks ago by mike8040.
• This reply was modified 8 months, 3 weeks ago by mike8040.

Thanks for updating the post!