Google Analytics Ecommerce Reports for Magento Merchants: What to Track and Tips

Roughly seven out of every ten people who add a product to an online shopping cart never complete the purchase. The Baymard Institute, whose research aggregates data from 49 independent studies, puts the global average cart abandonment rate at 70.19%. For a Magento store doing $2 million in annual revenue, that figure implies more than $4.6 million in potential sales evaporating before a single order confirmation email is sent. The question is not whether you have a funnel problem. The question is where in the funnel the problem lives, and that is exactly what Google Analytics 4 (GA4) ecommerce reports exist to answer.

GA4 has changed substantially since it replaced Universal Analytics in 2023. On August 25, 2025, Google expanded item-scoped dimensions and metrics to all reporting types, secondary dimensions, filters, and custom reporting, something that had previously been restricted. A further update in January 2026 launched independent conversion attribution settings per conversion in beta, giving merchants more control over how GA4 assigns credit across channels. If you configured GA4 for your Magento store in 2023 or 2024 and have not revisited your setup, your reports are probably missing data that is now available.

This guide walks through the specific GA4 ecommerce reports that give Magento merchants the clearest picture of store performance, what each report measures, how to read the numbers that matter, and the practical decisions each report should drive. It also flags setup mistakes that silently break your data long before you reach the reporting stage.

Before You Read Any Report: Four Settings Magento Merchants Must Get Right

The GA4 reports described in this guide only produce accurate data when your implementation is solid. Four settings in particular cause problems for a large proportion of Magento stores.

1. Choose Your Integration Method and Do Not Double-Track

Magento 2.4.5 and later include native support for the GA4 Measurement ID under Stores > Configuration > Sales > Google API. If you are on 2.4.5 or newer, the simplest path is to add your Measurement ID (format: G-XXXXXXXXXX) and enable Enhanced Measurement. Do not also deploy GA4 through Google Tag Manager (GTM) unless you have specifically architected the setup to prevent duplicate events. Double-tracking inflates every metric in every report.

If you are on Magento 2.4.5 or earlier, or if you need advanced GTM control to track multiple pixels and tags, use the GTM route. MageDelight's Magento 2 GA4 with GTM Extension handles the full data layer setup, event mapping, and GTM template import automatically, which eliminates the most error-prone part of manual GTM implementation. The extension supports multi-store and multi-currency configurations, is compatible with Magento 2.4.8, and is already Hyvä-ready. Manual GTM setup works but requires writing the data layer pushes yourself for every ecommerce event.

2. Extend Data Retention to 14 Months

GA4's default data retention for user-level data is two months. At two months, Exploration reports (Funnel Exploration, Cohort Analysis, Path Exploration) can only query the past 60 days. For any meaningful analysis of seasonal patterns, year-over-year comparisons, or customer lifetime value, that is far too short. Go to Admin > Data Settings > Data Retention, then set the retention period to 14 months. Per the GA4 audit guidance for ecommerce brands, extending retention does not affect standard aggregated reports, which remain available beyond the retention window. It only affects Explorations. Change this setting on day one.

3. Mark Purchase as a Conversion and Check the Attribution Model

GA4 does not automatically mark purchase events as conversions in all cases. Navigate to Admin > Events and verify that the purchase event has the Conversion toggle enabled. Without this, your purchase data will not appear in Conversion reports and cannot be imported into Google Ads for Smart Bidding.

On attribution: GA4's default is last-click, which gives 100% of conversion credit to the final channel before purchase. For Magento stores processing more than 400 conversions per month, data-driven attribution is more accurate. It uses Google's machine learning to assign fractional credit based on the actual paths of converting versus non-converting users. Switching typically surfaces 15 to 25 per cent more attributed conversions in channels like branded search and email, which appear undervalued in last-click reporting. Set attribution under Admin > Attribution Settings.

4. Validate Events with DebugView Before Trusting Reports

After installing any GA4 integration in Magento, open GA4 DebugView (Admin > DebugView) and browse your store with GTM Preview Mode active. Confirm that each key event fires once and only once on the correct page: view_item on product detail pages; add_to_cart when an item is added to the cart; begin_checkout on checkout initiation; and purchase on the order success page. A purchase event firing on page reload or on back navigation to the success page creates duplicate transaction records, overstating revenue in every monetisation report.

The GA4 Ecommerce Reports Magento Merchants Need: Quick Reference

The Reports That Drive Revenue Decisions

Monetisation Overview: Your Weekly Health Check

Located at Reports > Monetisation > Overview, this report is the starting point for any weekly review. It shows total revenue, total buyers, average purchase revenue per user, and a timeline of ecommerce events. The chart is useful for one specific purpose: spotting anomalies quickly. A drop in revenue that correlates with a spike in add_to_cart events, with no corresponding increase in purchase events, points to a checkout problem. A drop in revenue with a corresponding drop in view_item events points to a traffic or discovery problem. These are two very different problems requiring two very different fixes, and this report lets you tell them apart in under two minutes.

For Magento merchants, check this report after every promotional campaign. If you ran a 20%-off promotion and revenue did not increase proportionally, look at whether buyers per day changed or whether average order value dropped. The report gives you the aggregate numbers; the next two reports tell you why.

Ecommerce Purchases Report: Which Products Are Actually Making Money

Located at Reports > Monetisation > Ecommerce purchases, this is the product-level performance report. It shows item views, add-to-cart actions, checkouts, purchases, and item revenue for every SKU in your catalogue. The August 2025 GA4 update means item-scoped dimensions (item brand, item category, item variant) now work properly as secondary dimensions and in custom filters throughout this report, which was a significant previous limitation.

Three decisions this report should drive for Magento stores:

• High views, low add-to-cart rate: The product page is attracting traffic but not converting it. Check price competitiveness, image quality, and completeness of the product description.
• High add-to-cart rate, low purchase rate: The product interests buyers but something between cart and checkout is stopping them. Cross-reference with the Purchase Journey report.
• High item revenue, low item views: These are your hidden high-performers. Increase their visibility in category listings, paid search, and internal promotions.

Drill down by Item Category to identify whether performance differences are catalog-wide or concentrated in specific product lines. For Magento stores with multiple categories, this segmentation often reveals that one or two categories are carrying the rest of the catalog.

Purchase Journey Report: Where Your Funnel Leaks

Located at Reports > Monetisation > Purchase journey, this report shows the five-stage funnel from session start through purchase. The stages are: Session start, View product (view_item), Add to cart (add_to_cart), Begin checkout (begin_checkout), and Purchase. The abandonment rate at each stage is displayed below the funnel visualization. Per Google's official ecommerce exploration documentation, this report uses a closed funnel by default. That means only users who pass through all stages in sequence are counted. Users who jump directly to checkout (for example, returning customers using a bookmark) are excluded. This is not a bug, but it is a significant caveat: the conversion rates shown are lower than your actual funnel performance, because they exclude users who re-enter at a later stage.

What to look for: if more than 50% of users are dropping at the Add to Cart to Begin Checkout step, the problem is in the cart experience, not the checkout. If the drop is concentrated between Begin Checkout and Purchase, the problem is in the checkout flow itself. For most Magento stores, that means payment options, shipping cost reveals, or checkout form complexity.

Magento Tip: If your Purchase Journey report shows high drop between 'Begin checkout' and 'Purchase', navigate to your Magento checkout and check whether the guest checkout option is prominent. Baymard Institute research shows account creation requirements are among the top reasons for checkout abandonment globally.

Checkout Journey Report: Diagnosing Specific Checkout Steps

Located at Reports > Monetisation > Checkout journey, this report is more granular than Purchase Journey. It breaks the checkout process into discrete steps, typically corresponding to add_shipping_info, add_payment_info, and the final purchase confirmation. Each step shows how many users entered versus how many proceeded.

The practical use case: if you see a large drop at the payment information step specifically, cross-reference with your Magento payment gateway error logs. Payment processing errors that happen silently (where the user sees an error message but GA4 does not receive a failure event) often appear as high abandonment at the exact step where a gateway timeout or validation error occurs.

For multi-step Magento checkouts with third-party one-page checkout extensions, verify that each checkout step fires the correct GA4 event. If your checkout consolidates steps, the Checkout Journey report will show blanks for steps that were skipped, which can make abandonment look artificially concentrated at the final step.

Traffic Acquisition Report: Which Channels Deliver Buyers, Not Just Visitors

Located at Reports > Acquisition > Traffic acquisition, this report is where channel strategy decisions live. The critical distinction for Magento merchants is between sessions and revenue by channel. A paid search campaign might deliver 40% of your sessions but only 25% of your revenue. Organic search might deliver 30% of sessions but 45% of revenue. Last-click attribution in the standard report will show these numbers, but if you have switched to data-driven attribution (as recommended above), the numbers will be more accurate about which channels genuinely contribute across the journey rather than just capturing credit at the final click.

Apply a custom date comparison in this report to measure the impact of specific campaigns. Compare the 30 days before and after a major paid search change. Compare months where email campaigns were active versus paused. The report will not tell you whether a specific campaign caused a change, but it will show you whether revenue from that channel moved when you expected it to.

Funnel Exploration: Custom Analysis for Magento-Specific Journeys

Located at Explore > Funnel exploration, this is where the analytical power of GA4 becomes specific to your store. Unlike the Purchase Journey and Checkout Journey reports (which use fixed, platform-defined funnels), Funnel Exploration lets you define the exact sequence of events and conditions you want to measure. Per Google's ecommerce exploration guidance, you can create both closed and open funnels. Open funnels count users who enter at any step, which gives a more accurate picture of actual conversion rates when users skip steps or return across sessions.

Three Magento-specific explorations worth building:

• Mobile vs. desktop funnel: Apply a device category breakdown to your purchase funnel. In most Magento stores, mobile conversion rates are significantly lower than desktop. If mobile shows a specific step with extreme drop-off not visible on desktop, that step has a mobile UX problem, not a general conversion problem.
• New visitor vs. returning customer funnel: New visitors often abandon at the payment step due to trust uncertainty. Returning customers are more likely to abandon due to price comparison. Separate funnels reveal whether your recovery emails and retargeting should focus on trust signals or on price matching.
• Category-specific funnels: For Magento stores with multiple categories at very different price points, a single funnel masks category-level differences. Build a filtered funnel for high-ticket categories separately to understand whether longer consideration time (and multiple sessions) is normal for those buyers, or whether they are genuinely losing interest.

Cohort Analysis: Are You Acquiring Customers or Just Buyers

Located at Explore > Cohort exploration, this report groups users by the week or month they were first acquired and tracks their behaviour (and ideally, their revenue) over subsequent periods. For Magento merchants, it answers a question the other reports cannot: are the customers you acquired in February still buying in May? GA4's cohort exploration documentation explains how to configure the metric (transactions, revenue, or custom event) and the retention period.

The practical read: if week-0 revenue (first purchase) is high but week-4 retention is low, your acquisition channels are finding buyers for a single transaction but not loyal customers. This affects how aggressively you should spend on acquisition versus how much you should invest in post-purchase email sequences, loyalty programs, and personalised recommendations (all of which have Magento extension ecosystems behind them).

Order Coupon Report: Whether Your Promotions Are Profitable

Accessible by drilling down from the Monetisation Overview, the Order Coupon report shows revenue attributed to each coupon code used at checkout. For Magento merchants running discount promotions through Magento's price rules, this report closes the loop between the promotion you created in the admin panel and the revenue it actually generated.

The report is more useful than it looks at first. A coupon code with high revenue does not automatically mean a profitable promotion. Cross-reference coupon revenue against the discount depth (what percentage off was given) to calculate net revenue. A code generating $50,000 in revenue at 40% discount delivered $30,000 in discount value. Whether that acquisition was worth $30,000 depends entirely on the lifetime value of those customers, which is why Cohort Analysis needs to be read alongside this report.

The GA4 vs. Magento Revenue Gap: What It Means and What to Do

GA4 typically reports 20 to 30 percent less revenue than your Magento backend or payment processor. This is not a tracking error. It is a structural reality of client-side tracking in an environment where iOS Safari's Intelligent Tracking Prevention blocks some GA4 scripts, ad blockers suppress tracking on a meaningful percentage of browsers, and server-side consent preferences exclude certain users from measurement entirely. Per GA4 ecommerce tracking analysis for brands, this gap is expected and does not mean your implementation is broken.

The practical implication: use your Magento backend as the source of truth for financial reporting and revenue figures that go to stakeholders. Use GA4 for relative performance trends, channel comparison, and funnel analysis. If GA4 shows that organic search revenue increased by 15% month-over-month while paid search revenue held flat, that directional finding is reliable even if the absolute numbers are understated.

For Magento merchants who need higher revenue accuracy in GA4, server-side tracking via the GA4 Measurement Protocol routes event data directly from your server to Google instead of through the browser. This bypasses most client-side blocking. It is a more complex implementation but eliminates the majority of the 20-30% gap. Any serious Magento GA4 extension with server-side GTM support can implement this.

Four GA4 Mistakes Magento Merchants Make Most Often

Tracking the Purchase Event on Page Refresh

If your Magento order success page reloads when a user navigates back to it, and the purchase event fires on every load, every refresh creates a duplicate transaction in GA4. This inflates revenue in Monetisation reports and transaction counts in the Transactions report. The official Magento GA4 documentation specifically flags this: ensure the purchase event only fires on the initial load of the success page, not on back-navigation or refresh. Use GTM's Once Per Page trigger or add a session storage check.

Reading the Purchase Journey Report as an Open Funnel

The Purchase Journey report is a closed funnel. It only shows users who moved through all five stages in a single session sequence. This means it underrepresents actual conversion rates for returning customers who may have added to cart in one session and purchased in a later one. Treat the Purchase Journey report as a guide to relative abandonment rates at each step, not as an absolute conversion rate. For absolute rates, build an open funnel in Funnel Exploration.

Leaving Data Retention at Two Months

The most commonly overlooked GA4 setting for Magento merchants is data retention. At the default two-month window, you cannot run a 90-day cohort analysis, compare conversion rates across holiday seasons, or look at year-over-year product performance in Explorations. Set it to 14 months immediately after setup. There is no cost impact: GA4 is free for standard properties.

Not Validating Item Parameters After a Magento Catalog Update

When you update your Magento product catalog, add new categories, or modify SKUs, the data layer values sent to GA4 may no longer match your intended item hierarchy. If item_category in your data layer still reflects an old category structure, your Ecommerce Purchases report filters by category will produce misleading results. Validate event parameters in DebugView after any significant catalog change, not just after the initial implementation.

Frequently Asked Questions

Here are the common questions and their answers you might have.

1. Does Magento 2.4.5+ Support GA4 Natively Without an Extension?

Magento 2.4.5 introduced a native Google Tag (GA4) integration accessible at Stores > Configuration > Sales > Google API. This handles basic tracking including page views and the purchase event. However, it does not configure the full set of Enhanced Ecommerce events (view_item_list, select_item, view_item, add_to_cart, add_to_wishlist, remove_from_cart, begin_checkout, add_shipping_info, add_payment_info) out of the box. For the complete funnel data that makes the Purchase Journey and Checkout Journey reports useful, a dedicated GA4 extension or manual GTM data layer implementation is required. Per Magento's official GA4 documentation, merchants on 2.4.5+ can use the native integration as a starting point but should validate which events are firing before relying on ecommerce reports.

2. Why Does My GA4 Revenue Not Match My Magento Sales Figures?

A 20 to 30 percent gap between GA4-reported revenue and your Magento backend is normal and expected. The gap is caused by browser-level tracking prevention in iOS Safari, ad blocker interference, and users who decline analytics cookies under GDPR consent mechanisms. GA4 is not designed to be the financial system of record. Use it for channel comparison and funnel analysis, and use your Magento order management system or payment processor for accurate revenue figures.

3. What is the Difference Between the Purchase Journey and Checkout Journey Reports in GA4?

The Purchase Journey report covers the entire funnel from session start to purchase across five steps. The Checkout Journey report shows only the steps inside the checkout process itself (shipping information, payment information, and purchase confirmation). Use the Purchase Journey report to find where in the overall buying process most users drop off. Use the Checkout Journey report to diagnose which specific checkout step is causing the most abandonment after a user has already started the checkout process.

4. How Do I Track Magento Coupon Code Performance in GA4?

GA4 captures coupon data through the coupon parameter in both the add_to_cart and purchase events. The Order Coupon report (accessible by drilling down from the Monetisation Overview) shows revenue attributed to each coupon code. For the coupon parameter to populate, your Magento GA4 integration must pass the applied coupon code as a parameter in the data layer at checkout and purchase. Validate this in DebugView: complete a test order with a coupon applied and confirm the purchase event includes the coupon parameter with the correct code value.

5. What GA4 Reports Should a Magento Merchant Check Every Week?

Start with the Monetisation Overview for the revenue trend and any anomalies. Then check the Purchase Journey report to see if funnel abandonment rates have shifted from the prior week. Finally, review the Traffic Acquisition report to see whether channel mix and revenue by channel has changed. These three reports, reviewed weekly, will surface the majority of problems and opportunities that require action. Funnel Exploration and Cohort Analysis are monthly or quarterly analyses, not weekly monitoring tools.

Where to Start: A Practical Priority Order

If you have just set up GA4 for your Magento store: fix data retention to 14 months, mark purchase as a conversion, validate that the full Enhanced Ecommerce event set is firing correctly, and let the property collect data for at least two weeks before drawing conclusions from any report.

If you have had GA4 running for a while but have not used the ecommerce reports seriously: open the Ecommerce Purchases report and sort by Item Revenue descending. Identify your top five revenue-driving products. Then open the Purchase Journey report and find which funnel step has the highest abandonment rate. Those two findings will give you one product optimization task and one checkout task to prioritize, both of which are actionable without any additional data collection.

For Magento merchants who want the full ecommerce event set without manual GTM configuration work, MageDelight's GA4 with GTM Extension installs in under 10 minutes with a single code integration and ships with a pre-built GTM template that covers all Enhanced Ecommerce events. It is a practical starting point before investing time in custom data layer work or advanced exploration reports.

The Baymard Institute's 70.19% cart abandonment rate exists because most stores do not know where in their funnel the abandonment actually happens. GA4's ecommerce reports exist to answer that question. The merchants who close that gap are the ones who check the right reports, act on what they find, and revisit the data after making changes.