Google retired Universal Analytics and made GA4 the default from July 2023. Three years on, the most common GA4 ecommerce tracking setup we see in small ecommerce is the default platform integration, untouched, with half the event chain missing and the owner quietly distrusting every number. This guide covers what to wire, what to check and which discrepancies to stop worrying about.
This is the analytics pillar. Attribution and server-side tracking each get their own deep dive.
GA4 ecommerce reporting is built from a small chain of events. If one link is missing or fires without item data, every report downstream degrades.
| Event | Fires when | Why it matters |
|---|---|---|
| view_item | Product page viewed | Top of the product funnel |
| add_to_cart | Item carted | First commitment signal |
| begin_checkout | Checkout started | The cart-to-checkout leak point |
| add_payment_info | Payment details entered | Late-stage abandonment marker |
| purchase | Order completed | Revenue, conversion, ROAS, everything |
Two more worth adding once the chain is clean: view_item_list with item list names (which collections actually sell) and add_shipping_info (where shipping shock bites).
The payment-gateway referral exclusion is the single most common silent error. A store using an external payment redirect can show its biggest "channel" as the gateway domain, which means paid and organic are both being under-credited.
The discrepancy question consumes more owner anxiety than any other analytics topic. The platforms count differently by design:
A gap where GA4 shows fewer orders than the platform is normal. The platform is your source of truth for revenue. GA4 is your source of truth for behaviour and channel mix. Worked example of when to care: a stable gap that suddenly widens after a theme update usually means the purchase event broke. The gap's trend is the alarm, not its existence. If the gap is severe, the fix is usually server-side tracking, covered in its own guide.
Four GA4 reports cover most operating questions for a small store:
If checking these weekly feels like admin, that's the problem automated reporting exists to solve.
Different counting methods. Shopify records orders server-side, GA4 depends on a browser event that blockers, consent and script failures can suppress. A stable gap is normal. A suddenly widening gap means something broke.
view_item, add_to_cart, begin_checkout, add_payment_info and purchase, all carrying item data. Add view_item_list and add_shipping_info once those are clean.
GA4 client-side is enough for behaviour and channel reporting. Server-side tracking matters most for ad platform conversion feeds, covered in the server-side tracking guide.
Qwrki is the operating layer that runs retainer delivery for small businesses, and analytics is part of that cycle: we wire the GA4 event chain once, validate it, then read the four reports for you each week so the numbers stay trustworthy. We treat your store platform as the source of truth for revenue and GA4 as the source of truth for behaviour, so the discrepancy stops being a worry. Book a call if your purchase event looks shaky or your channel mix never quite adds up.
First click, last click, data-driven: every attribution model is wrong differently. A practical measurement stack for small ecommerce that still makes good decisions.
Server-side tracking and the Conversions API in plain English: what signal it recovers, what it can't, the real costs, and who actually needs it.
The twelve ecommerce KPIs that matter, organised in three tiers: weekly operating numbers, monthly health checks and quarterly strategy metrics.
