A simple example
A shopper views a product, adds it to their basket and buys it. A correctly designed setup records those steps so you can investigate where other shoppers stop.
What GA4 helps you decide
A useful measurement setup connects a business question to an observable action. Where do shoppers leave the purchase journey? Which landing pages attract engaged visitors? Do new-market customers return? Start with those questions, then select events and reports. A property installed on every page is only the beginning.
What an ecommerce setup needs
Google documents ecommerce events such as view_item, add_to_cart, begin_checkout, purchase and refund. Their implementation needs appropriate parameters, including item information and transaction details. Agree how your store handles order identifiers, currency, discounts, shipping and refunds before treating reported revenue as a business total.
A practical acceptance check
- Place a test order and record its unique order identifier and expected value.
- Check the purchase event and its parameters in the debugging tools.
- Repeat after refreshing the confirmation page to look for duplicate collection.
- Test the journey under the consent choices your implementation supports.
- Compare a defined period with the store using matching revenue definitions.
What the reports cannot settle
Analytics revenue and finance revenue can differ because they describe different scopes and because collection is incomplete. An attributed purchase is not proof that advertising caused it. Keep your order system as the transaction record, and use GA4 to investigate behavior within its documented collection limits.
Turn a report into a useful investigation
Imagine product views increase while completed purchases stay flat. That observation does not identify the cause. Segment the journey by device, landing page and customer type, then check whether the pattern survives a tracking review. A mobile checkout problem and a missing mobile purchase event can produce similar-looking reports but require different actions.
A useful review ends with a decision and an owner. If collection is unreliable, repair and retest before comparing channels. If collection is sound, select a specific friction point to investigate with the store team. Keep a dated record of promotions, site releases and tracking changes so a later movement in conversion rate has context.
- Write the business question in plain language before choosing the report.
- Compare the same dates, markets and revenue definitions; keep test orders separate.
- Record the suspected cause, the supporting evidence and the next check that could disprove it.
Investigate revenue discrepancies →
Frequently asked questions
What is Google Analytics 4 used for?
Google Analytics 4 (GA4) is Google’s event-based analytics platform for websites and apps. For ecommerce, its usefulness depends on collecting reliable shopping events and agreeing what the reports should measure.
Does a page tag establish useful ecommerce tracking?
No. Agree the events, parameters and success checks first. A tag on every page can coexist with missing purchase values or duplicate events.
Which system should hold the definitive order record?
Use the business transaction system for order records. GA4 helps investigate collected behaviour; differences need a defined reconciliation rather than an assumption that one report must exactly match another.
Sources and further reading
Primary material for the concepts discussed here. Our practical checklists and illustrative examples are editorial recommendations. Source links open in a new tab.