GA4 eCommerce Tracking: A Practical Checklist for Accurate Revenue Data

A practical checklist for setting up GA4 eCommerce events correctly, so the revenue and product data in your reports reflect what actually happened in your store.

Google Analytics 4 can report revenue, products and the full shopping journey, but only if the right events arrive with the right parameters. Small mistakes like a missing currency, a duplicated purchase or a badly formatted items array quietly distort your reports.

Use the recommended eCommerce events

GA4 has a set of recommended eCommerce events. Using these exact names is what unlocks the built-in monetization reports.

  • view_item_list and select_item
  • view_item
  • add_to_cart and remove_from_cart
  • begin_checkout, add_shipping_info and add_payment_info
  • purchase, plus refund if you process refunds

Send the parameters GA4 expects

The purchase event matters most. At a minimum it should include:

  • transaction_id, unique for every order
  • value, the order total you want to report
  • currency, as a three-letter ISO code such as USD
  • items, an array with an item_id or item_name for each product, plus price and quantity

Decide upfront whether value includes tax and shipping, send those separately in the tax and shipping parameters, and stay consistent.

Use Google Tag Manager with a clean data layer

The most reliable setups push eCommerce data to the data layer from the website or store platform, then use GTM to send it to GA4. Clear the previous ecommerce object before each new push, for example with dataLayer.push({ ecommerce: null }), so data from one event doesn’t leak into the next.

Avoid the classic duplicate purchase

Duplicate purchases usually happen when the thank-you page is reloaded or revisited, or when two different tags send the same event. A unique transaction_id helps, but it is still worth preventing the double fire at the source by sending the purchase only once per order.

Test before you trust the numbers

  • Use GTM Preview mode and GA4 DebugView to watch each event arrive with its parameters.
  • Place a real test order and compare GA4 with your store backend and payment provider.
  • Check the monetization reports a day or two later, since standard reports are not real time.
  • Confirm purchase is marked as a key event in GA4 Admin.

Expect small, explainable differences

GA4 will rarely match your store to the last cent. Consent choices, ad blockers and refunds all create gaps. The goal is a small difference you can explain, not a perfect match. If the gap is large or growing, something in the setup needs attention.

Ads or tracking not adding up? Let’s fix it.