What is GA4 purchase event?
The GA4 purchase event is the ecommerce event Google Analytics 4 uses to record a completed order, carrying the order value, the currency, a transaction id and the list of items bought.
Worked example, not a result
What one purchase event should carry
Say a customer buys two of the same item at 88.25 each. The purchase event should report a value of 176.50, a currency code, and a transaction id that matches the order number in the store admin.
The items array is the part most often left thin. It should carry each item's id, its name, its price and the quantity, and ideally the category and any variant. Without it, the reports can tell you how much money arrived and nothing at all about which products earned it, which removes most of the reason to have analytics on a store.
The transaction id does quiet but important work. It is what stops the same order being counted twice when a customer refreshes the confirmation page or returns to it from an email, which is one of the most common causes of analytics revenue drifting above the real figure.
The numbers here are an example.
Why it matters
The purchase event is the anchor for everything a store measures. Conversion rate, revenue by channel, product performance and the effectiveness of every campaign are all derived from it, so an event with the wrong value or a missing items array quietly corrupts every report built on top of it.
It also feeds decisions across all four levers. Channel level revenue tells you where visitors are worth buying. Product level revenue tells you which pages deserve conversion work. Order value trends show whether bundles and thresholds are doing anything. Returning customer revenue shows whether the repeat purchase work is landing.
For a store owner the useful check is simple and takes an afternoon. Compare a week of analytics revenue against the store admin, then compare the order count. If either is out by more than a small margin, fix that before drawing any conclusion from a dashboard.
Common mistakes
- Sending the event more than once for the same order. A confirmation page that fires on every view inflates revenue, and only a consistent transaction id prevents it.
- Including tax and shipping in the value without deciding to. Whatever the store chooses has to be applied everywhere, or channel comparisons stop meaning anything.
- Leaving the items array empty. Revenue with no product detail cannot answer which products or categories are worth more traffic.
- Never reconciling against the store admin. Analytics revenue and banked revenue always differ a little, and the size of the gap is the number worth knowing before you trust a report.
Related terms and answers
Your plan is free.
A person reads it. You keep the plan. No logins, no call first.