What purchase revenue measures
Purchase revenue counts one thing: the value sent with events named purchase. Every time a customer completes an order and your site fires that event with a value attached, the amount is added to this metric. Nothing else contributes to it.
That narrowness is the point. GA4 also reports a broader total revenue figure, which folds in subscription income and in-app advertising income alongside orders. For a shop that sells nothing but products, the two look identical and people use the names interchangeably. For a publisher, an app or a membership site they are different numbers, and quoting the wrong one in a report is an easy mistake to make.
The value itself comes from your own code. Whatever amount the website attaches to the purchase — with or without tax, shipping and discounts — becomes purchase revenue, so the metric is only as honest as the ecommerce tracking underneath it.
Why purchase revenue matters
It is the cleanest link between marketing and sales. Because it excludes other income streams, you can attribute it to channels, campaigns and landing pages and be confident you are looking at product orders rather than a mixture. Return on ad spend calculated on purchase revenue answers a question a business owner actually asked.
It is also the value most often exported onwards. Import it into Google Ads or Meta and the bidding systems will chase it, so the definition you chose when the tracking was built quietly becomes the goal your advertising optimises towards for as long as it runs.
Where purchase revenue goes wrong
The commonest fault is a purchase event that fires without a value, or with the value passed as text rather than a number. The order is counted, the revenue is not, and the shop appears to be selling nothing while the transaction count climbs.
The second is scope creep in the other direction. A site that fires purchase for a free trial sign-up, a quote request or a cash-on-delivery order that has not yet been paid inflates the metric with things nobody has been paid for. Cash on delivery deserves particular thought in Nepal, where a meaningful share of orders is settled at the door and some are never collected at all.
Duplicates are the third. A confirmation page that reloads and fires again adds the same order twice unless a stable transaction ID lets GA4 recognise it.
How to act on it
Place a test order and read the event in preview mode before it reaches a report. Check three things: the event is named purchase, the value is a plain number in the currency you expect, and the transaction ID is present and unique.
Then decide what a purchase means for your business and hold the line on it. If unpaid cash-on-delivery orders should not count as revenue until collected, either delay the event or send a refund event when an order fails. Finally, compare purchase revenue with total revenue in GA4 once. If they differ and you do not sell subscriptions or app advertising, something is firing that should not be, and that is worth tracing before any report is built on top of it.