E-commerce Analytics With GA4: Track What Matters

Good ecommerce analytics answers a few practical questions: where do visitors come from, which products and pages lead to sales, where do shoppers drop out of the buying process, and did the last change make things better or worse? Google Analytics 4 (GA4) can answer them, but only if it is set up properly, with the right events, accurate revenue and correct handling of consent. Many stores have analytics installed but cannot trust the numbers. Fixing the setup first, then focusing on a small set of useful reports, turns analytics from a dashboard nobody reads into a tool for decisions.

Why store owners need reliable analytics

Every decision about marketing spend, site changes and product range is easier with good data. Without it, owners guess: which advert works, why sales dipped, whether the new checkout helped. Reliable analytics lets you:

• Spend more on channels that bring profitable customers and less on those that do not.
• Find the step where most shoppers give up, and fix it.
• See which products attract interest but rarely sell, which may point to price, photos or descriptions.
• Compare mobile and desktop performance.
• Measure the effect of changes instead of relying on opinions.

It also protects you from expensive mistakes. A redesign that looks better but quietly lowers conversion, or a campaign that brings plenty of visitors who never buy, can run for months unnoticed without proper measurement.

Analytics complements, rather than replaces, your store's own order reports. The store knows exactly what sold; analytics explains how shoppers got there.

The e-commerce events that matter

GA4 records activity as events. For online stores, Google defines a set of recommended e-commerce events, described in its e-commerce measurement guide. Using the standard names unlocks GA4's built-in e-commerce reports.

Not every store needs every event on day one. If resources are limited, start with view_item, add_to_cart, begin_checkout and purchase, which together give you the core funnel. Add list, shipping and payment events afterwards to see the detail.

Each event should include item details such as product ID, name, category, price and quantity. The purchase event needs a unique transaction ID, revenue, tax, shipping and currency.

Setting up ecommerce analytics in GA4

1. Use your platform's integration or a well-maintained extension, or implement events through a tag manager with your developer.
2. Send events with item details on product lists, product pages, cart and checkout.
3. Send the purchase event once, with a unique transaction ID, so reloading the confirmation page does not double-count revenue.
4. Send refunds so revenue reflects returns.
5. Set up consent settings so tags respect visitors' choices.
6. Link Google Ads and Search Console if you use them.
7. Exclude internal traffic and test orders from your team.
8. Test everything using GA4's debugging tools before relying on the data.

Check the totals

Do this check monthly, not just at setup. Tracking breaks quietly, and a regular comparison catches problems within weeks rather than months. Compare revenue and order counts in GA4 with your store's reports for the same period. They will rarely match exactly, because of consent choices, ad blockers and time-zone differences, but they should be close. A large gap usually means a tracking problem.

Consent and privacy

In many countries, analytics and advertising cookies need visitors' consent. Your cookie banner and analytics setup must work together, so tags follow each visitor's choice. Google's consent mode lets tags adjust their behaviour based on consent, and is required for some advertising features in certain regions. Review your setup with your privacy policy and local rules in mind; our guide to GDPR for online stores covers the European side.

Collect only what you need. Do not send personal information such as names or email addresses to analytics. Remember that consent choices mean analytics will never see every visitor, so treat its figures as a reliable guide to trends and proportions rather than an exact count.

The reports worth watching

Traffic and acquisition

Which channels bring visitors and, more importantly, purchases and revenue: organic search, paid search, social, email, referrals and direct visits. Tag your email and social links consistently so their traffic is attributed correctly, rather than appearing as direct visits.

Purchase funnel

How many shoppers move from product view to cart, checkout and purchase, and where they drop out. Split by device to spot mobile problems. Our guide on how to reduce cart abandonment explains what to do with what you find.

Product performance

Which products are viewed, added to cart and bought. Products with many views but few purchases deserve a closer look at price, photos and descriptions.

Landing pages

Which pages bring visitors in and how well they convert, useful for SEO and advertising decisions. A landing page with plenty of visitors but few purchases is often the quickest place to find improvements, because it already has the traffic.

Devices and locations

Conversion by device and country helps prioritise design work and international plans. If one country converts much worse than others, check delivery costs, payment methods and language for that market before assuming customers there are simply less interested.

Common tracking mistakes

• Duplicate purchases from confirmation pages that fire the purchase event on every reload.
• Missing revenue when payments complete on an external page and shoppers never return to the confirmation page.
• Broken events after theme or checkout updates.
• Wrong currency or tax settings, inflating or deflating revenue.
• Test orders counted as real sales.
• Consent misconfiguration, either tracking without consent or blocking all tracking even when visitors agree.
• Too many custom events with inconsistent names, which make reports hard to use.

Many of these mistakes stay hidden for months because nobody checks. Put a quick test purchase and a look at the real-time report on the checklist for every release that touches the theme, checkout or payment methods.

Keep a short tracking document listing the events you send and where they fire, and check it after every significant change to the store.

Turning data into decisions

Reports are only useful if they lead to action. A simple habit helps: for every report you check, ask "what will we do differently because of this?"

Example: mobile checkout drop-off

The funnel shows that mobile shoppers reach checkout as often as desktop shoppers, but far fewer complete payment. That points to a mobile checkout problem. You test the checkout on several phones, find that the payment form is awkward on small screens, fix it, and compare the mobile funnel over the following weeks.

Example: a channel that looks expensive

A paid social campaign shows few direct purchases. Before cutting it, you check whether visitors from that campaign come back later through search or email and buy. If they do, the campaign may be valuable as a discovery channel, even if it rarely closes the sale itself.

Example: a product with many views

A product attracts plenty of views but few add-to-carts. You compare its price with competitors, improve its photos and answer the questions customers ask about it in the description. Add-to-cart rate rises over the following month.

In each case, the data points to a question; the answer comes from looking closely at the store, the product and the customer experience behind the numbers on the screen.

Beyond GA4: other data worth combining

• Your store's reports: the most accurate record of orders, revenue, margins and returns.
• Google Search Console: which searches bring visitors and how your pages rank.
• Advertising platforms: spend and results per campaign.
• Email platform: revenue from campaigns and automated flows.
• Customer service: common questions and complaints, which explain many patterns in the numbers.
• Session recordings and heatmaps: where they comply with your privacy obligations, they show how real people use your pages.

Combining sources gives a fuller picture. Analytics shows what happened; customers and recordings often explain why.

Dashboards for different people

Different people need different views. The owner may want a weekly summary of revenue, orders, conversion rate and the top channels. The marketing team needs campaign and channel detail. The merchandising team needs product and category performance. Customer service benefits from seeing which pages lead to the most contact. Build a small dashboard for each group with only the measures they act on, rather than one huge report nobody reads. Our guide to e-commerce SEO explains which search measures belong in a marketing dashboard.

Frequently asked questions

Not sure your analytics can be trusted? Ask us for a tracking audit. We will check your GA4 setup, fix broken events and help you focus on the reports that matter.