Skip to main content

GA4 Purchase Event Broken: Missing transaction_id, Items or Revenue

Zero revenue means missing value and currency. Missing items means a malformed array. No transaction_id means double-counted orders.

inX

The purchase event is the one event that has to be right. Everything else in GA4 is context. And in almost every audit I run, purchase is half-broken in some quiet way — the count looks plausible, the revenue column reads $0.00, and nobody noticed for four months because nobody opened the Monetization reports. Symptom by symptom:

Two columns listing purchase parameters GA4 ignores, such as revenue and total, against the ones it actually reads: value, currency, items with item_id, and transaction_id.
GA4 never sums the items array to get revenue, so a perfect items block can still report $0.00.
Accepted, then ignoredWhat GA4 actually reads
revenue: 149.90value: 149.90 as a number
total, price or order_valuecurrency: "USD" (ISO 4217)
"$149.90" or "1,499.00"items[] with item_id or item_name
"usd", "USD ", "$", "US Dollar"price and quantity as numbers
Item prices, summed for revenuetransaction_id = real order ID

Why does GA4 show purchases but zero revenue?

Because your event sends revenue under a parameter name GA4 doesn't read. GA4 wants exactly two things at the event level: value (a number) and currency (a three-letter ISO 4217 code). Send revenue, total, price, or order_value instead and GA4 accepts the event happily, then reports zero.

Invalid currency does the same thing. "USD " with a trailing space, "usd", "$", "US Dollar" — all wrong. It has to be a clean USD, EUR, GBP.

The part that surprises people most: GA4 does not sum your items array to calculate revenue. You can send a perfect items array with correct prices and still get $0.00 — item-level price feeds item reports, not purchase revenue.

// Wrong — GA4 reports 0 revenue
dataLayer.push({
  event: "purchase",
  ecommerce: { transaction_id: "1042", revenue: 149.90, items: [] }
});

// Right
dataLayer.push({ ecommerce: null });   // clear the previous object
dataLayer.push({
  event: "purchase",
  ecommerce: {
    transaction_id: "1042",
    value: 149.90,        // number, not "$149.90"
    currency: "USD",
    tax: 12.30,
    shipping: 9.99,
    items: [ /* ... */ ]
  }
});

Why is my items array missing or empty in GA4?

Usually because it's nested in the wrong place, or the item fields use your platform's names instead of GA4's. Three things break it:

  1. Nesting. With a GA4 Ecommerce tag reading the data layer, items lives inside ecommerce. With a direct gtag('event', 'purchase', {...}) call it sits at the top level. Mix the two and the array vanishes.
  2. Field names. GA4 needs item_id and/or item_name — at least one per item. Your cart may be handing you id, sku, name, or product_id. Those get dropped. Same for price and quantity: no other spelling works.
  3. Types. price and quantity must be numbers. Carts love to hand you "quantity": "2" and prices in cents. Cast them, and divide cents by 100.

One more that's easy to miss: a stale ecommerce object. GTM's data layer persists, so an old view_item payload can bleed into your purchase. Push { ecommerce: null } immediately before every ecommerce event. Cheap insurance.

A five-stage flow showing a thank-you page purchase, a customer refresh creating a duplicate, GA4 unable to deduplicate without transaction_id, overstated revenue, and the fix.
Deduplication and Google Ads conversion adjustments both hang off the same field: your platform's real order ID.
  1. Thank-you page — purchase event fires on load
  2. Customer refreshes — Second purchase, same revenue
  3. No transaction_id — GA4 can't recognize the repeat
  4. Revenue overstated — GA4 reads above your store admin
  5. Real order ID sent — Repeats dropped, refunds adjustable

What breaks when transaction_id is missing?

Deduplication and Google Ads adjustments — both silently. transaction_id is GA4's key for recognizing that two purchase events describe the same order. Without it, a customer who refreshes the thank-you page, hits back and forward, or reopens the confirmation link hands you a second purchase with the same revenue. I've seen stores report 30% more revenue than their Shopify admin from exactly this.

Send it and GA4 will catch obvious repeats. Don't treat that as bulletproof — assume dedup covers near-term duplicates, not an event replayed days later. Fix the cause too: store a flag keyed on the order ID and skip the push if it already fired.

It's also the order ID you need for Google Ads conversion adjustments — retracting a refunded order or restating its value. No order ID on the original conversion, no adjustment, and you can't go back and add it.

Why don't my numbers add up on a multi-currency store?

Because GA4 converts each event's value into the property's reporting currency at that day's rate, and it can only do that if currency is accurate per event. Hardcode USD while some customers pay in EUR and your totals go wrong in a way that never looks obviously wrong. Send the currency the customer actually paid in, and value in that same currency.

Tax and shipping cause the same drift. GA4 has dedicated tax and shipping parameters, so break those out and decide whether value includes them. What sinks people is inconsistency: GA4 gets the total with shipping, Google Ads gets it without, Meta gets subtotal before discount. Pick one definition and apply it everywhere.

Why are my purchases missing entirely?

Before assuming the payload is broken, check where it's going. The most common cause of "no purchases at all" is a measurement ID pointing at the wrong property — a staging container promoted to production, or a second GA4 tag firing on checkout with the dev ID. The events exist; they're in a property nobody looks at. Open DebugView on your production property while placing a real order. If nothing arrives but Tag Assistant says the tag fired, it's a destination problem, not a payload problem.

The other one is consent. Under Consent Mode v2, purchases from EEA visitors who declined analytics storage won't appear as normal events. Config decision, not a bug — but know it's happening before you compare GA4 to your order count.

Five ordered verification steps for a GA4 purchase event, starting at the raw DebugView payload and ending with a monthly reconciliation against real store orders.
Reconcile individual orders, not totals — totals hide errors that cancel each other out.
  1. DebugView, payload level — Place a real test order, expand the purchase event, and check value, currency and items
  2. Realtime — Confirms the event lands outside debug mode, and shows whether revenue reads $0
  3. Monetization, next day — Standard reports lag 24 hours; item names showing (not set) mean a malformed array
  4. Reconcile ten real orders — Compare your store admin field by field: transaction IDs, values, item counts
  5. Repeat monthly — Tracking breaks quietly when a theme update changes the checkout template

How do you actually verify the purchase event?

In this order, and don't skip to the reports:

  1. DebugView, payload level. Place a real test order with debug mode on, click the purchase event, expand it. Is value a number? Is currency a clean code? Does items have entries with item_id? This is the only place you see what GA4 received rather than what you think you sent.
  2. Realtime. Confirms the event lands outside debug mode, and it shows revenue — a $0 purchase here is a parameter problem you catch in minutes.
  3. Monetization → Ecommerce purchases, next day. Standard reports lag, so give it 24 hours. Item names showing "(not set)" means a malformed items array even though the event count looks fine.
  4. Reconcile ten real orders. Compare yesterday's last ten orders from your store admin field by field against GA4's transaction IDs, values, and item counts. Individual orders, not totals — totals hide compensating errors.

Make that reconciliation monthly. Tracking doesn't break loudly. It breaks when a theme update changes a template and nobody re-tests checkout.

Why does first-party server-side tracking close this for good?

Every failure above shares a root cause: the purchase event is assembled in the customer's browser, from whatever the theme happens to expose, on a page that may or may not finish loading. Server-side tracking moves that assembly to a server you control — a tagging container on your own subdomain, something like data.yourstore.com, that receives the order and forwards it to GA4, Google Ads, and Meta. First-party, because it runs on your domain instead of a third party's.

For a broken purchase event, that changes three things. The event is built from the backend order object, so it cannot be missing fields the order already has — value, currency, line items, and the real order ID come straight from the record instead of being scraped out of the DOM. Deduplication becomes reliable: one server holds the order ID and decides once whether that purchase has been reported, for every platform. And purchases stop disappearing — ad blockers, iOS privacy limits, and abandoned thank-you pages all interrupt browser tags, and none of them touch a server-to-server call.

Reconciliation gets fixed at the source too: one server, one definition of value, feeding every platform.

Frequently asked questions

Why is my GA4 purchase event showing 0 revenue?

Your event is missing the value parameter, sending it under a different name like revenue, or missing a valid currency code. GA4 does not calculate revenue from the items array — event-level value plus currency is required.

Is transaction_id required for the GA4 purchase event?

Treat it as required. It's how GA4 identifies duplicate purchases, and it's the order ID you'll need later for Google Ads conversion adjustments on refunds. Use your platform's real order ID, never a generated one.

Why are my GA4 items showing as (not set)?

The items array is malformed — usually missing item_id and item_name, or using platform field names like sku and product_id. Check the raw payload in DebugView rather than the reports.

How do I stop GA4 double-counting purchases on page refresh?

Send a consistent transaction_id so GA4 can recognize repeats, and guard the data layer push so it fires once per order using sessionStorage or a cookie keyed on the order ID. Server-side tracking removes the problem entirely.

Should GA4 purchase value include shipping and tax?

Either is defensible, but be consistent across GA4, Google Ads, and Meta. Send tax and shipping as their own parameters so you can analyze them separately regardless of what's in value.

Why doesn't my GA4 revenue match my Shopify or WooCommerce reports?

Common causes: browser tags blocked by ad blockers or iOS, declined analytics consent, thank-you pages that never load, refunds not sent back to GA4, and currency mismatches. A gap under about 5% is normal for browser-only tracking; more than that means something's broken.

  • ga4
  • ecommerce
  • purchase event
  • fix it
SETUP GUIDES

Guides for this topic

How accurate is your conversion tracking?

PLATFORM-REPORTEDconversionsdivided byBACKENDreal orders or leadsequalsaccuracy
TRY IT · YOUR NUMBERS
68%Broken. Something is missing entirely. Worth a free audit.
Reading guides because something is broken?Book 30 minutes with Ariful. We'll find it on the call and send a written fix list within 24 hours.
Get my free audit →
Ariful Islam
WRITTEN BYAriful IslamFounder of Tracking Consulting and a computer engineer (Diploma, BSc, MSc in CSE). 300+ clients and 1,000+ tracking projects since 2019.
About Ariful →
FREE · 30-MIN CALL · WRITTEN AUDIT IN 24H

Want us to check your accuracy for you?

We look at your setup together on the call. Within 24 hours you get a written audit and a prioritized fix list you can hand to any developer. Not a fit? We'll say so.