GA4 ecommerce events: what a correct implementation should send.
Google Analytics 4 (GA4) can only report what it is sent. This guide sets out the events an online shop normally sends, what each parameter should contain, a complete purchase example, and how to prove the data arrives correctly. It follows Google's own ecommerce documentation.
Core GA4 ecommerce events
Google's ecommerce guide describes a set of recommended events. A typical shop sends these:
| Shopper action | GA4 event |
|---|---|
| Sees a list of products | view_item_list |
| Clicks a product in a list | select_item |
| Views a product page | view_item |
| Adds to basket | add_to_cart |
| Removes from basket | remove_from_cart |
| Views the basket | view_cart |
| Starts checkout | begin_checkout |
| Submits delivery details | add_shipping_info |
| Submits payment details | add_payment_info |
| Completes an order | purchase |
| Gets a refund | refund |
Use these exact names. A custom name such as order_complete won't populate GA4's ecommerce reports.
Parameter mapping
Most ecommerce events carry the same building blocks:
| Parameter | What it should contain | Typical source |
|---|---|---|
currency |
ISO 4217 code, for example GBP |
Store or order currency |
value |
The event's monetary value | Sum of item price times quantity |
items |
Array of products | Basket or order lines |
transaction_id |
Unique order identifier (purchase, refund) |
Order number or ID |
shipping, tax |
Shipping cost and tax (purchase) |
Order totals |
coupon |
Code used, if any | Order discount codes |
On Shopify, standard customer events supply this data. For example, the checkout_completed event carries the checkout and order details a custom pixel can map to GA4's purchase. On WooCommerce, the source depends on the plugin or the code on the order received page.
Purchase example
An illustrative purchase event with invented data, in the gtag.js format Google's guide uses:
gtag('event', 'purchase', {
transaction_id: '1001',
value: 70.00,
tax: 14.00,
shipping: 4.95,
currency: 'GBP',
coupon: 'WELCOME10',
items: [
{
item_id: 'SKU-TEE-BLK-M',
item_name: 'Organic tee',
item_variant: 'Black / M',
price: 25.00,
discount: 2.50,
quantity: 2
},
{
item_id: 'SKU-CAP-NVY',
item_name: 'Canvas cap',
price: 20.00,
quantity: 1
}
]
});
Here value is (25.00 × 2) + (20.00 × 1) = 70.00. With Google Tag Manager, the same data is usually pushed to the data layer as an ecommerce object with a purchase event, and a GA4 event tag reads it.
Transaction ID
Google's help on duplicate key events says GA4 deduplicates purchase events that share the same transaction ID. That makes the ID important twice over:
- It must be unique per order. If every purchase sends the same ID, GA4 will treat later orders as duplicates and undercount.
- It must never be empty. Google's help warns that GA4 deduplicates all purchases sent with
transaction_id="". - It must not contain personal data, such as an email address.
Use the order number or order ID, consistently, everywhere the purchase is sent.
Currency and value
- Google's event reference says to set
valueto the sum of price times quantity for all items, and not to include shipping or tax. Send those inshippingandtax. currencyis required whenever you sendvalue. Without it, revenue metrics can't be computed accurately.- Send numbers, not formatted strings.
70.00is right;"£70.00"is not. - If you sell in several currencies, send the currency of the order, and let GA4 convert.
Item arrays
- Each item needs
item_idoritem_name. Google's reference requires one of the two. priceis the unit price. The reference says that if a discount applies,priceshould be the discounted unit price, with the unit discount indiscount.- Keep
item_idconsistent across events and with your product feed, so product reports join up. - Variants belong in
item_variant, or in the ID if each variant has its own SKU.
Duplicate prevention
Most double-counted revenue comes from one of these:
- Two tags sending
purchase, for example a platform app and a tag manager tag. See duplicate GA4 tags. - The confirmation page firing again on reload or revisit.
- Two GA4 measurement IDs, each receiving the order. See multiple GA4 IDs.
A consistent, unique transaction_id lets GA4 deduplicate repeats of the same order. It doesn't fix two tags sending different IDs for the same order. See duplicate purchase events.
Debugging
- Use DebugView. Turn on debug mode with Tag Assistant or the GTM preview, then watch events in GA4's DebugView. Open each event to read its parameters and items.
- Read the network request. Filter the Network tab for
collect?v=2. Each request shows the event name (en=) and, for ecommerce events, the parameters. Count how manypurchaserequests one order produces. - Compare with the order. Check transaction ID, value, currency and each item against the order in your store admin.
- Wait, then check reports. Standard reports take time to process. Use Realtime and DebugView for same-day testing.
On Shopify, Google tags loaded inside a custom pixel aren't visible to Tag Assistant's troubleshooting, according to Shopify's help. Test those with DebugView and a test order.
Validation checklist
- [ ] Event names match Google's recommended names exactly.
- [ ] One
purchaseper order, including after a page reload. - [ ]
transaction_idis unique, non-empty and matches the order. - [ ]
valueequals the sum of item price times quantity, without shipping or tax. - [ ]
currencyis present on every event that hasvalue. - [ ] Every item has
item_idoritem_name, pluspriceandquantity. - [ ] Discounted items show the discounted
priceand thediscount. - [ ]
item_idmatches the product feed. - [ ] Behaviour with consent declined matches your consent policy.
For a Shopify-specific version, use our Shopify tracking checklist. If GA4 revenue still doesn't match your store, read why GA4 revenue doesn't match. Some difference is normal; consent choices alone mean GA4 won't see every order.
When you'd like evidence rather than a checklist, our GA4 and GTM audit checks every event, parameter and tag on one store and documents the findings.
Sources
- Google for Developers: Measure ecommerce
- Google for Developers: Recommended events reference
- Google Analytics Help: Minimize duplicate key events with transaction IDs
- Google Analytics Help: Monitor events in DebugView
- Shopify developer docs: checkout_completed event
Last checked against official documentation: 18 November 2026.
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.