Shopify purchases not showing in GA4?
If Shopify records orders but GA4 shows few or no purchases, check four things: whether anything sends a purchase from checkout at all, whether consent stops it, whether the event carries a transaction ID, value and currency, and whether the missing orders could ever have been tracked in a browser. A test order and an order-by-order comparison will show which it is.
Symptom
Shopify shows, say, 120 orders for last week. GA4 shows 70 purchases, or none, or the right number with zero revenue. Sometimes it started on a specific date: after a theme change, an app install, or the move to Shopify's upgraded Thank you and Order status pages.
Possible causes
- Cause A: no checkout route. Nothing sends the purchase from checkout. GTM in the theme doesn't run there, and no app pixel or custom pixel handles
checkout_completed. See Shopify GTM in the theme. - Cause B: legacy scripts stopped. Purchase code lived in the old order status page's additional scripts and stopped when the page was upgraded. Shopify's help gives 26 August 2026 as the upgrade deadline for non-Plus stores.
- Cause C: consent. The pixel's privacy settings or your banner stop the event for visitors who haven't consented. Some missing purchases are then expected.
- Cause D: missing or malformed parameters. The event fires, but without
currencyGA4 can't compute revenue accurately, and without a stabletransaction_idyou can't match or deduplicate orders. - Cause E: wrong destination. The app or pixel sends to a different GA4 property from the one you read.
- Cause F: orders that never pass through online checkout. Point-of-sale orders, draft orders created by staff and some subscription renewals have no browser checkout, so a browser pixel can't see them.
How to check
- Map the route. In Settings, Customer events, list which app or custom pixel is meant to send the purchase, and to which GA4 ID.
- Place a test order. Clean browser, cookies accepted, DevTools open with "Preserve log" ticked and the Network tab filtered on
collect. Look for a request withen=purchaseand your GA4 ID. Check that it carries a transaction ID, a value and a currency (in the request, fields such asep.transaction_id,epn.valueandcu). - Repeat with consent declined. Note whether the purchase is sent, and how. This tells you how much under-reporting your consent setup will produce by design.
- Find the order in GA4. In DebugView or Realtime first, then the next day in an Exploration with the Transaction ID dimension. Compare value and currency with the Shopify order.
- Compare order lists. Export a week of orders from Shopify. In GA4, export transaction IDs for the same dates, in the same time zone. List the orders missing from GA4.
- Look for a pattern in the missing orders. Sales channel, payment method, device, country, post-purchase upsell, or a date when the gap started.
Illustrative comparison, with invented figures:
| Week | Shopify online orders | GA4 purchases | Missing | Pattern |
|---|---|---|---|---|
| Before change | 118 | 101 | 17 | Spread across days and devices |
| After change | 124 | 0 | 124 | All orders, from the upgrade date |
The first row looks like consent and browser loss. The second looks like a broken route.
What the result means
- No purchase request in the test order: cause A or B.
- Request sent only with consent: cause C. Expected to some degree. The size of the gap is a business decision, not only a bug.
- Request sent but revenue is zero or IDs don't match Shopify: cause D. Check whether the transaction ID uses the order ID or the order name (such as
#1001), and use one consistently. - Request sent to another ID: cause E.
- Only certain channels missing: cause F, or a pattern worth investigating.
False positive. A gap between Shopify orders and GA4 purchases is not by itself a fault. Consent, ad blockers and offline orders all create a gap in a correct setup. The question is whether the gap is explained. Note also that Shopify's documentation says checkout_completed fires on the first upsell offer page when a post-purchase upsell is shown, not on the Thank you page, so a pixel that waits for the Thank you page can miss those orders.
How to fix it
- If there is no route, add one: the Google and YouTube app connected to the right property, or a custom pixel subscribed to
checkout_completed. One route per destination. - Send
transaction_id,value,currencyanditemsevery time, mapped from the checkout data, and document whatvalueincludes. - Align pixel privacy settings with your consent banner and test both states.
- Remove legacy additional scripts once the new route is confirmed.
- Validate with a fresh test order, then compare a full week of orders.
What not to do
- Don't add a second purchase route because the first "might be missing some". You will create duplicate purchase events.
- Don't compare GA4 and Shopify revenue without matching dates, time zones and order types first. See GA4 revenue mismatch.
- Don't test with an ad blocker running and conclude the tracking is broken.
When to request help
The £495 Shopify Purchase Tracking Fix covers one store and one agreed GA4 purchase path: review, correction where feasible within scope, a validated test order with transaction ID, value and currency checked, consent handling for that path, and a before and after evidence summary. See Shopify tracking and pricing.
Related guides:
- Shopify GTM is in the theme. Is checkout covered?
- Why doesn't GA4 revenue match your store?
- Why are purchase events counted twice?
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.
Sources and updated date
- Shopify Developer docs: checkout_completed
- Shopify Developer docs: Customer Privacy API
- Shopify Help Center: Upgrading the Thank you and Order status pages
- Google for Developers: Measure ecommerce
- Google Analytics Help: Currency reference
- Google Analytics Help: Monitor events in DebugView
Last checked against official documentation: 18 November 2026.