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

READING ROOM › FIELD NOTE › NOTE-021

NOTE-021 · FIELD NOTE FILED 10 NOV 2026 · REVISED 10 NOV 2026 F-301 F-302 F-101

GA4 ecommerce events reference: which parameters each report needs.

ABSTRACT — When a GA4 ecommerce report shows zeros or an empty step, the event behind it was never sent or arrived without a required field. Google says such an event is treated as a custom event and won't appear in the report. Report by report: which events each one reads, which parameters are required, and a two-minute check to find the gap.

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

If a GA4 ecommerce report shows zeros or an empty step, the event behind it was never sent, or it arrived without a required field. Google says such an event is treated as a custom event: GA4 keeps it, but no ecommerce report counts it. Each report reads a fixed set of events. Ecommerce purchases reads view_item, add_to_cart and purchase. Purchase journey adds session_start and begin_checkout. Checkout journey adds add_shipping_info and add_payment_info. Promotions reads view_promotion and select_promotion.

The required fields are short. Every ecommerce event except refund and select_promotion needs items, the list of products in the event, and each item needs item_id or item_name. Send a value and you need currency. purchase also needs transaction_id, the order number.

This note works backwards from the report. How to push the events through Google Tag Manager is in the GA4 ecommerce dataLayer GTM can read. If purchases arrive with no revenue or no products, GA4 purchase events missing items or value finds the broken field. A partial event set is on file as F-301 .

Check this first

Two minutes, no code. Set the date range to a full week that ended at least two days ago (reports can take 24 to 48 hours to fill). Google labels the menu “Monetization”; depending on your property it sits under Life cycle or under Business objectives, Drive online sales.

  1. Monetization, Ecommerce purchases. Read the three item columns in the table.
    • Items viewed at 0: view_item is missing, or has no items.
    • Items added to cart at 0: same for add_to_cart.
    • Items purchased at 0 while purchases are recorded: the purchase event has no items.
  2. Monetization, Checkout journey. Four steps. An empty middle step means add_shipping_info or add_payment_info is never sent.
  3. Admin, Data display, Events. Check the names are exactly Google’s. Purchase with a capital P, or a home-made checkout_start, is a custom event, and no ecommerce report counts it.

Still can’t place the gap? Send me a screenshot of the report that looks wrong and Viewer access to the GA4 property: [email protected]. I’ll check it against the tables below and tell you what I find.

Which report reads which event?

ReportEvents it readsEmpty or (not set) when
Ecommerce purchasesview_item, add_to_cart, purchasean event, or its items, is missing
Purchase journeysession_start, view_item, add_to_cart, begin_checkout, purchasea step’s event is never sent
Checkout journeybegin_checkout, add_shipping_info, add_payment_info, purchasethe shipping or payment event is never sent
Promotionsview_promotion, select_promotionpromotion fields or items are missing
Monetization overviewpurchase (refunds subtracted from Total revenue)item_name or item_list_name not on the purchase items
GA4 ecommerce reports · the events each one reads · what an empty column points to · compiled from Google Analytics Help, read 10 November 2026

The help page for the Ecommerce purchases report sets one rule above the rest. If an ecommerce event misses a required parameter, the event “will be treated as a custom event and won’t appear in the report”. The event is typically still listed under its name in the Events report, which is why the gap is easy to miss.

What does the Ecommerce purchases report need?

Three events, each with items:

  • Items viewed counts the items on view_item.
  • Items added to cart counts the items on add_to_cart.
  • Items purchased counts the items on purchase.
  • Item revenue is price times quantity for each item, without tax or shipping.

The rows are item dimensions: item_id, item_name, item_brand and item_category to item_category5. Send only an ID and the Item name column typically shows (not set). An item with no numeric price adds nothing to Item revenue; a price like "£40.00" is not a number. That is how Item revenue can sit below purchase revenue on the same orders.

Your own item fields, such as a stock flag, only show in reports once you create an item-scoped custom dimension for each: 10 on a standard property, 25 on Analytics 360.

What feeds the Purchase journey and Checkout journey?

Purchase journey counts users at five steps: session_start, view_item, add_to_cart, begin_checkout, then purchase (or in_app_purchase in apps). Google says you can’t customise it. For other steps, build a funnel exploration in Explore with your own events.

Checkout journey counts users at four: begin_checkout, add_shipping_info, add_payment_info and purchase. Its steps can’t be changed either. The two middle events sit inside the checkout, which is often a different template, app or payment page from the rest of the shop, so check they are sent there.

On Shopify? Google’s page says Shopify collects begin_checkout, add_payment_info and purchase automatically, and that you must set up add_shipping_info yourself for this report. What each Shopify app sends is in Shopify tracking apps: what each one sends.

What does the Promotions report need?

Banners and featured slots use two events. view_promotion fires when the promotion is shown; select_promotion fires when someone clicks it.

  • Item promotion ID and Item promotion name come from promotion_id and promotion_name.
  • Item promotion creative name comes from the item-level creative_name.
  • Items viewed in promotion, Items clicked in promotion and the click-through rate count the items on those two events.

The events reference lists items as optional on select_promotion, with a warning: sent without it, the event is left out of some reports and metrics, the Promotions report among them. Send the items. You can set the promotion fields once at event level; Google copies them onto each item unless the item sets its own.

What does the Monetization overview read?

The cards read the purchase side:

  • Total revenue is purchases, subscriptions and ad revenue, minus refunds. Purchase revenue is purchases only.
  • Total purchasers and First time purchasers count the purchase event.
  • Items purchased by Item name reads item_name from the items on purchase.
  • Items purchased by Item list name reads item_list_name from the purchase event.
  • Purchase revenue by Order coupon shows the most-used coupons and the revenue from each.

The list card is the one that surprises people. A list name sent only on view_item_list or select_item stays on those events, so the purchase card typically shows (not set). To see which list sold, carry item_list_name through to the purchase items.

Which parameters are required on each event?

If you only check one row, check purchase: items, value, currency and transaction_id.

The full list, from Google’s recommended events reference. “Value pair” means value with currency: Google marks both required, and says currency is needed whenever value is set for revenue to be computed accurately.

EventRequiredWorth sending
view_item_listitems, currencyitem_list_id, item_list_name
select_itemitemsitem_list_id, item_list_name
view_itemitems, value paireach item’s price
add_to_cartitems, value pairquantity per item
remove_from_cartitems, value pairquantity per item
view_cartitems, value pairnone extra
begin_checkoutitems, value paircoupon
add_shipping_infoitems, value pairshipping_tier, coupon
add_payment_infoitems, value pairpayment_type, coupon
purchaseitems, value pair, transaction_idshipping, tax, coupon, customer_type
refundvalue pair, transaction_iditems for item-level refunds
view_promotionitemspromotion_id, promotion_name, creative_name, creative_slot
select_promotionnone listeditems (see above), promotion fields

Inside items, one of item_id or item_name is required; Google recommends both. quantity defaults to 1.

Written down per event, with where each value comes from on your site, this table is the ecommerce part of a tracking plan: the developer builds to it, and the next change is checked against it.

transaction_id matters past the requirement. GA4 drops a repeat purchase with the same ID. An ID that changes on every reload counts every reload, and a blank ID lumps orders together. Both are on file as F-101 , with the reload case in GA4 purchase event fires twice.

What should value contain, as the reports see it?

Google’s rule: value is the sum of price times quantity for the items in the event, without shipping or tax, which have their own parameters on purchase. price is the discounted unit price, and value on view_item doesn’t count as revenue.

Send shipping or tax inside value and Purchase revenue on the Monetization overview runs above the store’s product total. The mismatch across platforms is on file as F-302 . Field-level fixes (text values, symbols, missing currency) are in GA4 purchase events missing items or value.

How do refunds reach the reports?

A refund needs the original order’s transaction_id, plus currency and value. items is optional, but Google recommends it: send each refunded item with item_id and quantity, and item-level refund figures fill in alongside the order figure. If refunded orders still sit in your revenue, GA4 revenue doesn’t drop after refunds has the checks.

Common questions

Why does a GA4 ecommerce report show zeros or an empty step?

The event behind that column or step was never sent, or arrived without a required field. Google says an ecommerce event missing a required parameter is treated as a custom event and won’t appear in the report. Find the event in the report table on this page, then check its required fields.

Which parameters does every GA4 ecommerce event need?

Every ecommerce event except refund and select_promotion requires an items array (the list of products in the event), and each item needs item_id or item_name; Google recommends both. Events that carry a value need currency, a three-letter code such as GBP. Purchase and refund also need transaction_id.

Why is my GA4 Checkout journey report empty?

It reads four events: begin_checkout, add_shipping_info, add_payment_info and purchase. A step whose event is never sent stays empty. On Shopify, Google says begin_checkout, add_payment_info and purchase are collected automatically, but add_shipping_info has to be set up for this report.

What does the GA4 Purchase journey report use?

Users who triggered session_start, view_item, add_to_cart, begin_checkout and purchase (or in_app_purchase). The steps are fixed. For a different set of steps, Google points you to a custom funnel exploration.

Why is the GA4 Promotions report blank?

It needs view_promotion and select_promotion, with promotion_id, promotion_name or creative_name, and an items array. Google says a select_promotion sent without items is left out of some reports, the Promotions report among them.

Why does Item list name show (not set) on the Monetization overview?

That card reads item_list_name from the purchase event. A list name sent only on view_item_list or select_item stays on those events. Carry the list name through to the purchase items if you want lists on that card.

Sources

Read on 10 November 2026:

  • Google for Developers, Recommended events reference (required and optional parameters per ecommerce event; currency required for accurate revenue metrics if value is set; value as the sum of price times quantity, without shipping or tax; view_item value doesn’t contribute to revenue; one of item_id or item_name required; price as the discounted unit price; quantity defaults to 1; select_promotion without items left out of some reports such as Promotions; promotion fields copied from event level; item-level parameters take precedence)
  • Google for Developers, Measure ecommerce (set currency at event level when sending value; set each parameter you have data for; checkout event order; refund with transaction_id and items with item_id and quantity, item details recommended for item-level refund metrics)
  • Google for Developers, Create item-scoped custom parameters (an item-scoped custom dimension is needed to analyse a custom item parameter; 10 on standard properties, 25 on Analytics 360)
  • Google Analytics Help, Ecommerce purchases report (Items viewed, Items added to cart and Items purchased from the items array on view_item, add_to_cart and purchase; Item revenue as price times quantity; item dimensions; a missing required parameter makes the event a custom event that won’t appear in the report)
  • Google Analytics Help, Purchase journey report (five steps and their events; can’t be customised; custom funnel alternative)
  • Google Analytics Help, Checkout journey report (four steps and their events; Shopify collects begin_checkout, add_payment_info and purchase, add_shipping_info must be set up; steps can’t be modified)
  • Google Analytics Help, Promotions report (promotion dimensions from promotion_id, promotion_name and item-level creative_name on view_promotion or select_promotion; promotion metrics from the items array)
  • Google Analytics Help, Monetization overview report (total revenue minus refunds; purchase revenue; purchasers from the purchase event; items purchased by item_name and by item_list_name from the purchase event; revenue by order coupon)
  • Google Analytics Help, Minimise duplicate key events with transaction IDs (Analytics deduplicates purchases with the same transaction ID), Events in Analytics (the event list in Admin) and data freshness (reports can take 24 to 48 hours)

— B.A., filed from London

CONNECTED RECORDS F-301 F-302 F-101

REVISION HISTORY — revised 10 NOV 2026.

← back to the reading room