How the purchase event works
This is the event that records a completed order, and it is the one every other ecommerce number depends on. It fires once the order is confirmed — normally on the thank-you page — and it must carry a unique transaction ID, the order value, the currency, and the items bought with their identifiers, names, prices and quantities. Tax and delivery can be sent as their own fields so the goods value stays comparable across events.
Two things decide whether it is trustworthy. First, it must fire exactly once per order: the transaction ID is what lets GA4 discard a repeat if the shopper refreshes the confirmation page. Second, the value must be a plain number in a consistent currency, with no symbols, no thousands separators and no formatting a spreadsheet would add.
Why the purchase event matters
Revenue, return on ad spend, average order value, product performance and every channel comparison in GA4 are built from this one event. If it is wrong, nothing above it can be right, and the errors are rarely obvious — a shop with a broken purchase event does not show zero revenue, it shows a plausible figure that is quietly too high or too low.
It also feeds the ad platforms. Google Ads and Meta bidding both learn from purchases, so a purchase event that misses orders starves the bidding of examples and one that duplicates them teaches the system that traffic is more profitable than it is. Fixing the measurement usually improves the advertising without any change to the campaigns themselves.
Common mistakes with the purchase event
Duplicates lead the list. The confirmation page is bookmarked, refreshed, revisited from an email, or reached again through the browser’s back button, and without a stable transaction ID every visit is another order. A related version is the payment gateway redirect: the shopper returns from the gateway, the page loads twice, and the order is counted twice.
The other frequent fault is a value that does not match the shop’s own books, because delivery or tax has been folded into the goods total on some orders and not others, or because a currency conversion happens on the page. And then there is the silent failure — an order placed by phone, by message or over the counter never touches the website, so it never appears here at all. That is not a bug, but you have to remember it when you compare GA4 with your accounts.
How to act on it
Reconcile before you interpret. Take a period, put the order count and revenue from your shop platform next to the same figures in GA4, and find out where the difference comes from. A small gap from consent choices and blocked scripts is expected; a large gap means the event is wrong.
Then place a real test order, refresh the confirmation page, and check in DebugView that the second visit does not create a second purchase. Do the same on a phone and through your payment gateway’s redirect. If the numbers still disagree after that, server-side sending is usually the durable fix, and it is standard scope in a GA4 and ecommerce tracking setup rather than something to patch tag by tag.
