What revenue measures
In an analytics tool, revenue is simply the sum of the value your website sent with each completed order. It is not read from your bank, your accounting software or your shop’s own admin screen. Someone decided, when the tracking was built, which figure to attach to the purchase event, and that decision is what every revenue report afterwards repeats.
In GA4 the headline total revenue metric adds together purchase revenue, subscription revenue and advertising revenue, which is why it can differ from purchase revenue on the same screen. Alongside it sits a currency: values are recorded in the currency you declare on the event and displayed in the property’s reporting currency, converted at the rate held for that day.
Why revenue matters
Revenue is the metric that turns marketing activity into a business conversation. Sessions and clicks describe traffic; revenue describes outcome. It is also the input for almost every commercial calculation you will make afterwards — return on ad spend, average order value, revenue by channel, revenue by product — so an error here spreads into all of them at once.
It matters even more once automated bidding is involved. When purchase values are imported into Google Ads or Meta, the platforms optimise towards the numbers you supply. Whatever your tracking calls revenue becomes the definition of success that the machine learns to chase, whether or not it matches the money in the account.
Where revenue reporting goes wrong
The first problem is scope. Gross order value, value after discount, value excluding tax and shipping and value after refunds are four different figures, and a shop that reports one while the finance team uses another will never reconcile. Deciding which one you mean, writing it down, and keeping it stable matters more than which you choose.
The second is mechanical. A purchase counted twice, an order fired without a value, a missing currency code on a multi-currency store, or refunds that are never sent back to analytics will each move the total on their own. In Nepal there is a further wrinkle: shops selling in more than one currency, or taking cash on delivery, often record a sale at checkout that the business only treats as revenue once the money is collected.
How to act on it
Write a one-line definition of revenue for the business and apply it everywhere — website tracking, ad platforms and reports. Then test it: place a real order with tax, shipping and a discount code applied and check that the value recorded is the one your definition says it should be.
After that, reconcile. Compare analytics revenue against the shop’s own order export for the same period and the same time zone, monthly at least. You are not looking for an exact match, because attribution windows and cancellations will always create a gap; you are looking for a gap that stays roughly the same size. A gap that suddenly widens is a tracking fault, and finding it early is far cheaper than explaining it later. If the numbers have drifted and nobody can say why, a proper analytics and tracking review is the sensible next step.