TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-033

SYMPTOM FILE SYM-033 FILED 07 NOV 2026 · REVISED 08 NOV 2026

GA4 purchase event not firing at all: where the order gets lost.

ALSO FILED AS
  • “GA4 purchase event not firing”
  • “GA4 purchase event not showing”
  • “GA4 not tracking purchases”
  • “GA4 shows no purchases but the shop has orders”
  • “missing purchase event in GA4”
  • “purchase tag fires in GTM preview but not in GA4”
  • “PayPal orders missing in GA4”
  • “Shopify GA4 purchase stopped after thank you page upgrade”
  • “Shopify custom pixel purchase not firing”
  • “GA4 purchases lower than orders”

Baris Asa, tracking consultant, London · Filed 7 November 2026 · Last checked: 7 November 2026

When the shop takes orders and GA4 records no purchase for them, the order was lost at one of four points: the shopper never reached the thank-you page, the purchase tag never fired there, consent stopped it, or GA4 dropped it. The usual culprits, in that order: PayPal or another off-site payment not sending the shopper back; a trigger on a thank-you URL that changed, or a Shopify page upgrade that removed the old script; a tag waiting for consent it never gets; the wrong G- measurement ID or an active data filter.

No access to Google Tag Manager (GTM)? Start with the order comparison below. It tells you which of the four it is before anyone opens a tool.

This note is about purchases that never arrive. If the purchase arrives with no revenue or no products, see GA4 purchase events missing items or value. If it arrives twice, see GA4 purchase event fires twice.

Every order missing, or some orders?

Answer this first.

  • No purchases at all, from a set date. Something changed that day: a new theme or checkout, a Shopify page upgrade, a plugin update, a GTM version, a new banner. Start at the tag.
  • Some orders missing, always the same kind. One payment method, one country, one device. Start at the thank-you page.
  • Some orders missing, spread evenly. Usually consent or ad blockers. Start at consent.

Compare a week of orders with GA4

No GTM access needed. Use a laptop and a closed week, at least three days ago.

  1. Export that week’s orders from the shop’s admin, with order number, payment method, country and device if the shop records it.
  2. In GA4, open Explore (also called Explorations) and pick Blank. Set the date range to the same week. Click + next to Dimensions, add Transaction ID, and drag it to Rows. Click + next to Metrics, add Ecommerce purchases, and drag it to Values. Export it.
  3. Mark each order number that is in the shop and not in GA4.
  4. Look at what the missing orders share.

Read it like this:

  • Nothing in GA4 for the whole week. A setup break: the tag, the trigger or the destination.
  • Missing orders share a payment method. The shopper isn’t coming back from that provider.
  • Missing orders share nothing. Compare the share missing with your banner’s decline rate. Your consent tool’s dashboard usually shows the share of visitors who decline. Ad blockers add a loss of their own on top. A gap far above both points at consent wiring.
  • A warning at the top of the exploration says data is withheld. That is thresholding: GA4 hiding rows, not losing events. It can make this check undercount. Read R-502 before you count.

Found a pattern? The rest of this note is for whoever runs GTM and the site. If nobody does, tracing and fixing it is my work.

Where it stopsWhat you seeFirst check
Thank-you page never loadsone payment method missingthe gateway’s return to the shop
Tag never firesnone from a set dateGTM Preview on a test order
Consent blocks iteven gap, all routesTag Assistant Consent tab
GA4 drops ittag fires, GA4 emptymeasurement ID, event name, filters
Where the purchase stops · what you see · the first check · worked example, illustrative, not a client account

Does the shopper reach the thank-you page? (PayPal, WooCommerce, Shopify)

Most purchase tags fire on the order confirmation page. No page, no tag. The order still exists, because the payment provider tells the shop directly. The browser just never comes back to say so.

  • PayPal Payments Standard. The shopper pays on PayPal’s page. With Auto Return off, they see a button to go back to the shop. Anyone who closes the tab first is never measured. Turn Auto Return on and set the return URL to your order confirmation page. The setting is in the PayPal account under Account Settings, Website payments, Website preferences.
  • Other PayPal integrations and other off-site gateways. Newer PayPal checkouts, hosted card pages, buy now pay later and open banking set the return in the integration, not in that account setting. Pay with each one and watch where you land. If it isn’t your confirmation page, the gateway plugin’s return or redirect setting is the fix.
  • WooCommerce. A theme, page builder or funnel plugin that replaces the thank-you page can stop the tracking plugin sending the purchase. The WooCommerce checks, plugin by plugin, are in WooCommerce orders not showing in GA4.
  • Shopify upsell pages. Shopify’s checkout_completed event fires once per checkout, usually on the thank-you page, but on the first upsell offer page when there is one, and not again after. If that page fails to load, it doesn’t fire at all. A tag that only watches the thank-you page misses every upsell order.

If the shopper comes back but the order sits under paypal.com / referral, the purchase arrived. The source is the fault, on file as F-205 .

Does the GA4 purchase tag fire in GTM?

Who checks this: whoever manages your GTM container. Open GTM Preview (Tag Assistant, Google’s tag debugger), place a test order, and click the message where the purchase should happen. Read Tags Fired and Tags Not Fired.

  • Shopify purchase code that lived in Additional scripts. Shopify says upgrading the Thank you and Order status pages replaces existing customisations on them, and Additional scripts became view-only on 28 August 2025. Non-Plus stores had until 26 August 2026 to upgrade. A purchase tag that lived there stopped on the day of the upgrade. Rebuild it as a pixel subscribed to checkout_completed (Settings, Customer events).
  • A Shopify custom pixel that isn’t connected. Shopify lists it under Disconnected pixels. It tracks nothing until someone clicks Connect.
  • The trigger matches a page that moved. A Page View trigger on “Page URL contains /thank-you” stops matching when a new checkout changes the URL. Fire the tag on a Custom Event trigger named purchase, matched to the site’s push.
  • The event name doesn’t match. The trigger listens for purchase; the site pushes Purchase or order_complete. Names must match exactly, case included.
  • The dataLayer was replaced. Code that runs window.dataLayer = [] after GTM loads cuts GTM off. Google’s rule: “Never overwrite or re-assign the window.dataLayer variable.”
  • Preview fires, live doesn’t. Preview runs your workspace. Visitors only get changes after someone clicks Submit and publishes. Check the live version has the tag.
  • The tag needs consent it never gets. In the tag’s Advanced Settings, Consent Settings, “Require additional consent for tag to fire” means it fires only when every listed type is granted. The Consent Overview (turn it on in Container Settings) shows which tags carry it.

The tag fires but sometimes with nothing in it? That is timing, on file as F-103 , covered in GTM tag fires before the dataLayer is ready. Purchase arriving but earlier funnel steps missing is F-301 .

Consent Mode decides what a declined shopper sends. Set up as advanced, it lets GA4 recover part of the declined purchases: tags load at once, send cookieless measurements when the shopper declines, and GA4 can model those users back into reports. That needs volume. Google’s thresholds are at least 1,000 events a day with analytics consent denied for 7 days, and at least 1,000 consenting users a day on 7 of the previous 28 days, and meeting them doesn’t guarantee modelling. Set up as basic, tags wait for the answer, and a decline sends nothing at all.

The order comparison above reads raw collected events, so modelled purchases won’t appear in it.

On Shopify, the banner settings apply as well: custom pixels run only when the visitor has given the permissions set in the pixel’s configuration.

Some missing purchases are the setup working as configured. The fault is a gap well above declines plus blockers, or shoppers who accepted going missing. That is a banner wired to the tags wrongly, on file as F-201 . The test is in How to check Consent Mode v2 is working.

Accept the banner when you test. DebugView shows nothing without analytics consent.

Does GA4 receive the purchase but drop it?

The tag fires in Preview and GA4 still shows nothing. Check the destination.

  • The wrong measurement ID. The tag sends to a test property, an old property or another stream. Compare the G- ID on the tag with Admin, Data streams.
  • The wrong event name. GA4 event names are case sensitive. Purchase lands as a separate custom event, not as a purchase, and the ecommerce reports stay empty. Look for it in Reports, Engagement, Events.
  • A data filter. An active internal traffic filter excludes your office IP; a developer traffic filter excludes debug-mode activity. Filtered data is never processed and can’t be recovered. Test orders from the office can vanish this way: F-602 working as designed. Check Admin, Data filters before blaming the tag.
  • Server-side GTM. The purchase reaches the server container but nothing forwards it. Open the server container’s Preview, find the incoming purchase request, and check a GA4 tag fired on it and sent an outgoing request.
  • Too soon. Reports can take 24 to 48 hours. Realtime covers the last 30 minutes. DebugView streams events as they arrive.

Data streams, Data filters and the Events report all live in the GA4 property, not in the tag. When nobody on your side owns the property, those are the first three screens I open as a GA4 consultant.

Orders no browser tag can see

Some orders never pass a checkout page: subscription renewals charged automatically, in-store and phone sales. No browser tag will send them. If GA4 should hold them, Google’s Measurement Protocol sends events from a server. Google’s line on it: it is meant “to augment automatic collection through gtag, Tag Manager, and Google Analytics for Firebase, not to replace it”. If GA4 shouldn’t hold them, leave them out of the comparison.

How do I test the purchase end to end?

  1. Open Tag Assistant, connect it to the live site, and accept the banner.
  2. Place a real order, paid the way the missing orders were paid. Use a new order each time: GA4 collects only the first purchase with a given transaction ID.
  3. In Tag Assistant, find the purchase message and confirm the GA4 tag fired on it.
  4. In GA4 DebugView, confirm purchase arrived, lowercase, with a transaction ID.
  5. Repeat for each payment method the comparison flagged.

How do I know it’s fixed?

  • In DebugView, a test order through each payment method shows a purchase event with its own transaction ID.
  • Rerun the order comparison on the first closed week after the fix. Missing orders share no payment method, country or device.
  • The share still missing sits within declines plus blockers.

The fix only counts orders from go-live. GA4 can’t rebuild purchases it never received. For earlier weeks, the shop’s order data is the record.

Common questions

Why is my GA4 purchase event not firing?

The order got lost at one of four points: the shopper never reached the thank-you page, the purchase tag never fired there, consent blocked it, or GA4 dropped it. The usual culprits: PayPal or another off-site payment not sending the shopper back, a trigger on a thank-you URL that changed, a Shopify thank-you page upgrade that removed the old script, a tag waiting for consent, or the wrong G- measurement ID.

Why do PayPal orders not show as purchases in GA4?

PayPal takes payment off your site. If the shopper isn’t sent straight back, they have to click a button to return, and anyone who closes the tab first never loads the thank-you page, so no tag fires. On PayPal Payments Standard, turn Auto Return on. On a plugin or newer PayPal integration, check how that integration returns the shopper.

Shopify purchases stopped in GA4 from one day. Why?

Check whether the Thank you and Order status pages were upgraded. Shopify says the upgrade replaces existing customisations on those pages, so purchase code that lived in Additional scripts stops. Rebuild it as a pixel subscribed to checkout_completed.

The purchase tag fires in GTM Preview. Why is nothing in GA4?

Preview runs your unpublished workspace, so check the change was published. Then check the tag sends to the right G- measurement ID, that the event name is lowercase purchase, and that a data filter isn’t excluding your test traffic.

Is it normal for GA4 to show fewer purchases than the shop?

Some gap, yes. Shoppers who decline cookies or block trackers aren’t fully measured. A gap evenly spread across payment methods and devices, no larger than declines plus blockers, is the setup working. Every order missing, or every order from one payment route, is a fault.

My test order isn’t in GA4 reports. Is the tag broken?

Not necessarily. Reports can take 24 to 48 hours; use DebugView or Realtime for a test. An active internal traffic or developer traffic filter also excludes test orders, and GA4 can’t recover filtered data.

Sources

Read on 7 November 2026:

  • Shopify, checkout_completed (once per checkout, typically on the Thank you page; on the first upsell offer page when there is one, and not again on the Thank you page; not triggered at all if that page fails to load)
  • Shopify Help Center, Customize and upgrade your Thank you and Order status pages (additional scripts view-only from 28 August 2025; the upgrade replaces existing customisations; 26 August 2026 for non-Plus stores; use pixels to keep tracking customer events), Managing custom pixels (a pixel must be connected before it tracks; Disconnected pixels) and Custom pixel code (web pixels run only when visitors have given the permissions in the pixel configuration)
  • PayPal Help Center, Auto Return (PayPal Payments Standard; redirects buyers back to your website after payment; Account Settings, Website payments, Website preferences; Return URL)
  • GTM4WP, plugin page and FAQ (gateways that don’t redirect back by default; plugins that alter the order received page; Custom order received page and Reliable purchase tracking since 2.0)
  • Google for Developers, The data layer (casing must match; never overwrite or re-assign window.dataLayer)
  • Google Tag Manager Help, Publishing (changes must be published to be operational) and Consent settings (Require additional consent for tag to fire; Consent Overview)
  • Google for Developers, Consent mode overview (basic: no data transferred when declined; advanced: consent state and cookieless measurements sent)
  • Google Analytics Help, Behavioral modeling for consent mode (1,000 events a day with analytics_storage denied for 7 days; 1,000 daily consenting users on 7 of the previous 28 days; meeting them doesn’t guarantee eligibility)
  • Google Analytics Help, Event naming rules (event names are case sensitive), Data filters (internal and developer traffic; filtered data is not recoverable), Data thresholds (data may be withheld in reports and explorations), DebugView (not visible without analytics consent) and Data freshness (24 to 48 hours; Realtime covers 30 minutes)
  • Google for Developers, Validate your ecommerce setup (only the first event with a given transaction ID is collected) and Measurement Protocol (augments tag collection, not a replacement; server-to-server and offline events)

← back to the reading room