Transactions

In GA4, transactions is the count of completed purchase events over a period — simply, the number of orders. It's one of the most grounded numbers in your reports: each transaction is a real customer who finished buying, which makes it the anchor for the rest of your monetisation metrics.

Why it matters

Revenue and average purchase revenue only make sense once you know how many orders produced them. A revenue jump driven by more transactions is healthy growth; the same jump from a single large order is volatile and may not repeat. Transaction count tells you which of those you're looking at. It also catches tracking breakage fast — orders rarely drop to zero in real life.

A concrete example

Say a small store sees revenue hold steady month over month and assumes nothing changed. But transactions fell from 200 to 140, while average order value rose to compensate. Fewer customers are spending more — a fragile pattern that looks stable on the topline. The transaction count exposes the shift the revenue figure hides.

The common misreading

The mistake is conflating transactions with items sold. One transaction can contain ten products; ten transactions can each contain one. If you want to understand product movement, read transactions next to item quantity, not in place of it. And a sudden transaction drop usually means a broken purchase event before it means a sales collapse — check the tracking first.