GA4 Ecommerce Tracking: The Complete Setup Guide

Most GA4 ecommerce setups are good enough to show you a revenue total and nothing useful beyond it. The purchase event fires, a number appears in a report, and everyone assumes the tracking is done. Then someone asks where shoppers are dropping out of checkout, or which products fail to convert, and the data cannot answer, because the events that would answer it were never sent correctly.

Proper GA4 ecommerce tracking is not about counting sales. It is about instrumenting the whole journey so you can see where revenue leaks and price what each leak costs. This guide covers the ecommerce events you actually need, how to implement them correctly, how to validate that they work, and how to read the result to find revenue leaks rather than just admire a total.

What GA4 ecommerce tracking is

GA4 ecommerce tracking is the set of events and parameters that record how shoppers move through your store, from viewing a product to completing a purchase, so that Google Analytics 4 can report on your funnel, products and revenue.

It is more than a conversion pixel. Done properly, it captures each stage of the buying journey as a distinct event with structured product and value data attached, which is what lets you analyze drop-off, product performance and revenue by segment. Done improperly, it still shows a purchase count, which is exactly why so many broken setups go unnoticed for months.

This guide is the foundation of the analytics cluster. Once tracking is correct, you can build funnels and revenue reports on top of it, and you can feed clean data into the Revenue Intelligence framework to price and rank the leaks it reveals.

Why tracking is the foundation of Revenue Intelligence

You cannot find, price or fix a revenue leak you cannot see. Correct GA4 ecommerce tracking is what makes the leaks visible, by recording each step of the journey so you can measure the drop-off, and the lost revenue, at every stage.

A revenue leak is a specific point where ready buyers drop out and the sale is lost. To act on one, you first have to observe it: how many shoppers reached that step, how many continued, and what the gap is worth. That observation depends entirely on the events being sent correctly. If your begin_checkout event does not fire, your checkout funnel has a hole in the middle and every conclusion drawn from it is wrong.

This is why tracking comes before tactics. The Revenue Intelligence framework begins with identifying and quantifying leaks, and both steps run on the data GA4 collects. Get the tracking right and the rest of the discipline has something true to work with. Get it wrong and you optimize confidently in the wrong direction.

The GA4 ecommerce events you actually need

Google defines a set of recommended ecommerce events. You do not need every one, but you need enough to see each stage of the journey. The table maps the core events to the leak each one helps you find.

The view_item, add_to_cart, begin_checkout and purchase events are the minimum for a usable funnel. Adding add_shipping_info and add_payment_info lets you isolate friction inside checkout, which is often where the largest, most fixable leaks hide, as covered in our guide to checkout optimization.

How to implement GA4 ecommerce tracking

Step 1: Plan the measurement before you tag

Do not start by copying a snippet. Start by mapping your journey to events and deciding what question each one answers. A tracking plan that lists every event, the parameters it must carry, and the leak it helps you find, prevents the most common outcome: events that fire but cannot answer any real question.

Step 2: Send each event with a correct items array

Every ecommerce event carries an items array describing the products involved, plus value and currency on the events where money is in play. This structure is what powers product and revenue reports. A purchase event with no items, or with value in the wrong place, will still count a conversion while breaking every product-level report.

Here is a correctly formed purchase event:

gtag('event', 'purchase', {
  transaction_id: 'T_12345',
  value: 72.05,
  currency: 'USD',
  items: [
    { item_id: 'SKU_123', item_name: 'Merino Beanie', price: 29.00, quantity: 1 },
    { item_id: 'SKU_456', item_name: 'Wool Scarf', price: 43.05, quantity: 1 }
  ]
});

The details matter. value should be the order total you want to report as revenue, currency must be a valid ISO code, and each item needs at least an item_id and item_name. The same items structure carries through view_item, add_to_cart and begin_checkout, so a shopper's journey stays consistent from view to purchase.

Step 3: Implement through GTM or your platform

There are two common paths. Google Tag Manager reads a dataLayer your site populates and sends the events to GA4, which keeps tracking logic out of your templates and is the flexible choice for custom or headless stores. Alternatively, ecommerce platforms and their apps can send GA4 events directly.

On Shopify, a GA4 integration can emit the standard events for you, which is the fastest route, though you should still validate that every event and parameter arrives as expected rather than assuming it does. Whichever path you choose, the principle is the same: one clean, consistent stream of correctly parameterized events.

Step 4: Validate in DebugView before you trust it

This is the step teams skip and later regret. GA4's DebugView shows events arriving in real time, with their parameters, so you can confirm each one fires correctly before you rely on the reports.

• Trigger each event manually: view a product, add to cart, start checkout, complete a test purchase.
• Confirm each event appears with the right name, and that items, value and currency are present and correct.
• Check both mobile and desktop, because a tag can fire on one and silently fail on the other.

Step 5: Avoid the common implementation errors

A handful of mistakes account for most broken GA4 ecommerce setups:

• A missing or empty items array, which breaks all product-level reporting while conversions still count.
• value sent as a string or in the wrong field, so revenue reports are blank or wrong.
• Double-counted purchases from an event that fires on page reload, inflating revenue and conversion.
• Inconsistent item_id between events, so a product's journey cannot be followed from view to purchase.
• Wrong or missing currency, especially for multi-currency stores, which corrupts revenue totals.

Reading the data to find revenue leaks

Correct tracking is the means, not the end. The point is to read the funnel in revenue terms and find where you are losing the most.

• Build a funnel across view_item, add_to_cart, begin_checkout and purchase, and read the drop-off at each step. The largest drop is the largest opportunity.
• Segment by device. A funnel that looks healthy overall often hides a mobile checkout that is quietly failing.
• Compare products. A product with many view_item events and few add_to_cart events has a product page problem, addressed in our guide to product page optimization.
• Translate drop-off into money. Multiply the drop at a step by the traffic reaching it and your average order value to price the leak. The revenue loss calculator and conversion rate lift calculator help, and our guide to revenue leak detection shows the full method.

This is where tracking becomes Revenue Intelligence: clean events become a ranked list of priced leaks you can actually act on.

Attribution and consent in GA4

Two settings shape how GA4 reports the revenue you track. Both are worth getting right.

• Attribution. GA4 now uses data-driven attribution by default rather than last-click, distributing conversion credit across touchpoints from your own data. It changes which channels get credit for the revenue your events record. Our guide to revenue attribution covers how to read and validate it.
• Consent. Privacy rules mean a share of shoppers will not be tracked. Consent Mode adjusts GA4 behaviour based on the consent a visitor gives, and GA4 models some of the gap. Understand that your tracked numbers represent consented, observed activity, not every shopper, and plan analysis accordingly.

Common GA4 ecommerce tracking mistakes

Even careful teams repeat these. Treat the list as a pre-flight check.

• Assuming a purchase count means tracking works. A conversion can fire while every product and funnel report is broken.
• Skipping DebugView validation. Silent failures are the norm, and they only surface when you try to use the data.
• Tracking only the purchase. Without the mid-funnel events, you can see that you lose sales but never where.
• Ignoring the items array. It is what powers product reporting, and it is the most commonly malformed part.
• Never re-checking after a theme or app change. Tracking that worked last quarter can break the moment the site changes.
• Reporting a total instead of a funnel. A revenue number is a scoreboard; a funnel is a map of where to act.

The GA4 ecommerce tracking checklist

Use this to audit any store's GA4 ecommerce setup in a single pass.

• A tracking plan maps each event to a journey stage and the leak it reveals.
• The core events fire: view_item, add_to_cart, begin_checkout, purchase.
• Mid-checkout events fire: add_shipping_info, add_payment_info.
• Every event carries a correct items array, and money events carry value and currency.
• item_id is consistent across a product's events, so journeys can be followed.
• Every event has been validated in DebugView, on mobile and desktop.
• Purchases are not double-counted on reload.
• The funnel is read as drop-off by step, segmented by device, and priced in revenue.

Frequently asked questions

What is GA4 ecommerce tracking?

GA4 ecommerce tracking is the set of events and parameters that record how shoppers move through your store, from viewing products to purchasing, so Google Analytics 4 can report on your funnel, products and revenue. It replaced the ecommerce tracking in Universal Analytics.

What ecommerce events does GA4 need?

At minimum, view_item, add_to_cart, begin_checkout and purchase, which give you a usable funnel. Add add_shipping_info and add_payment_info to see friction inside checkout, view_item_list for merchandising, and refund to track avoidable returns.

Why is the items array important in GA4?

The items array describes the products in each event and powers all product-level reporting. If it is missing or malformed, GA4 still counts conversions but your product and revenue reports break, which is one of the most common and least noticed setup failures.

How do I validate GA4 ecommerce tracking?

Use DebugView. Walk the full journey, view a product, add to cart, begin checkout, complete a test purchase, and confirm each event arrives with the correct name and parameters, including items, value and currency. Check on both mobile and desktop, because a tag can fire on one and fail on the other.

Why does GA4 show conversions but no revenue?

Usually because value is missing, sent as a string, or placed in the wrong field on the purchase event, or currency is missing or invalid. The conversion counts, but GA4 has no valid amount to report, so revenue shows as zero or blank.

Should I use Google Tag Manager or a platform integration for GA4?

Either works. Google Tag Manager keeps tracking logic out of your templates and suits custom or headless stores. A platform or app integration is faster to set up. Whichever you choose, validate every event in DebugView rather than assuming the integration is correct.

How does GA4 tracking help find revenue leaks?

By recording each stage of the journey, it lets you build a funnel and see the drop-off at every step. Multiply a step's drop-off by the traffic reaching it and your average order value, and you have the price of that leak. Clean tracking is what turns analytics into a ranked list of priced leaks.

Does GA4 track every shopper?

No. Privacy rules and consent requirements mean a share of shoppers are not tracked, and GA4 models part of the gap. Your reported numbers represent consented, observed activity. Consent Mode governs how GA4 behaves based on the consent each visitor gives.

What attribution model does GA4 use?

GA4 uses data-driven attribution by default, which distributes conversion credit across touchpoints based on your data rather than assigning it all to the last click. See our guide to revenue attribution for how to interpret and validate it.

What is a revenue leak?

A revenue leak is a specific, fixable point where ready buyers drop out and the sale is lost. GA4 ecommerce tracking is how you make those leaks visible so they can be priced and fixed. See our definition of a revenue leak for the full concept.

Conclusion and next steps

GA4 ecommerce tracking is worth doing properly because it is the foundation everything else stands on. A setup that only counts purchases tells you the score. A setup that records the whole journey, validated and correctly parameterized, tells you where revenue leaks and what each leak is worth, which is the input Revenue Intelligence turns into action.

Your next three moves:

1. Write a tracking plan that maps each ecommerce event to a journey stage and the leak it reveals, then implement and validate it in DebugView.
2. Read your funnel as drop-off by step, and price the biggest leak with the revenue loss calculator.
3. Turn the data into action with the Revenue Intelligence framework, or run a free revenue audit that prices the leaks in your funnel for you, with the evidence behind each number.

Track the whole journey, validate every event, and read the funnel in revenue. That is how GA4 stops being a scoreboard and starts being a map to your next recovered dollar.