GA4 e-commerce tracking: the basics
Here’s a question that should be easy: how much money did your organic search traffic make last month?
For a lot of stores, since Universal Analytics stopped processing data in July, the honest answer is “no idea”. GA4 is installed. Page views are coming in. But the Monetisation reports are empty, or they show revenue that doesn’t match the store’s own orders, or every sale is credited to “(direct)”.
That’s not a GA4 problem so much as a setup problem. GA4 only knows about a sale if your store tells it, in the right format, at the right moment. Get that part right and you can finally connect search work to revenue, which is the whole point of measuring it.
How GA4 thinks about e-commerce
In Universal Analytics, e-commerce was a separate feature you switched on. In GA4, it’s just events with a specific name and a specific set of details attached.
A purchase is an event called purchase. It carries:
- a transaction ID (so the same order isn’t counted twice)
- a value and a currency
- an items list: each product’s ID, name, price, quantity, and optionally brand, category and variant
If any of those are missing, the event still arrives, but the reports can’t use it properly. No currency, no revenue. No items, no product reports.
I wrote about events in general in GA4 events for beginners. E-commerce events are the same idea with stricter rules.
The events that matter
Google’s recommended e-commerce events follow the shopping journey. You don’t need all of them on day one. Here’s the order I’d care about them:
| Event | When it fires | Why it matters |
|---|---|---|
purchase |
Order confirmed | Revenue. Non-negotiable. |
begin_checkout |
Checkout started | Where people drop out before paying |
add_to_cart |
Product added to cart | Interest, by product |
view_item |
Product page viewed | Which products get seen and not bought |
view_item_list / select_item |
Collection viewed / product clicked from a list | How collections perform |
add_shipping_info / add_payment_info |
Checkout steps | Finer checkout drop-off |
refund |
Order refunded | Keeps revenue honest |
If you only get one right, make it purchase. If you get four right, make it purchase, begin_checkout, add_to_cart and view_item. That’s enough to build a simple funnel and see where it leaks.
Getting the events in
Shopify
Shopify’s Google channel app (Google & YouTube) can connect your GA4 property and send the standard e-commerce events for you, including purchases from the checkout. For most stores that’s the place to start, because the checkout is the hardest part to track yourself.
Things to watch:
- Don’t double up. If someone has also pasted a GA4 tag into the theme, or a previous app is still sending events, you’ll count purchases twice. Check the theme code and your installed apps.
- Check which events actually arrive. Don’t assume. Use the DebugView method below.
- Custom setups (Google Tag Manager, custom pixels) are possible but need someone who knows what they’re doing. Start with the official route.
WooCommerce
WooCommerce’s official Google Analytics extension supports GA4 and sends the main e-commerce events. Other plugins do the same; some do it better than others. Whichever you use:
- Make sure only one thing sends GA4 data. Your SEO plugin, a tracking plugin and a theme setting can all try to add the tag.
- Check that the purchase event fires on the thank-you page and only once. Refreshing the thank-you page shouldn’t create a second sale.
- If you use a payment gateway that sends people off-site to pay, check they come back to your thank-you page. If they don’t, the sale never gets tracked, and the referral can end up credited to the payment provider.
Checking the numbers are real
This is the bit most people skip. Do it once properly and you’ll trust the reports.
1. Watch events arrive in DebugView
In GA4, go to Admin → DebugView. Install Google’s Tag Assistant or enable debug mode, then browse your own store: view a product, add it to the cart, start checkout. You should see each event appear with its parameters. Click an event to check it has a value, a currency and an items list.
2. Place a test order
If you can, place a real low-value order (or use a test mode if your payment provider has one). Within a day it should appear in Reports → Monetisation → Ecommerce purchases.
3. Compare with the store
Pick a week. Compare GA4’s purchase count and revenue with your store’s own order report.
They won’t match exactly, and that’s normal. Ad blockers, cookie consent, and people who never return from the payment page all mean GA4 sees fewer orders than you actually took. What you’re looking for is a gap that’s consistent and explainable. If GA4 shows twice as many orders as the store, something is firing twice. If it shows a tenth, something is missing.
4. Check the currency
Stores selling in naira, pounds or dollars need the currency on every event, and it needs to match the reporting currency in GA4’s property settings (GA4 converts if it knows the source currency). A missing currency is one of the most common reasons revenue shows as zero.
The reports to use once it works
- Monetisation → Ecommerce purchases: revenue and units by product.
- Acquisition → Traffic acquisition: add revenue as a column and look at the Organic Search row. That’s your answer to the question at the top.
- Explore → Funnel exploration: build a funnel from
view_itemtoadd_to_carttobegin_checkouttopurchaseand see where people drop out. - Landing page report with revenue: which pages people arrive on before they buy. This is where SEO and sales finally meet.
That last one is how you stop treating rankings as the goal. If a product guide brings in visits but never leads to a sale, and a boring collection page quietly makes money, that changes what you work on next. I wrote more about that in rankings aren’t revenue.
Common mistakes
- Two tags, double the sales. The most common one by far.
- Purchases attributed to the payment provider. Add payment domains to the referral exclusion list (Admin → Data streams → Configure tag settings → List unwanted referrals).
- No transaction ID. Without it, GA4 can’t spot duplicates.
- Testing on the live property with no filter. Your own test orders end up in the data. Define your internal traffic and filter it.
- Never checking again. A new app, a theme update or a checkout change can break tracking silently. Check DebugView after any big change.
Related reading
- GA4 events for beginners: what to track first
- GA4 vs Universal Analytics: the differences that matter
- Universal Analytics has stopped: what to do with your old data
- Rankings aren’t revenue: setting SEO goals a business cares about
Open your store’s order report and GA4 side by side for last week. Do the purchase counts land roughly together? If not, that’s the first job, before any keyword research.