Item Revenue
What each product earned in GA4, before tax and shipping go anywhere near it.
What it means
Item Revenue is the total revenue from items only, excluding tax and shipping. It's GA4's figure, recorded against the items on purchase events, so it counts what the site's tracking saw rather than what the shop billed. It's the default sort on the Products table — the same column whether you're looking at item name, variant or category — so the first row you see is your biggest earner by this measure.
Show the math
Formula and a worked example
Item Revenue = what the items on purchase events were worth, with tax and shipping stripped out. Divide it by the units beside it and you get the average unit price — the app does exactly that in the next column along.
Worked example. A jacket takes 300 Items Purchased and shows €18,000 of Item Revenue. Working back, 18,000 ÷ 300 = €60 a unit. Next month the row reads €18,000 again on 360 units: 18,000 ÷ 360 = €50 a unit. The revenue column didn't move and the price fell 17%.
That's the whole reason this column is never read alone. A flat euro figure hides a price cut, a mix shift and a discount campaign equally well.
It answers the question
Which products earned the most, and at what price per unit? Sorting the catalogue by anything else puts your attention on products that can't repay it.
Why it matters
Everything else on the Products row is a rate — cart rate, purchase rate, unit price. Item Revenue is the only column that says whether any of them matter. A 12% cart rate on a product earning €400 a month is a statistic; the same rate on the row above it is a plan for next quarter.
It's also the honest ranking. Sort the catalogue by views and by Item Revenue and the two orders rarely match: the products high on attention and low on revenue are being promoted past their ability to sell, and that gap is the cheapest thing on this page to fix.
What good looks like
There's no universal figure — it's a euro total per product, so it scales with your traffic, your prices and how many products you stock. Judge each row against its own last 30 days, and always beside Items PurchasedItems PurchasedItems Purchased: the number of units purchased across all purchase events, because that pair is what separates a price move from a volume move. The comparison that pays most is internal: rank by Item Revenue, then by Items ViewedItems ViewedItems Viewed: the number of times item details were viewed, and act where the two rankings disagree hardest.
How to improve it
| Lever | What you do | Expect | How long | Watch out for |
|---|---|---|---|---|
| Fast Find the rows where unit price has drifted | Divide Item Revenue by Items Purchased down the table and flag the products whose price fell without a decision behind it | Revenue recovers on the same units | 1–2 weeks | Putting a price back costs conversion first. The same views produce fewer purchases for a few weeks before the extra price catches up. |
| Fast Point traffic at the products that convert | Link campaigns and the top row of collections to the items with the strongest purchase rate, not the newest ones | More revenue on the same sessions | 1 week | Discovery narrows. The rest of the range gets fewer views and new products never build the history they need to earn a place at the top. |
| Slow Fix the templates that under-report | Check the purchase event fires with item data on bundle, subscription and configurator pages | Products that were selling stop reading as zero | 3–6 weeks | Developer time, and the fix breaks your history — every period-on-period comparison spanning it will show growth that didn't happen. |
| Slow Add a tier above your bestseller | Build a higher-priced version of the product that already sells well | Average unit price rises, revenue with it | 1–2 quarters | Stock and photography cost real money up front, and a premium tier usually takes sales from the mid-price product rather than adding new ones. |
Every lever costs something somewhere. The last column is the one to read twice.
Read it with
Euros and units sit next to each other on every row. Reading one without the other is how a price cut gets mistaken for a good month.
Genuine growth
More units at prices that held. The only thing that stops this product now is running out of it.
Fewer, dearer sales
Revenue grew on falling units. A deliberate price rise looks identical here to your cheapest variant selling out.
Selling more for less
Units up and euros down means the price per unit fell. Sometimes the right trade, never an accident worth leaving in place.
Losing the product
Both halves down. A product genuinely fading and a tracking change on its template produce exactly this shape.
Divide one by the other and you have the average unit price, which the app shows in the next column. It's the only way to read a flat revenue row correctly — the same €18,000 on more units is a price cut nobody signed off, and neither column shows it alone.
Size against efficiency. A product earning well on a weak purchase rate is being carried by traffic and will stop the moment you stop sending it; one earning little on a strong rate is starved of attention. The pair decides which row gets your next hour.
Common misreads
It won't. Tax and shipping are excluded here, and GA4 counts what the site's tracking recorded rather than what the shop billed. Read Gross SalesGross SalesRevenue before discounts; compare with Product Revenue for markdown cost. when you need the shop's own figure.
Divide by units before you decide. Steady revenue on rising units is a falling price, and it's the most common way a product quietly stops being worth stocking.
It's your biggest earner, which isn't the same thing. No product cost appears anywhere on this table, so the row carrying the most revenue can be the one carrying the least profit.
Also called
Product revenue · item sales · revenue from items
See yoursYour catalogue ranked by Item Revenue, with units, unit price and the view-to-purchase rates on the same row.
Open Google Analytics Products →