Google Ads and GA4 tracking for WooCommerce
The Google side on WooCommerce is mostly about counting rather than tags. A purchase tag on a revisitable page plus a conversion action set to count every conversion produces inflated numbers that look plausible. Getting the event onto the order hook and the counting setting right fixes more than any amount of tag work.
Free30 minutesNo obligation
WooCommerce + Google · what breaks
What goes wrong on WooCommerce
- 01
The same order counted several times
The order-received page is refreshable, bookmarkable and shareable.
- 02
Different gateways returning differently
Card, PayPal and offsite redirects each land the customer somewhere different, and the untested one is where conversions go missing.
- 03
Plugin conflicts
A tracking plugin and a hand-built tag both firing a correct purchase produces two correct purchases.
- 04
Orders paid later never counted
Bank transfer and cheque sit in on-hold and complete outside any browser session.
WooCommerce + Google · the fix
What changes — WooCommerce + Google
One conversion per order
Fired from a status change, not a page view.
Refreshes and back-buttons harmless
Because the page no longer triggers anything.
Every gateway path covered
Including the ones that redirect twice.
WooCommerce + Google · architecture
How the Google destinations behave on WooCommerce
Most WooCommerce Google problems are counting and duplication rather than missing tags.
- 1
transaction_id must be the order ID
It's what stops a refreshed confirmation counting twice in GA4.
- 2
Counting set to every for ecommerce
But verify — a lot of Woo accounts inherited lead-gen defaults.
- 3
Enhanced Conversions from the order
You have the customer data server-side; don't scrape the DOM for it.
- 4
Click IDs persisted into order meta
The cleanest carrier on WooCommerce, and it survives the gateway round trip.
- 5
Check for a caching plugin
A cached confirmation page can serve one customer's values to another.
WooCommerce + Google · diagnose
Where WooCommerce tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Refresh a confirmation page and watch
The fastest reproduction of the most common WooCommerce fault.
- 02
Match platform purchases to order IDs
Repeated IDs prove duplication rather than over-attribution.
- 03
List every tracking-adjacent plugin
Then check the ones nobody mentioned.
- 04
Test each gateway's return path
They differ more than people expect.
- 05
Check whether a caching plugin is active
And whether the confirmation page is excluded from it.
WooCommerce + Google · prove
The QA evidence — WooCommerce + Google
Run on WooCommerce specifically, on a live conversion rather than in preview mode.
Source of truth
your WooCommerce order records
- Confirmation page refreshed repeatedly with no additional event.
- Every gateway return path tested with a real transaction.
- No order ID appearing twice at any destination.
- Purchase count within a few percent of WooCommerce orders for a closed week.
- A real refund issued and confirmed reversing.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
WooCommerce + Google · free audit
What we check in the free audit
- Refresh a confirmation page and watch
- Match platform purchases to order IDs
- List every tracking-adjacent plugin
- Test each gateway's return path
- Check whether a caching plugin is active
Checked against
your WooCommerce order records
Free30 minutesNo obligation
WooCommerce + Google · when not to buy
When you don't need this on WooCommerce
Worth reading before you buy anything, from us or anyone.
- If your purchase count matches your WooCommerce order count and refreshing the confirmation page fires nothing extra, you don't have the classic WooCommerce problem and probably don't need us.
- Filtering duplicates out in GA4 is not a fix — the ad platforms still received them and bidding still optimized on them — but if you genuinely only care about reporting, it's cheaper than a rebuild.
- Moving purchase to the order hook is something a competent WordPress developer can do. If you have one, hand them this page.
- Reconcile a closed week on order ID first. It costs an hour and tells you whether any of this is worth paying for.
WooCommerce + Google · what we deliver
What gets built for Google on WooCommerce
GA4 ecommerce events in the recommended shape
Correct names, transaction_id present, currency per order, an items array that agrees with the value.
Click identifiers captured and persisted
gclid, gbraid and wbraid — not just the first, because iOS traffic arrives with the others.
Enhanced Conversions from the data layer
Not from CSS selectors, which break on every redesign silently.
Conversion action settings reviewed
Counting, primary status and attribution window — free to change and more consequential than most tag work.
Written guarantee
95%+ tracking accuracy
Measured against your WooCommerce order records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
WooCommerce + Google questions, answered
Every, for ecommerce. But check it — plenty of Woo accounts inherited a lead-gen default that inflates everything.
Usually duplication from the revisitable confirmation page, or non-web orders included in your store total but not in GA4.
It can, and it shouldn't have to. You have clean customer data on the order object server-side; use that instead of DOM selectors.
It can serve one customer's confirmation values to another. Exclude the confirmation page from caching, or source the event server-side.
Free · 30 min
Get Google Ads and GA4 right on WooCommerce
WhatsAppFree30 minutesNo obligation
