WooCommerce purchases missing from GA4?
Most WooCommerce setups send the Google Analytics 4 (GA4) purchase from the order-received (thank-you) page, so anything that stops a customer reaching or loading that page loses the purchase. Check the payment gateway's return, the plugin that sends the event, script optimisation and caching, and whether two integrations are fighting. A test order per payment method usually shows which.
Symptom
WooCommerce shows the orders. GA4 shows fewer purchases, or none from one payment method, or purchases with the wrong value. Sometimes it began after a plugin update, a new payment gateway, a switch to the block-based checkout, or a performance plugin.
WooCommerce setups vary a lot by theme, plugins, checkout type and payment integrations, so don't apply Shopify instructions here.
Possible causes
- Cause A: the thank-you page isn't reached. Some off-site payment methods return the customer to your site, but not every customer waits for the redirect. If the purchase only fires on the thank-you page, those orders are lost.
- Cause B: plugin settings. The GA4 or Google Tag Manager (GTM) plugin is set up with the wrong ID, has purchase tracking turned off, or doesn't support the checkout type you now use.
- Cause C: duplicate or conflicting integrations. Site Kit, an analytics plugin, a GTM plugin and the Google for WooCommerce extension can each add Google tags. One may send purchases, another may not, or both may.
- Cause D: script optimisation and caching. A performance plugin delays JavaScript until the user interacts, combines scripts, or caches the order-received page. The tag may never run, or run with stale data.
- Cause E: consent. A consent plugin blocks the tags until consent, and the thank-you page loads before the choice is applied.
- Cause F: order ID problems. Reloading the thank-you page sends the purchase again, or the transaction ID doesn't match the WooCommerce order number, which makes reconciliation impossible.
How to check
- List the integrations. In Plugins, note everything that mentions Google, Analytics, Tag Manager, pixel or consent, and the settings page of each. Search the theme's header for hard-coded tags too.
- Place one test order per payment method. Card, PayPal or other off-site gateway, and a manual method such as bank transfer if you offer it. Keep DevTools open with "Preserve log", filtered on
collect. Look foren=purchase. - Read the thank-you page. The order-received URL usually looks like
/checkout/order-received/10452/?key=wc_order_…. In the console, typedataLayerand check for a purchase object with the right order ID and value. - Reload the thank-you page. If a second purchase request is sent, you have cause F.
- Check optimisation and caching. In your performance plugin, look for "delay JavaScript" or similar, and check that the cart, checkout and order-received pages are excluded from page caching.
- Compare order lists. Export a week of WooCommerce orders and the GA4 transaction IDs for the same dates. Group the missing orders by payment method.
Illustrative dataLayer push on the thank-you page, with invented values:
dataLayer.push({
event: 'purchase',
ecommerce: {
transaction_id: '10452',
value: 64.00,
tax: 12.80,
shipping: 4.95,
currency: 'GBP',
items: [{ item_id: 'SKU-TEA-01', item_name: 'Loose leaf tea', price: 32.00, quantity: 2 }]
}
});
What the result means
- Missing only for one gateway: cause A. Check the gateway's return settings and whether the customer is sent back automatically.
- No purchase in any test order: cause B, D or E.
- Two purchase requests, or two GA4 IDs: cause C or F. See duplicate purchase events.
- Purchase appears but with the wrong value: check what the plugin puts in
valuecompared with your WooCommerce report. See GA4 revenue mismatch.
False positive. Some integrations send the purchase from the server when the order is created, not from the browser. In that case you won't see a browser purchase request, yet GA4 still receives the order. Check the plugin documentation and GA4 itself before deciding the event is missing.
How to fix it
- Keep one integration responsible for GA4 ecommerce events. Turn off the overlapping features in the others.
- If an off-site gateway loses orders, consider sending the purchase from the server when payment is confirmed, rather than relying on the thank-you page. That needs careful design to avoid sending it twice.
- Exclude checkout and order-received pages from page caching, and exclude your tag scripts from delayed or combined JavaScript.
- Guard against reloads, so a purchase is sent once per order.
- Use the WooCommerce order number as the transaction ID consistently.
- Re-test every payment method after each change.
What not to do
- Don't install another analytics plugin to "fill the gap". It usually creates duplicates.
- Don't copy a Shopify custom pixel guide. WooCommerce has no customer events sandbox.
- Don't update a payment or performance plugin on a busy day without a test order afterwards.
When to request help
Our WooCommerce tracking service tests checkout and thank-you events, payment redirects, plugin conflicts, consent and caching, then validates GA4, Google Ads and Meta.
Related guides:
- Why are purchase events counted twice?
- Why doesn't GA4 revenue match your store?
- GA4 not tracking? Start with these checks.
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.
Sources and updated date
- WooCommerce documentation: Google Analytics for WooCommerce
- WooCommerce documentation: Google for WooCommerce
- Google for Developers: Measure ecommerce
- Google Analytics Help: Minimize duplicate key events with transaction IDs
- Google Tag Manager Help: Preview and debug containers
Last checked against official documentation: 18 November 2026.