GA4 Ecommerce Reporting: Reports, Metrics and a Dashboard

Analyst reviewing an ecommerce sales report

GA4 ecommerce reporting works in three layers. Ecommerce events collect the data, the standard reports (Ecommerce purchases and Monetization overview) summarize it, and Explorations let you dig into funnels and segments. If the events are wrong or incomplete, every report above them is wrong too. This guide shows where each report lives, which metrics deserve a place on your dashboard, how to build a purchase funnel, and how to check that the numbers can be trusted.

Quicktoimpress
Make Ecommerce Data Actionable
Quicktoimpress builds growth systems for scaling companies, including commerce platforms, integrations, and automation that connect reporting to business operations.
Explore Quicktoimpress

TL;DR

  • GA4 fills the Ecommerce purchases and Monetization overview reports automatically, but only after you implement the recommended ecommerce events with the required parameters.
  • Start your dashboard with four item metrics: Item revenue, Items added to cart, Items purchased and Items viewed.
  • Use a Funnel exploration built on begin_checkout, add_shipping_info, add_payment_info and purchase to find where checkout abandonment happens.
  • Validate with DebugView before you trust a report, and allow up to 24 hours for standard reports to populate.
  • Reporting is only as good as the tracking behind it. Get the data layer right first, then build views on top.

Table of Contents

What GA4 ecommerce reporting actually covers

People use “ecommerce reporting” to mean three different things, and mixing them up causes most of the confusion.

  1. Standard reports. Pre-built views inside the Reports section. They need no configuration beyond sending the right events.
  2. Explorations. Flexible analysis tools for funnels, paths and segment comparisons. Google recommends them for deeper work such as checkout funnels once ecommerce events are configured, per its ecommerce exploration guidance.
  3. Exports and dashboards. Data pushed to BigQuery, pulled through the Data API, or visualized in an external tool. Google notes that Explorations, BigQuery and the Data API support custom analysis and external tools.

A useful dashboard usually draws on all three: a standard report for the daily pulse, an exploration for diagnosis, and an export when you need to join sales data with ad spend, CRM records or inventory.

Where the standard ecommerce reports live

The main report is Ecommerce purchases. Google describes it as a pre-made detail report showing information about the products or services you sell, and you find it under Reports in the left menu. The companion report is Monetization overview, which sits in the same area and gives you the time-series summary of revenue and purchase activity.

If you are used to Universal Analytics, here is how the old views map across, according to Google’s UA-to-GA4 report comparison:

Universal Analytics report GA4 equivalent
Ecommerce Overview Monetization overview
Shopping Behavior Purchase journey
Checkout Behavior Checkout journey
Product Performance Ecommerce purchases
Marketing reports Promotions or Order coupons

Two practical notes. First, none of these reports show anything until the underlying events arrive. Second, the names differ from what many teams remember, so if a stakeholder asks for “the shopping behavior report,” point them to Purchase journey.

The events that feed every report

GA4 does not collect ecommerce events by default. They need extra context such as product IDs, prices and quantities, so you add them to your website, app or Google Tag Manager container. Google’s recommended events list covers the full shopping journey:

  • view_item_list, view_item, select_item
  • view_promotion, select_promotion
  • add_to_wishlist, add_to_cart, view_cart, remove_from_cart
  • begin_checkout, add_shipping_info, add_payment_info
  • purchase, refund

You do not have to send all of them on day one, but the more of the journey you cover, the more your funnel and product reports can tell you.

The purchase event is the one that matters most

Google’s event reference says a purchase event represents one or more items bought by a user. It requires a transaction_id and an items array, and currency is required whenever you send a value. The same reference specifies that purchase value should equal the sum of price multiplied by quantity for all items, excluding shipping and tax.

That last rule is where reports and finance systems drift apart. If your platform sends a value that includes shipping and tax, GA4 revenue will not match the revenue your accounting team sees, and nobody will know why until someone checks the payload.

Placement matters too. Google recommends firing purchase on the page where the purchase occurs, such as a confirmation page, or triggering it from the purchase action itself.

The purchase event is the one that matters most

Item-level versus event-level parameters

Google separates item-level parameters, which describe products inside the items array, from event-level parameters, which describe the interaction outside that array. Put the item name, ID, category, price and quantity inside items. Put the currency, transaction ID and coupon at the event level. Mixing them up is a common reason a report shows blank product fields.

The metrics worth putting on your dashboard

A GA4 ecommerce dashboard does not need thirty tiles. Start with the four item metrics defined in the Ecommerce purchases report documentation:

Metric What it tells you Where it comes from
Item revenue Item price multiplied by quantity, excluding tax and shipping Items arrays in purchase events
Items viewed How often products are seen view_item events
Items added to cart Purchase intent by product add_to_cart events
Items purchased Units sold Items arrays in purchase events

Read them as a set. A product with many views and few cart additions has a page problem: price, imagery, copy or page speed. A product with many cart additions and few purchases has a checkout or shipping problem. A product with strong purchases but low views is a candidate for more visibility on collection pages and in ads.

Metrics to layer on top

Once the core four are stable, add the ratios that your team actually makes decisions with:

  • Conversion rate by channel and campaign. Compare how each source converts, not just how much traffic it sends.
  • Average order value. Divide revenue by transactions, and watch it by channel and by first-time versus returning customers.
  • Cart-to-purchase rate. The cleanest single signal of checkout health.
  • Revenue by item category. Useful for merchandising and for deciding where to spend ad budget.
  • Refund rate. Only meaningful if you send the refund event, which many stores skip.

These are calculations you build from the events above, so each is only as accurate as the data behind it. If you want to understand which marketing touches deserve credit for the sales these metrics record, our guide to multi-touch attribution setup walks through the process.

Building a purchase funnel in Explorations

The standard reports tell you what happened. A funnel tells you where shoppers leave. Google’s guidance is to use the Ecommerce purchases report to view ecommerce data and a Funnel exploration to identify checkout abandonment.

A checkout funnel step by step

  1. Open Explore and create a new Funnel exploration.
  2. Add steps using begin_checkout, add_shipping_info, add_payment_info and purchase, which is the sample checkout funnel in Google’s documentation.
  3. Choose between a closed and an open funnel. Google suggests an open funnel when you want to count users who enter at a later step.
  4. Break the funnel down by device category, channel or country to see where the drop-off concentrates.
  5. Save the exploration and share it with your team.

The open-versus-closed choice changes the story. A closed funnel only counts users who begin at step one, which is stricter and shows pure progression. An open funnel counts people who return to the process mid-way, such as a shopper who comes back through a saved cart link or a direct visit to the payment step. If a lot of your buyers re-enter late, a closed funnel will understate your real conversion.

Reading the drop-offs

Look for the biggest percentage loss between adjacent steps, then segment it.

  • A large drop from begin_checkout to add_shipping_info often points to surprise shipping costs or a forced account creation.
  • A large drop between add_payment_info and purchase on mobile only often points to payment-method or form friction.
  • A sudden drop on a single day usually points to a release, not shopper behavior.

If your store runs on Shopify, our post on Shopify checkout optimization covers what to change once the funnel shows the problem.

The top of the funnel deserves the same attention. When view_item and add_to_cart numbers are weak, creative is often the lever, and ecommerce video ads that convert can help bring more qualified shoppers to the product page before they ever reach checkout.

Assembling the dashboard

A dashboard is a decision tool, not a gallery. Organize it around the questions your team asks each week.

Row one: how are sales doing? Revenue, transactions, average order value and conversion rate, compared to the previous period. Pull these from Monetization overview or from the Data API.

Row two: which products are driving it? Item revenue, items viewed, items added to cart and items purchased, by product and by category. This is the Ecommerce purchases report, filtered and sorted.

Row three: where do we lose shoppers? The checkout funnel with a device breakdown, plus the purchase journey view.

Row four: what is the marketing contribution? Revenue and conversion rate by channel and campaign, plus the Promotions report for on-site merchandising.

Keep one owner per row. When nobody owns a block of the dashboard, nobody notices when it breaks. For teams that live in a CRM as well, joining sales data with lead or customer records usually means exporting from GA4 and modeling in a warehouse or BI tool, an approach we cover alongside offline conversion tracking from CRM and POS data.

Validating the data before you trust it

Bad ecommerce data looks just like good ecommerce data until someone compares it to the order system. Build verification into the process.

Check events in real time

Google says DebugView shows realtime data for checking your event setup, and you can enable debug mode with the debug_mode parameter. Walk through a test purchase on a staging site or with a real low-cost order, and confirm each event appears with the expected parameters.

Be patient with the reports

A missing number on day one is not automatically a failure. Google states that ecommerce reports and explorations can take up to 24 hours to populate. Its ecommerce overview adds that data typically begins appearing within 24 to 48 hours once users begin using a correctly tagged site or app. Purchase data also becomes available in explorations and the Data API after about 24 hours, and in BigQuery when export is configured.

Common reasons the numbers are wrong or missing

  • Required parameters are missing. Google warns that when they are, the event is treated as a custom event and will not appear in the Ecommerce purchases report. Check transaction_id and items on every purchase.
  • Currency is not set. Send it at the event level whenever you send a value.
  • Parameters are skipped. Google’s guidance is to send every ecommerce parameter you have data for, in the documented format, and to review custom dimension and metric limits.
  • Value includes tax or shipping. It should not, per the event reference above.
  • Duplicate purchase events. A confirmation page that reloads can fire purchase twice. Deduplicate by transaction_id in your implementation.

Reconcile weekly

Compare GA4 revenue with your platform’s order revenue each week. Small differences are normal, since consent choices, ad blockers and refunds all play a part. A gap that suddenly widens is a signal to open DebugView.

Performance affects data quality too. Slow pages lose visitors before tags fire, which is one reason we pair measurement work with website performance optimization.

Our perspective

We see the same pattern in most scaling ecommerce teams. The dashboard looks polished, but the tracking underneath was set up once, by someone who has since moved on, and nobody can say with confidence what a number means.

Reporting is an engineering problem before it is a design problem. The data layer, the event payloads, the consent handling and the join to CRM and revenue systems decide whether the dashboard is a source of decisions or a source of arguments.

That is why we do not split strategy from build. The people who define which metrics matter stay involved in implementing the events, the exports and the reporting views, so the definition in the roadmap is the definition in the data. Teams get one accountable partner and a visible roadmap, instead of a handoff between an analyst, a developer and an agency.

If your GA4 numbers do not match your order system, treat that as the first project, not a footnote to the next campaign.

Growth platforms

Get reporting you can act on

If your team spends more time debating the numbers than acting on them, the fix is usually in the implementation, not in another chart. Quick To Impress embeds with marketing, revenue and technology teams to build the connected systems behind growth: clean ecommerce tracking, reporting that reconciles with your platform and CRM, and the experimentation to act on what it shows.

Quicktoimpress

Engagements run on monthly capacity. Core capacity is $3,500 to $5,999 per month, and larger tiers are listed on our pricing page. You can also see how our revenue operations work connects analytics to the CRM, or browse all capabilities.

FAQ

What is the best reporting tool for ecommerce?

Start with GA4’s own Ecommerce purchases report and Funnel exploration, since they need no extra tooling once your events are correct. Add a BI or dashboard tool when you need to combine GA4 with ad spend, CRM or order data. Google supports this through BigQuery export and the Data API.

How do I track ecommerce transactions in Google Analytics?

Implement the purchase event on your site, app or in Google Tag Manager, with transaction_id, an items array, and currency whenever you send a value. Verify it in DebugView, then allow up to 24 hours for reports to populate. Without the required parameters, the event will not appear in the Ecommerce purchases report.

Why are my GA4 ecommerce reports empty?

The most common causes are events that were never implemented, purchase events missing required parameters, or simply timing, since reports can take up to 24 hours. Check DebugView first. If events appear there with the right parameters, wait for processing before assuming something is broken.

Which GA4 ecommerce metrics matter most?

Item revenue, Items viewed, Items added to cart and Items purchased give you the clearest picture of product performance. Pair them with conversion rate by channel, average order value and cart-to-purchase rate to connect product behavior with marketing and checkout health.

Sources