Skip to main content
NS
Ecommerce21 Nov 2026·By Nazmun Sakib·5 min read

GA4 purchases not matching WooCommerce orders: a debugging checklist

If GA4 reports fewer or more purchases than your store, the cause is usually one of a handful of known problems. This checklist helps you find which one.

Every store owner eventually compares GA4 with the order list and finds two different numbers. A small gap is normal. A large or changing gap means something is wrong, and it is almost always one of a few known causes. Use WooCommerce as the source of truth, because it records every order, and work through this checklist to find where GA4 loses or invents purchases.

First, decide what you are comparing

Compare like with like before you debug anything.

  • Use the same date range and time zone in GA4 and in WooCommerce.
  • Compare completed or paid orders, not every order status. Failed, cancelled and pending orders should not count as purchases.
  • Compare orders with purchase events, then revenue. Revenue can differ because of tax, shipping, discounts and refunds even when counts match.
  • Allow for processing delay. GA4 reports can take many hours to settle.

If GA4 shows fewer purchases

The tag is missing some orders. Check these in order.

  • Is the purchase event firing at all? Use GTM Preview and GA4 DebugView to place a test order and watch the event arrive with its parameters.
  • Is it firing on the right trigger? A trigger on a thank-you page URL misses customers who never reach it.
  • Off-site payment gateways. If customers leave your site to pay and do not always return, the browser never reports the purchase. This is a common cause of undercounting.
  • Ad blockers and privacy browsers stop browser-side tags. The gap grows with technical audiences.
  • Consent. If analytics is denied by the consent banner, purchases are not collected normally, and the setup of consent mode affects what is modelled.
  • Payment gateways and referral exclusions. A gateway domain appearing as a traffic source can start a new session and hide the original source, so add the gateway to the unwanted referrals list.

If GA4 shows more purchases

The event is firing more than once or for orders that should not count.

  • Page reloads. If the thank-you page can be refreshed or revisited from an email, the event fires again. Guard it so each order is sent only once, for example by recording that it was sent.
  • Two tags sending the same event, such as a plugin and a GTM tag. GA4 does not remove duplicates unless the transaction ID matches, so keep one source.
  • Test orders and staff orders counting as real. Exclude internal traffic and mark test orders.
  • Failed or pending payments triggering the event too early.

Check the event itself

A purchase event needs the right data.

  • transaction_id, unique for each order. GA4 uses it to ignore repeated events.
  • value and currency, matching the order total as you define revenue.
  • items, with an ID, name, price and quantity for each product.

Missing or wrong values produce revenue that never matches, even if counts are right.

Refunds and cancellations

GA4 does not know about a refund unless you tell it. A store with many returns will show higher revenue in GA4 than in WooCommerce unless refund events are sent. Decide whether you want net revenue in GA4 and, if so, send a refund event for each refunded order.

Attribution is a different question

Even when purchase counts match, the credit assigned to channels can differ between GA4, your ad platforms and your store, because each uses its own attribution model and window. Do not expect channel totals from different tools to agree. Agree on one number for orders, from WooCommerce, and use each platform for what it is good at.

A fix that holds up: send from the server

Many of these problems come from relying on the browser. Sending the purchase event from the server, from the moment WooCommerce marks an order paid, avoids blockers, gateway redirects and page reloads, and makes the transaction ID reliable. Browser-side events can remain for the rest of the journey. I cover how this fits together in my guide to ecommerce tracking tools.

A quick routine

  • Place a test order and watch DebugView.
  • Compare yesterday's WooCommerce paid orders with GA4 purchases.
  • Check that every purchase has a unique transaction ID.
  • Look for a sudden change, which usually points to a recent plugin, theme or tag change.
  • Re-check after any checkout, gateway or consent change.

Need it fixed?

Tracking gaps cost money in ads and in decisions. I build and repair GA4, GTM and server-side tracking for WooCommerce stores. Describe what you see and I can tell you where the gap is likely to be.

Frequently asked questions

Why does GA4 show fewer purchases than WooCommerce?

Common causes are ad blockers and consent banners stopping the tag, customers who pay on an external gateway and never return to the thank-you page, and a purchase tag that is misconfigured or fires on the wrong page.

Why does GA4 show more purchases than my orders?

Usually the purchase event fires more than once, for example when the thank-you page is reloaded, or test orders and failed payments are being counted.

Should GA4 revenue exactly match WooCommerce?

Not exactly. Small differences are normal because of blocked tracking, refunds, taxes and shipping settings and processing delay. A large or growing gap means something is broken.

What does a GA4 purchase event need?

A transaction ID that is unique per order, a value, a currency and an items list. The transaction ID is what lets GA4 recognise duplicates.

ShareX / TwitterLinkedIn