GA4 Ecommerce Events Checklist: The 9 Events You Need to Set Up Now

If you sell online and rely on GA4 to understand what happens between the storefront and checkout, ecommerce events are your wiring. Wired correctly, you see every step of the customer journey, from the product list all the way to purchase and refund. Wired badly, you get numbers that look right but aren’t: inflated revenue, phantom carts, conversion rates that make no sense.

The problem is that GA4 doesn’t track ecommerce automatically. Enhanced measurement handles clicks, scrolls and downloads, but purchase events have to be implemented by hand, with the correct data structure. This guide walks through the 9 events to set up right now, one by one, with the required parameters and the mistakes that most often skew the data. Treat it as an operational manual: use it as a checklist and tick off one line at a time.

How GA4 thinks about ecommerce events

Before the checklist, one concept needs to be locked in: in GA4, every ecommerce event revolves around a parameter called items. It’s an array (a list) describing the products involved, with properties like item_id, item_name, price and quantity, plus optional ones like brand, category and variant. Without the items array, your events still fire, but they stay empty shells: GA4 logs “someone added to cart” without knowing what.

Two other parameters are just as decisive. value is the monetary value of the action, and currency is the ISO currency code (for Italy, “EUR”). They always go together: send value without currency and GA4 won’t calculate revenue. Finally, use Google’s recommended event names exactly as documented (view_item, add_to_cart, purchase, and so on): those are what feed the default ecommerce reports. An event called “cart_add” still works as a generic event, but it falls outside commerce reporting entirely.

In practice, these events are the most granular layer of your ecommerce tracking system: if this layer is wrong, everything you build on top of it inherits the error.

The 9 GA4 events checklist to set up now

These 9 events cover the entire purchase journey, from product discovery to refund. Set them up in this order: it mirrors the funnel and lets you read drop-offs step by step, so you can immediately spot which ecommerce KPIs are suffering.

The actual implementation depends on the platform: many stores (for example on Shopify connected to GA4) already send part of these events through an app or theme, but they almost always need to be completed, corrected and tested. Never assume it “just works by default.”

1. view_item_list

Fires when the user views a list of products: a category, search results, a grid on the homepage. It measures which lists generate interest. Common mistake: passing the whole page as a single list without item_list_name, so you can’t tell the “Shoes” category apart from the “Recommended for you” section.

2. view_item

Fires when a product page opens. It’s the first event with an economic value attached (the product’s price). Common mistake: setting value to the price but forgetting currency, or sending the price as text (“$29.90”) instead of a plain number (29.90).

3. add_to_cart

The heart of purchase intent. Fires when a product enters the cart, with quantity and price. Common mistake: firing it on page load instead of on the button click, inflating add_to_cart counts. Always verify it fires exactly once per real action.

4. view_cart

Fires when the cart opens (dedicated page or side drawer). It measures how many users revisit the cart before deciding. Common mistake: confusing it with begin_checkout. They’re two distinct steps, and keeping them separate lets you see precisely where the customer stalls.

5. begin_checkout

Fires when the user starts the checkout process. It’s the dividing line between “browsing” and “buying.” Common mistake: not including the full items array, which loses the cart’s value going into checkout and makes it impossible to calculate drop-off by price range.

6. add_shipping_info

Fires when the user selects a shipping method (parameter shipping_tier, e.g. “Standard” or “Express”). It tells you whether a shipping option is blocking conversion. Common mistake: skipping it because “begin_checkout already covers it,” losing visibility into one of the most frequent drop-off points.

7. add_payment_info

Fires when the user enters a payment method (parameter payment_type). It’s the last step before purchase and one of the costliest drop-off points. Common mistake: omitting it entirely, leaving a blind spot in the funnel exactly where you’d need to understand why the customer stops.

8. purchase

The most important event: it records a completed order. It requires transaction_id (a unique order identifier), value, currency and the items array, plus ideally shipping, tax and coupon. Mark it as a key event in GA4 so it counts as a conversion. Common mistake: the event fires twice because the customer reloads the thank-you page. GA4 uses transaction_id to recognize transactions, but the safest approach is to make sure purchase fires only once.

9. refund

Fires on a full or partial refund. Use the same transaction_id as the original purchase; for partial refunds, include only the returned products in the items array. Common mistake: not implementing it at all, so GA4’s revenue stays gross and doesn’t reflect returns — a figure that, in some industries (fashion above all), radically changes the real ROI.

Three complementary events to add once the base funnel is solid: select_item (clicking a product inside a list, to link lists to product views), remove_from_cart (removing an item from the cart) and add_to_wishlist. They’re not as high-priority as the 9 above, but they sharpen your read on micro drop-offs.