Ecommerce Analytics & Tracking: Measure the Customer Journey From Product View to Purchase

Ecommerce analytics is useful only when the numbers describe what customers actually did. A dashboard can look sophisticated while purchase events are duplicated, product IDs are inconsistent or revenue is missing. The foundation is not reporting. It is trustworthy measurement.

This is Cluster 20—the final planned page in Desa Digit's ecommerce authority cluster. It connects analytics to the Ecommerce Website Design Washington pillar, Conversion Rate Optimization, Abandoned Cart Optimization, Customer Retention, Email Marketing and Ecommerce SEO Washington.

What Should an Ecommerce Store Measure?

Google states that ecommerce-specific interactions such as product views, cart additions and purchases are not sent by Google Analytics automatically in a generic implementation; ecommerce events need to be implemented. Once those events are sent correctly, Analytics can populate ecommerce dimensions, metrics and reports.

“If the event is wrong, the dashboard is confidently wrong.”Desa Digit measurement principle

The Core GA4 Ecommerce Events

Google's current ecommerce documentation describes a recommended event model that can measure product-list views and selections, product detail views, cart activity, checkout, shipping and payment information, purchases, refunds and promotions.

Purchase Tracking Has to Be Correct

The purchase event is one of the most consequential events in the entire analytics implementation. Google recommends sending transaction context such as transaction ID, currency, value and an items array. When value is sent, Google specifically recommends setting currency at the event level.

Prevent duplicate purchases

A confirmation page that fires again on refresh can distort revenue. Transaction IDs are important for purchase identification and duplicate-event control. Test reloads, browser back/forward behavior and payment redirects.

Validate Before You Analyze

Google recommends using debug mode and DebugView to validate ecommerce events in real time. Its validation documentation identifies issues such as syntax problems, incorrect event names and duplicate transaction IDs as common reasons implementations fail.

1. Open DebugView.
2. View a product.
3. Add it to cart.
4. Begin checkout.
5. Enter shipping/payment information.
6. Complete a test order.
7. Confirm event names and parameters.
8. Verify the transaction and revenue against the commerce platform.
9. Test refunds if the store sends refund events.

Build an Ecommerce Funnel

Google's current GA4 setup guidance recommends checkout events including begin_checkout → add_shipping_info → add_payment_info → purchase, with product and cart events useful earlier in the journey. GA4 explorations can then be used to investigate where users abandon the checkout process.

Measure Product Performance

Google's Ecommerce purchases report can show item-level information including item revenue, items viewed, items added to cart and items purchased when the required ecommerce data is sent correctly.

• Which products receive many views but few cart additions?
• Which products are added to cart but rarely purchased?
• Which categories generate the most item revenue?
• Which products have unusually high refund rates?
• Which promotions or placements influence product interaction?

Understand Event-Scoped vs. Item-Scoped Metrics

GA4 distinguishes event-scoped ecommerce metrics from item-scoped metrics. For example, one add-to-cart event containing multiple units can count as one event while the item-level metric records the number of items added. Understanding scope prevents misleading product analysis.

Acquisition and Attribution

Do not evaluate an ecommerce channel only by sessions. Compare the traffic source with product engagement, checkout behavior, purchases, revenue, repeat behavior and—where your data supports it—customer value.

UTM discipline

Use documented naming conventions for campaign parameters. Inconsistent capitalization and naming fragment reports and make channel comparisons harder.

Google Search Console + Ecommerce Analytics

Search Console's Performance reporting provides search visibility and interaction data such as impressions and clicks. Google explains that an impression represents a link to the site being shown in Google under the rules for the relevant search-result type.

Use Search Console to understand how organic search discovers the store, and GA4/commerce data to understand what happens after the visit. These systems answer different questions and their numbers should not be expected to match exactly.

Shopify and WooCommerce Analytics

Shopify

Google's current GA4 documentation notes that when Analytics is set up on Shopify, some ecommerce events—including add_to_cart, begin_checkout and purchase—can be collected for you. Merchants should still validate the implementation and confirm that reporting matches store transactions.

WooCommerce

WooCommerce tracking commonly depends on the analytics extension, theme, checkout architecture, consent system and tag implementation. Plugin installation is not validation. Complete test transactions after meaningful tracking, checkout or theme changes.

Build a Dashboard Around Decisions

A useful executive dashboard should be smaller than the underlying dataset. Choose KPIs that answer recurring business questions.

Common Ecommerce Analytics Mistakes

• Assuming GA4 automatically tracks every ecommerce interaction.
• Installing a plugin and never validating the data.
• Counting duplicate purchase events.
• Sending revenue without currency.
• Changing product IDs between events or platforms.
• Mixing event-scoped and item-scoped metrics incorrectly.
• Comparing attribution numbers across platforms as though they use identical rules.
• Building dashboards before defining the business questions.
• Ignoring refunds when discussing revenue quality.
• Collecting dozens of custom events nobody uses.

The 50-Point Ecommerce Analytics & Tracking Audit