WooCommerce order placed, but no purchase in GA4?

Pick a test environment and an agreed test method. Note the page, time, expected G- measurement ID and whether the visitor accepted Analytics cookies. Use a test order reference without customer details. An administrator session can behave differently from a customer session.

List how GA4 was added: Google Analytics for WooCommerce, another plugin, GTM or custom code. Check the documentation for that exact setup. Having a measurement ID on the homepage does not tell you which integration sends purchases.

For the free Google Analytics for WooCommerce extension, purchase tracking depends on the customer returning to the thank-you/order-received page. That is a condition of this extension, not a rule for every server-side integration. Keep the distinction when comparing payment methods.

With permission, walk through the agreed sandbox flow. Record whether the customer reaches the store confirmation page after leaving the payment provider. Stop if completing the flow would create a real charge, order email or fulfilment task you have not agreed to handle.

Compare the actual destination with the page where your integration expects to send purchase. Do not fire purchase merely because someone viewed checkout. A public check of a homepage cannot observe a private order confirmation.

Use Tag Assistant on the same page and inspect the action. If you inspect Network, a request is evidence of a send attempt; its presence alone does not confirm receipt. Compare the destination with the intended web stream.

Enable debug mode for your test device and look for purchase in that property’s DebugView. Keep the consent choice with the result. An empty DebugView can also reflect privacy controls, denied consent or a device that is not in debug mode. Do not disable a consent requirement to make the test pass.

Inspect transaction_id, value, currency and items for the same test event. For example, a numeric value without its intended currency is not enough to interpret a revenue result. Use the store’s actual currency rather than copying an example configuration.

If the purchase appears twice, investigate which integrations sent it. Check that the transaction identifier refers to the same order, and review the integration’s duplicate handling. Adding another tag can make the discrepancy harder to diagnose.

Save the test time, page, integration, cookie choice, expected destination and the first point where the evidence stops. Keep customer information and payment tokens out of the note. Many standard GA4 reports need 24–48 hours to process data; a missing report row is a different finding from a missing event in a correctly configured debug session.

TrackCanary can inspect visible public-page tracking and WooCommerce hints. It does not enter your payment flow, read private orders or establish that GA4 received purchase. Use the public checker for the page evidence and the account-side steps above for the receiving side.