Hi there,
Thanks for taking the time to share your experience — and glad to hear the Merchant Center feed sync is working well for you!
Regarding the conversion tracking conflict with GTM4WP: this happens because both plugins are trying to handle the same tracking events (like purchase conversions and e-commerce data layer pushes) on the same pages. When two plugins inject overlapping tracking scripts, they can interfere with each other — duplicate events, blocked scripts, or one overriding the other.
Google for WooCommerce is designed as a single, integrated solution for Google services — syncing your product feed to Google Merchant Center, running Google Ads campaigns, and measuring their performance with its built-in Google tag and conversion tracking — all managed directly from your WooCommerce dashboard. As a result, it includes its own measurement layer rather than relying on a separate Tag Manager setup. The plugin is built for a typical WooCommerce user looking to improve sales in their store using marketing options from Google services. Advanced users can always find ways to turn off certain functionality via custom code.
That said, the long-term vision for Google for WooCommerce is to be the single plugin for all Google integrations on the WooCommerce platform — so it wouldn’t be surprising to see its capabilities expand further over time.
Hope that helps clarify things!
Thank you for your explanation. I completely understand the philosophy behind having a single plugin for Google services, and I agree that it is suitable for many WooCommerce users.
However, I believe there is still an important usability issue for stores that already have a complete Google Tag Manager implementation.
In my case, both “Improve conversion accuracy (Enhanced Conversions)” and “Send Enhanced Conversions data to Google Ads” are disabled. Despite this, the plugin still creates Google Ads conversion actions and continues to inject Google Ads measurement/tracking code and purchase-related events automatically.
This makes it very difficult to understand which component is responsible for sending conversion data:
- Google Tag Manager
- Google for WooCommerce
- or both
For users who already use GTM as the single source of truth for Google Ads and GA4 tracking, this creates unnecessary complexity and can lead to conflicts during debugging.
My suggestion is to add a dedicated “Feed Only” mode that:
- Syncs products with Google Merchant Center.
- Does not create Google Ads conversion actions.
- Does not inject any Google Ads or Google Tag measurement code.
- Does not send purchase or remarketing events.
- Leaves all tracking entirely to Google Tag Manager.
This would make the plugin much more flexible for agencies and advanced users, while keeping the current all-in-one experience for users who prefer automatic setup.
During troubleshooting with Google Tag Assistant and GTM Preview, it is not always obvious which events originate from Google Tag Manager and which originate from Google for WooCommerce. A clear option to completely disable the plugin’s measurement layer would make debugging significantly easier.
Hey there,
Thanks for the detailed follow-up — your points about the debugging difficulty when multiple tracking sources are active are well taken.
To clarify how the plugin’s tracking layer works: the Enhanced Conversions toggles control whether hashed first-party customer data (name, email, address) is sent alongside conversion events to improve attribution accuracy. Disabling those settings stops that additional data from being sent, but it doesn’t disable the underlying Google tag or the conversion events themselves. Those are part of the plugin’s core measurement layer, which powers the campaign analytics dashboard inside WooCommerce and feeds performance data back to Google Ads for campaign optimization.
Google for WooCommerce is built to handle the full integration loop — product feed, campaign management, and conversion measurement — as a single connected system. The tracking isn’t a separate, optional add-on; it’s what connects your product feed to campaign performance reporting. That’s the reason the plugin manages its own Google tag rather than deferring to an external Tag Manager setup.
For stores that already manage all Google tracking through GTM, the recommended approach is to keep using your current GTM implementation for tracking and use custom code to disable any tracking that Google for WooCommerce adds. There are documented workarounds using custom code in the forums.
I’ll note your “Feed Only” mode suggestion as a feature request, though we can’t make any promises on timing given the current roadmap priorities. We appreciate the detailed feedback — it helps the team understand how agencies and advanced users work with the plugin.
Hey @virdislucas ,
Thank you for your detailed feedback.
The plugin has the woocommerce_gla_disable_gtag_tracking filter that can be used to disable Google Ads tracking.
Here’s a snippet for that:
add_filter( 'woocommerce_gla_disable_gtag_tracking', '__return_true' );
If you are not sure how to install snippets like this, I propose that you use a plugin such as Code Snippets.
Can you please give this a try and let me know if the double tracking issue is resolved?