Purchase Event

In GA4, the purchase event records a completed transaction. It carries the order value, the currency, a unique transaction_id, and item-scoped parameters for each product bought. It is the single source of your revenue, transaction count, and average purchase revenue.

Why it matters

Almost every monetary metric in GA4 traces back to this one event. If the purchase event fires correctly, your revenue reporting is trustworthy and you can reason confidently about what's selling. If it fires wrong — twice, never, or with a missing value — every downstream number inherits the error. It's the most important event to get right and the easiest to break.

A concrete example

Say a small store moves its order confirmation to a new page. The next week, GA4 shows revenue down 30% while the bank says sales are flat. The cause: the purchase event was tied to the old confirmation page and no longer fires on the new one. No money was lost — the event simply stopped recording it. The drop was a tracking failure wearing the costume of a sales problem.

The common misreading

The mistake is trusting purchase revenue without a transaction_id. That unique ID is what lets GA4 deduplicate orders. Without it, a customer who refreshes the confirmation page can fire two purchase events and inflate your revenue. Inflated and undercounted numbers both look plausible — which is why GA4 revenue should always be reconciled against your store platform before you act on it.