WooCommerce purchase tracking, properly tested.
Every WooCommerce store is put together differently: plugins, theme, checkout type and payment gateways all change how a purchase is tracked. We look at how yours actually works, then test it with a real order.
Common plugin and tag conflicts
WooCommerce gives you many ways to send the same purchase. Problems usually start when more than one is active:
- a Google Analytics or GA4 plugin, plus GTM sending its own
purchasetag; - Google's Site Kit plugin and a separate analytics plugin both loading GA4;
- a marketing plugin that adds the Meta Pixel, plus a pixel added in GTM or the theme;
- a code snippet in
functions.phpor a child theme, forgotten after a plugin replaced it; - a GTM plugin pushing a dataLayer in one format while GTM tags expect another.
Each of these is easy to add and hard to see afterwards. The first job is a list of every source, so the purchase event has one clear owner. See WooCommerce purchases missing from GA4.
Checkout and thank-you events
On most stores, the purchase event is sent from WooCommerce's order received page, the "thank you" page shown after payment. We check:
- which plugin or tag generates the event on that page, and whether it reads the order from WooCommerce or from the page;
- whether the store uses the block-based Checkout or the classic shortcode checkout, since plugins can behave differently with each;
- that the event fires once per order, and not again when the customer reloads or revisits the page;
- earlier ecommerce events such as
add_to_cartandbegin_checkout, where they matter for your reporting.
Orders and refunds
We compare tracked purchases with WooCommerce's own order records for the same orders:
| Field | What we compare |
|---|---|
transaction_id |
The WooCommerce order number, unique per order |
value |
Order total, and whether tax and shipping are included consistently |
currency |
The order currency, including stores using a currency switcher |
items |
Product IDs or SKUs and quantities |
Refunds and cancellations reduce your WooCommerce totals but not GA4's unless a refund event is sent. If you want refunds in GA4, we check how, and whether a plugin already does it. Failed and pending orders matter too: a purchase event for an order whose payment never completed overstates revenue.
Payment redirects
Many gateways take the customer to the provider's own page and send them back afterwards. That creates two common problems:
- The customer doesn't come back. If the purchase event only fires on the thank-you page, orders from customers who close the tab after paying are never sent to GA4.
- The gateway becomes the traffic source. The return visit can be attributed to the payment provider's domain rather than the original campaign. GA4's unwanted-referrals setting addresses this.
We test the gateways you actually use, for example card, PayPal or a buy-now-pay-later provider, rather than assuming one test covers them all.
GA4, Google Ads and Meta validation
- Inventory every plugin, snippet and GTM tag that sends ecommerce or conversion data.
- Place an approved test order through each gateway in scope.
- Confirm one
purchasein GA4 DebugView with the order's ID, value and currency. - Confirm one Google Ads conversion with the same transaction ID, and one Meta
Purchase, de-duplicated if both Pixel and Conversions API are used. - Record the evidence and recheck the standard reports after processing.
For Google Ads and Meta detail, see Google Ads and Meta conversions. For duplicates, see duplicate purchase events.
Consent and caching
- Consent. The consent plugin must set Google's Consent Mode defaults before tags load, update them when the visitor chooses, and apply the same choice to Meta and other tools. See Consent Mode v2 checks.
- Page caching. WordPress caching plugins and hosting caches can serve the same HTML to every visitor. If order details are written into cached HTML, or a cached page holds an old dataLayer, events can carry the wrong values or fire for the wrong session. The order received page and the checkout should normally be excluded from page caching, and we check that they are.
- Script optimisation. Plugins that delay or combine JavaScript can stop tags firing in time, or at all. We check which scripts are delayed.
Diagnostic
WooCommerce tracking diagnostic
From £399
One store and one selected problem, such as missing or duplicated purchases. Written findings, evidence and recommended actions, with a scope for any fix.
Check WooCommerce trackingDefined tracking fix
From £495
An agreed, contained correction with test-order evidence and a handover. Quoted after the scope is defined.
About tracking fixesThe £495 Shopify offer is Shopify-only, because WooCommerce stores vary too much for a single fixed scope. Plugin development, payment gateway engineering, hosting changes and full theme work are not included. See pricing.
Introductory pricing. These are introductory prices for our current service packages. We agree the scope and price with you before work starts. Future prices may change, but an accepted quote won't change without your agreement.
FAQ
Which plugin should I use?
It depends on what you already have and who maintains it. We usually recommend fewer moving parts: one owner for each event, documented.
Do you need WordPress admin access?
For a full check, yes, through a user account you create for us, removed after the work. We never ask for your own password.
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.