WooCommerce orders not showing in GA4: plugin conflicts, payment redirects and the thank-you page.
- “WooCommerce orders not showing in GA4”
- “Missing purchase event in GA4 on WooCommerce”
- “GA4 purchase missing on WooCommerce”
- “WooCommerce purchase not tracked in GA4”
- “GTM4WP purchase event not firing”
- “Google Analytics for WooCommerce not tracking purchases”
- “WooCommerce thank you page purchase event missing”
- “WooCommerce GA4 purchases lower than orders”
- “WooCommerce purchase tracking stopped after plugin update”
Baris Asa, tracking consultant, London · Filed 8 November 2026 · Last checked: 8 November 2026
WooCommerce has the order and GA4 has no purchase event for it. What the missing orders share tells you why: one payment method, one thank-you page, one order status, or everything from one date. Most fixes are a single setting in the payment gateway, the page cache, or the plugin that sends the purchase, usually GTM4WP or Google Analytics for WooCommerce. The table below maps each pattern to its fix.To find the pattern, list the missing orders first. Export last week’s WooCommerce orders, then look each order number up as a Transaction ID in GA4 (Explore, Blank, Transaction ID as rows, Ecommerce purchases as values). The ones that aren’t there are your list. Each order’s screen in WooCommerce shows its payment method and, with order attribution on, its origin and device type. The full method, and the four-point check for any platform, are in GA4 purchase event not firing at all.
| Missing orders share | Likely cause | Fix |
|---|---|---|
| placed in the last two days | not processed yet | wait 48 hours, then compare |
| nothing; small, even gap | declined consent, ad blockers | expected; check consent wiring |
| no ecommerce events at all | nothing set up to send them | turn on GTM4WP “Track e-commerce” |
| one payment method; shopper never returns | gateway doesn’t redirect back | gateway auto-return or redirect setting |
| one payment method; shopper returns late | order older than GTM4WP’s window | raise “Only track orders younger than” |
| a funnel or custom thank-you page | page skips WooCommerce’s step | GTM4WP custom thank-you page setting |
| one order status | status not counted | GTM4WP purchase statuses |
| Android, arriving from social apps | GTM4WP before 2.0.6 | update the plugin |
| everything from one date | cache, update or second plugin | exclude the page; check versions; one sender |
Rather not run these checks yourself? That is the work I do: GA4 ecommerce tracking on WooCommerce.
Are the orders really missing, or just not processed yet?
- The orders are too new. Many GA4 reports take 24 to 48 hours to process. Compare a week that closed at least three days ago.
- The gap is expected. Shoppers who decline cookies or run ad blockers aren’t fully measured. A gap spread evenly across payment methods and devices, no bigger than your banner’s decline rate plus blockers, is not a fault.
- Nothing sends ecommerce events at all. No purchases ever, no add to cart, no checkout. That means no plugin is set up to send them. In GTM4WP, “Track e-commerce” is the master switch for the whole WooCommerce integration, and it is off by default.
Which plugin sends your purchase?
Start in WordPress, Plugins. Look for:
- GTM4WP (Google Tag Manager for WordPress). It writes the purchase into the dataLayer, the list of facts the page hands to Google Tag Manager (GTM). A GA4 tag in your GTM container sends it on.
- Google Analytics for WooCommerce, published by WooCommerce. It sends the purchase to GA4 itself, no GTM needed.
- Anything else that mentions Google, GA4 or tags: Site Kit, an ads plugin, a theme’s header-code box.
Then ask your developer to place one test order with Tag Assistant (Google’s tag debugger) connected. You want one purchase, sent to one G- measurement ID.
For your developer: in the Network panel, tick Preserve log and filter on collect. Count en=purchase in each request’s URL and in its Payload, since one request can carry several events. tid is the G- ID it went to. With server-side GTM the requests go to your own tagging domain, not Google’s. Searching the page source for G- is only a hint: a GA4 tag inside GTM doesn’t show there.
Two senders is the first thing I’d settle. Pick one. Which one matters less than having only one.
Do the missing orders share a payment method?
Then check how the shopper comes back. Both plugins send the purchase from the order confirmation page. Google Analytics for WooCommerce “requires a payment gateway that redirects to the thank you/order received page after payment.” GTM4WP’s FAQ says PayPal and some other gateways “do not redirect users back to your website after a successful transaction by default.”
The shopper never comes back. Pay with each method on the live site and watch where you land. The fix is the gateway’s auto-return or return URL setting, where it has one. PayPal Payments Standard is covered step by step in the platform-free note.
The shopper comes back late. GTM4WP has an experimental setting, “Only track orders younger than”, 30 minutes by default: “the maximum age of an order, or of its payment, for the purchase event to fire on the order received page.” Past it, opening the confirmation page “is treated as a revisit to a purchase already measured”, so no purchase is sent. Its settings reference says to raise it when customers reach the confirmation page long after ordering, as with slow redirecting payment methods.
Some shoppers never come back, whatever the setting: they pay and close the tab. GTM4WP’s fallback “cannot recover an order where the buyer pays through an asynchronous gateway and never returns to your site. That case needs server side tracking.” That means sending the purchase from the order itself, through Google’s Measurement Protocol or a server container, with the same transaction ID the browser would use. See Orders no browser tag can see.
If the shopper comes back and the order shows under paypal.com / referral or a card provider’s domain, the purchase arrived. The source is wrong, on file as F-205 .
Is the thank-you page WooCommerce’s own?
WooCommerce’s order confirmation page is an endpoint on the Checkout page’s URL: an extra part added to the end of that address (WooCommerce, Settings, Advanced, Page setup). Funnel plugins, page builders and some themes send the shopper to a page of their own instead. That page may skip the WooCommerce step tracking plugins listen for. GTM4WP’s FAQ names this cause.
How to tell: after a test order, if the address bar isn’t your Checkout page’s address with the confirmation endpoint on the end, the page is custom.
GTM4WP offers two workarounds, both de-duplicated so an order isn’t counted twice:
- Custom order received (thank-you) page (beta). Names the page where the purchase should fire when a theme or plugin replaces the standard one.
- Reliable purchase tracking (experimental, off by default). When the shopper lands on a heavily customised thank-you page, or on the order-pay page, it sends the purchase on the next page they view in the same browser session.
Google Analytics for WooCommerce documents purchases on the order confirmation page only. Its documentation doesn’t cover custom thank-you pages, so send one test order through the funnel before trusting it.
Is the order in a status the plugin counts?
This one is GTM4WP. Its setting “Order statuses that trigger the purchase event” (beta) defaults to Processing, On hold and Completed. The purchase is sent when an order first reaches one of these, “which is at order placement.” Its advice: “Leave Failed, Cancelled and Pending payment unchecked so that unpaid orders are not reported as sales.” An empty list counts every order except Failed ones.
WooCommerce defines Pending payment as “the order has been received, but no payment has been made.” An order still Pending payment when the shopper lands sends no purchase from that page. Open a missing order in WooCommerce, Orders: the order notes panel records status changes and payment results, so you can see what the status was when the shopper landed.
The opposite case: a bank transfer (BACS) order sits On hold, “awaiting payment confirmation” in WooCommerce’s words. With the defaults, GTM4WP counts it at checkout, paid or not.
Is a page cache serving the thank-you page?
A full page cache saves a copy of a page and serves it to the next visitors. On a thank-you page, that copy holds the purchase of whichever order filled the cache. GA4 collects only the first event with a given transaction ID. So the copies served after it are dropped as repeats, and the real orders behind them are never sent. It is easy to miss: the purchase tag fires every time, so Tag Assistant looks healthy.
WooCommerce asks you to keep three pages out of the cache: Cart, My Account and Checkout, because they “display information specific to the current customer and their cart.” The built-in confirmation page sits on the Checkout URL, so that exclusion covers it, whichever plugin you use. A custom thank-you page has its own URL and needs its own exclusion. Since 2.0.6, GTM4WP tells page-cache plugins not to cache a theme or page builder thank-you page that carries the purchase, and 2.1.0 fixed further page-caching issues in purchase tracking. Run the current version.
The test takes two orders. Place one, then a second from a different browser. On the second thank-you page, read the transaction ID in the purchase: in GTM Preview’s Data Layer tab, or in the purchase hit in the Network panel. If it is the first order’s number, the page is cached.
GTM4WP’s “Cache-safe data layer” option solves a different problem: it keeps visitor-specific values out of the cached copy. For a cached purchase, exclude the page and update GTM4WP to the current version.
Did it stop after a plugin update?
Purchases missing from one date, across every payment method, usually line up with a change that day. Check the plugin update dates and the changelogs of anything that touches the checkout.
Hand these to whoever set up your GTM:
- 2.0 rebuilt GA4 ecommerce tracking for WooCommerce. Check your GTM tags and variables against GTM4WP’s current container template. Its GA4 setup page says anyone who imported the template before August 2026 should import the current file.
- 2.1.0 removed
orderData.customer.billing.emailhash, deprecated since 1.20. GTM variables still reading it come back empty: switch them toorderData.customer.billing.email_hash. - 2.1.0 fixed further page-caching issues in WooCommerce purchase tracking (see the cache section above).
- 2.0.6 fixed in-app browsers. Before it, shoppers in the in-app browser of an Android app such as Facebook or Instagram got no WooCommerce data layer, so “their purchase and other e-commerce events were missing.”
- After a reinstall or settings reset, check “Track e-commerce” is back on.
If the purchase fires but finds the dataLayer empty, that is timing, on file as F-103 and covered in GTM tag fires before the dataLayer is ready.
Are two tracking plugins sending the purchase?
WooCommerce’s documentation for its extension says “multiple tracking code instances on the same page can cause issues.” GTM4WP carries a plugin conflict notice that names Google Analytics for WooCommerce.
Two plugins lose purchases in two ways:
- Different properties. Each plugin sends to its own
G-measurement ID. The purchase lands in a property nobody reads. - A replaced dataLayer. A script that runs
window.dataLayer = []after GTM loads cuts GTM off: GTM keeps listening to the list it started with, so a purchase pushed into the new one is never seen. Google’s rule: never overwrite or re-assign thewindow.dataLayervariable.
If both send to the same property with the order number as transaction ID, GA4 keeps the first and drops the second. If one copy carries a different ID or none, you get doubles instead: F-101 , covered in GA4 purchase event fires twice.
Keep one sender for the purchase and switch the other’s purchase tracking off.
Is consent holding the purchase back?
Consent only explains shoppers who decline. For them, advanced Consent Mode lets GA4 model users and key-event rates once the property clears Google’s thresholds. Their individual orders stay in WooCommerce.
What passes the shopper’s answer on depends on the plugin. Google Analytics for WooCommerce has no banner of its own; it reads the WP Consent API, so your consent plugin has to update the consent state when the shopper accepts. With GTM4WP, the GTM container decides: a consent default set before any tag sends data, and an update from your banner’s consent template when the shopper chooses. Shoppers who accepted and still go missing point to a wiring fault, on file as F-201 . The test is in How to check Consent Mode v2 is working.
How do I test a WooCommerce purchase end to end?
- Log out of WordPress and use a private window, so the test matches a real shopper. Accept the banner.
- Open Tag Assistant and connect it to the live site.
- Place a real order with the payment method the missing orders share.
- Note the address you land on, how long the payment took, and the order status in WooCommerce at that moment.
- In Tag Assistant, find the purchase and check the transaction ID is this order’s number.
- In GA4 DebugView, confirm
purchasearrived, lowercase. DebugView only shows sessions connected through Tag Assistant or with debug mode on.
With GTM4WP’s defaults, reloading the thank-you page won’t send the purchase again: it marks each order it has tracked, unless “Do not flag orders as being tracked” is on. Use a new order for each test.
How do I know it’s fixed?
- A test order through each payment method shows one
purchasein DebugView with its own order number. - Rerun the order comparison for the first closed week after the fix. The missing orders share no gateway, status, device or page.
- The share still missing sits within your banner’s decline rate plus ad blockers.
GA4 can’t rebuild purchases it never received. For the weeks before the fix, WooCommerce’s order data is the record.
Common questions
Why are WooCommerce orders not showing in GA4?
Find what the missing orders share. One payment method: the gateway doesn’t send the shopper back to the order confirmation page, or sends them back late. A funnel or custom thank-you page: that page skips the WooCommerce step the tracking plugin listens for. One order status: the plugin doesn’t count it. Everything from one date: a page cache, a plugin update or a second tracking plugin. Orders less than 48 hours old may simply not be processed yet.
Why are PayPal orders missing from GA4 on WooCommerce?
Either the shopper never comes back from PayPal, or comes back too late. Turn on the gateway’s auto-return, where it has one. If you use GTM4WP and shoppers do return, check its “Only track orders younger than” setting, 30 minutes by default and measured from the order or its payment: past it, the confirmation page is treated as a revisit and sends no purchase. Shoppers who never return can only be counted server-side.
Two tracking plugins on WooCommerce: why are purchases missing?
Two plugins lose purchases when each sends to a different GA4 property, so the purchase lands where nobody looks, or when one replaces the dataLayer that Google Tag Manager reads. If both send to the same property with the order number as transaction ID, GA4 keeps the first and drops the second; with different or missing IDs you get doubles instead. Keep one plugin sending the purchase.
My page cache plugin excludes the checkout. Can the thank-you page still be cached?
Yes, if the thank-you page lives somewhere else. WooCommerce asks you to exclude the Cart, My Account and Checkout pages from caching. Its own confirmation page sits on the Checkout URL, so that exclusion covers it. A thank-you page built by a theme, page builder or funnel plugin has its own URL and needs its own exclusion.
Reloading the thank-you page doesn’t send the purchase again. Is that broken?
No. By default GTM4WP marks each order it has tracked, so reloading the confirmation page doesn’t send a second purchase. Its “Do not flag orders as being tracked” setting, off by default, removes that protection. Place a new order for each test.
Should I test WooCommerce purchase tracking while logged in?
No. Google Analytics for WooCommerce doesn’t track pageviews for logged-in admin users, and its documentation tells you to log out before testing. Test as a guest in a private window, with the cookie banner accepted, so the test matches a real shopper.
I have no partnership, affiliate or commission arrangement with any plugin on this page.
Sources
Read on 8 November 2026:
- GTM4WP, WooCommerce settings reference (Track e-commerce, the master switch, off by default; Only track orders younger than, experimental, 30 minutes by default, the maximum age of an order or its payment; Reliable purchase tracking, experimental, off by default, covers customised thank-you and order-pay pages, cannot recover a buyer who never returns from an asynchronous gateway; Custom order received page, beta; Order statuses that trigger the purchase event, beta, Processing, On hold and Completed at order placement; orders marked as tracked so a reload sends no second purchase; Do not flag orders as being tracked, off by default, removes that protection)
- GTM4WP, plugin page, FAQ and changelog (version 2.1.1: gateways that don’t redirect back by default; plugins that alter the order received page without WooCommerce’s
is_order_received_pagefunction andwoocommerce_thankyouaction; workarounds de-duplicated; Cache-safe data layer for visitor-specific values; 2.0 GA4 ecommerce rework; 2.0.6 thank-you pages kept out of page caches, Android in-app browser fix, conflict notice naming Google Analytics for WooCommerce; 2.1.0emailhashremoved, deprecated since 1.20, and further page-caching fixes; an empty purchase status list counts every order except failed ones) and GA4 for WooCommerce (import the current container template if yours predates August 2026) - WooCommerce, Google Analytics for WooCommerce (requires a gateway that redirects to the order received page; multiple tracking code instances can cause issues; pageviews not tracked for logged-in admins; WP Consent API)
- WooCommerce, Configuring caching plugins (exclude Cart, My Account and Checkout), Order statuses (Pending payment, On hold and BACS), Advanced settings (Checkout endpoints; Order received), View, edit or add an order (system notes for status changes and payment results) and Order attribution tracking (origin and device type on the order screen)
- Google for Developers, Validate your ecommerce setup (only the first event with a given transaction ID is collected), The data layer (never overwrite or re-assign
window.dataLayer) and Set up consent mode on websites (consent default before any measurement commands; consent mode templates in Tag Manager update consent when the user interacts with the banner) - Google Analytics Help, Behavioral modeling for consent mode (estimates user and key-event metrics; 1,000 events a day with analytics_storage denied for 7 days and 1,000 daily consenting users on 7 of the previous 28 days) and Confirm that you’re collecting data (many reports and explorations take 24 to 48 hours to process)