WooCommerce + Google Ads: the setup that reports revenue accurately
WooCommerce runs on WordPress, which means its Google Ads integration lives or dies by how the plugins and data layer are configured. The out-of-the-box connection captures the basics, but Enhanced Conversions, a clean product feed, and server-side tracking are where accurate ROAS is won. This guide covers the setup iClick applies on WooCommerce stores.
A 47-point written audit of your Google, Meta or Shopping account, back in five business days.
Get your auditBook a callWhat this integration unlocks
- Product feed sync from WooCommerce to Merchant Center for Shopping and PMax
- Purchase conversion tracking for baseline ROAS reporting
- Dynamic remarketing audiences from product-view behaviour
- Enhanced Conversions once wired through the data layer
- Server-side event pipeline that survives ad-blockers and privacy browsers
Setup steps
- 1
Connect the product feed to Merchant Center
The official Google for WooCommerce extension does not use a feed file. It syncs products to Merchant Center through Google's API, so there is no feed URL to check. Each product create or update syncs straight away through a background job, and a daily job re-syncs expiring products. If you need a traditional feed file instead, that is a separate feed plugin.
Either way, confirm GTINs, prices, and availability populate in Merchant Center. Common miss with feed-file plugins: a slow refresh schedule or a WordPress caching layer serving a stale file, so out-of-stock items keep serving. Check the live file against real inventory.
- 2
Install conversion tracking through a tag manager
Pick one tag source and stick to it. Google for WooCommerce installs its own built-in Google tag and sets up its conversion tracking automatically. If you prefer Google Tag Manager with a proper data layer, which gives you clean access to order value, transaction ID, and product data at purchase, switch the extension's tag off with the woocommerce_gla_disable_gtag_tracking filter that its documentation provides. Running both double counts every order.
On WooCommerce, the order-received page is where the purchase event should fire, and the transaction ID must be passed to enable deduplication later.
- 3
Enable Enhanced Conversions
Enhanced Conversions hashes first-party checkout data, email and phone, to recover conversions lost to privacy limits. If you use the extension's own tag, turn on its enhanced conversions setting on the extension's Settings page. If you use GTM, map the WooCommerce checkout fields into the data layer so the tag can read and hash them.
Verify in the Enhanced Conversions diagnostics that events reach a Recording state. A common WordPress failure is the email field not being present in the data layer at the moment the purchase event fires.
- 4
Add server-side tracking for durability
Client-side tracking on WordPress loses events to ad-blockers and privacy browsers. A server-side GTM container captures the purchase event server-side and forwards a clean, deduplicated conversion to Google Ads.
This takes engineering to stand up, but on any WooCommerce store where bidding drives real budget, the recovered signal usually justifies it quickly.
- 5
Add custom labels to the feed
Push custom labels for margin tier, hero-SKU status, seasonality, and discount state into the feed. These let Shopping and Performance Max bid a high-margin product differently from a loss leader, which is impossible without them.
Common issues
Fix. Usually two tags fire for the same order: Google for WooCommerce's built-in tag plus a GTM container, or a theme-level tag plus GTM. Keep one, using the woocommerce_gla_disable_gtag_tracking filter if GTM wins, and use the transaction ID for deduplication so refreshes of the order-received page do not double-count.
Fix. The checkout email is often missing from the data layer when the event fires. Confirm the field is captured before the purchase event and hashed correctly.
Fix. Commonly missing GTINs, low-resolution images, or titles over the length limit. Run a feed audit and fix at the WooCommerce product level so the correction persists through refreshes.
Fix. Often PMax counting branded search plus view-through conversions. Apply brand exclusions and reconcile against the store's own revenue as the source of truth.
Common questions
Want this checked on your own account?
A 47-point written audit of your Google, Meta, or Shopping account. Five business days, no sales call.
