How to Quantify Revenue Loss From Funnel Drop-Offs in GA4
Most funnel analysis stops at percentages. "We lose 62% of users between cart and checkout." That's a useful diagnostic but it's not a number anyone can make a budget decision with.
The question your team actually needs answered is: what is that drop-off worth in rupees, and how much of it can we realistically get back?
This post covers the calculation. It also covers the part most guides skip the difference between the revenue that appears lost and the revenue that's genuinely recoverable, which are very different numbers. If you're still at the stage of identifying where the drop-offs are, start with our guide on spotting conversion drop-offs using GA4 funnel reports and come back here.
Step 1: Pull the Raw Numbers From GA4
Open GA4 → Explore → Funnel Exploration. Build a standard closed funnel over a clean 30-day window (avoid sale periods, they distort every ratio):
Step | Event |
|---|---|
1 |
|
2 |
|
3 |
|
4 |
|
5 |
|
Record the absolute user count at each step, not just the completion percentage. The percentages tell you where the problem is; the absolute numbers are what you convert into rupees.
You also need two figures from Shopify (not GA4, more on why below):
Total orders for the same 30-day window
Average order value = total revenue ÷ total orders
Step 2: Calculate Raw Drop-Off Value
For any funnel step, the raw value of the drop-off is:
Raw drop-off value = (Users at step N − Users at step N+1) × AOV × Expected conversion rate of that segment
That last multiplier matters, and it's where most calculations go wrong.
A user who viewed a product page is not worth a full AOV. Most product page viewers were never going to buy. A user who reached the payment step, on the other hand, had demonstrated near-complete purchase intent their value is much closer to a full AOV.
Use these intent weightings as a starting point:
Drop-off between | Intent weighting |
|---|---|
| 5–8% |
| 25–35% |
| 50–60% |
| 70–85% |
These are the rough probabilities that a user at that step would have converted in an ideal-friction scenario. Calibrate them against your own historical data if you have it.
Worked example, a D2C brand with ₹1,800 AOV:
40,000 users viewed a product
3,200 added to cart → 36,800 dropped off
1,900 began checkout → 1,300 dropped off
1,400 reached payment → 500 dropped off
980 purchased → 420 dropped off
Step | Users lost | Weighting | Raw value |
|---|---|---|---|
PDP → Cart | 36,800 | 6% | ₹39,74,400 |
Cart → Checkout | 1,300 | 30% | ₹7,02,000 |
Checkout → Payment | 500 | 55% | ₹4,95,000 |
Payment → Purchase | 420 | 78% | ₹5,89,680 |
The PDP step looks like the biggest number by a wide margin. This is where most analyses stop and where most of them go wrong.
Step 3: Apply a Realistic Recovery Rate
Raw drop-off value is not recoverable revenue. It's the theoretical ceiling if friction dropped to zero, which never happens.
The realistic question is: how much of this can a CRO programme actually recover?
Recovery rates vary sharply by funnel step, because the cause of drop-off differs:
Step | Typical achievable recovery | Why |
|---|---|---|
PDP → Cart | 3–8% | Most non-adders had low intent. Hard to shift at scale. |
Cart → Checkout | 10–20% | Shipping transparency, trust signals, guest checkout — well-understood levers. |
Checkout → Payment | 15–25% | Form friction and field reduction produce reliable gains. |
Payment → Purchase | 20–35% | Payment failures and retry paths are often straightforward technical fixes. |
Applying these to the example above:
Step | Raw value | Recovery rate | Recoverable revenue |
|---|---|---|---|
PDP → Cart | ₹39,74,400 | 5% | ₹1,98,720 |
Cart → Checkout | ₹7,02,000 | 15% | ₹1,05,300 |
Checkout → Payment | ₹4,95,000 | 20% | ₹99,000 |
Payment → Purchase | ₹5,89,680 | 28% | ₹1,65,110 |
The picture changes completely. The PDP drop-off looked twenty times larger than the payment drop-off in raw terms. In recoverable terms, they're within ₹35,000 of each other and the payment step requires far less work to fix.
This is the number that should drive prioritisation. Not raw drop-off volume. Recoverable value per unit of effort.
Step 4: Segment Before You Act
An aggregate number hides where the recoverable revenue actually sits. Re-run the calculation with breakdowns applied:
By device. If mobile is 70% of traffic and converts at half the desktop rate, most of your recoverable revenue is concentrated there. A fix that only works on desktop addresses a fraction of the opportunity.
By payment method. For Indian D2C brands this is essential. COD and prepaid buyers have structurally different drop-off patterns at the payment step, and the recovery levers are different COD abandonment is usually a trust or confirmation issue, prepaid abandonment is usually a transaction failure issue. Our guide to GA4 setup for brands with multiple funnels covers how to configure this segmentation.
By traffic source. Recoverable value from a retargeting audience is genuinely recoverable. Recoverable value from cold prospecting traffic often isn't, those users may never have been in-market.
The Assumption This Entire Calculation Rests On
Every number above comes from GA4 event counts. If those events are wrong, the calculation produces a confident, precise, wrong answer.
Three specific failure modes that invalidate this analysis:
Duplicate purchase events. If your order confirmation page fires purchase twice for a portion of orders, your final funnel step is overstated. The payment → purchase drop-off looks smaller than it is, and you'll under-prioritise the step with the highest recovery rate.
Missing begin_checkout on mobile. A common failure after Shopify theme updates. The cart → checkout drop-off appears catastrophic and the checkout → payment drop-off appears tiny — because most mobile users never registered at the checkout step at all. You'd direct your entire CRO budget at the wrong stage.
Missing value or currency parameters. If some purchase events fire without revenue data, your GA4 AOV is wrong. This is why Step 1 instructs you to pull AOV from Shopify, not GA4.
The validation check: compare GA4 purchase event count against Shopify order count for the same window. Within 5–8% is acceptable. Outside that range, fix the tracking before running this calculation, the output isn't usable. Our GA4 ecommerce tracking audit guide covers the full reconciliation process.
This is why FunnelFreaks validates the data layer before producing any revenue-loss analysis. Every conclusion we hand a client is data-backed, which requires the underlying events to be verified first, a quantified revenue opportunity built on unverified tracking is a number that looks rigorous and isn't.
Turning the Number Into a Decision
Once you have recoverable value by step, three decisions become straightforward:
What to fix first. Rank by recoverable value ÷ implementation effort. A ₹99,000/month opportunity that takes two days to fix beats a ₹1,98,720/month opportunity requiring a three-month redesign.
Whether a CRO engagement is worth it. Total recoverable revenue across all steps gives you the ceiling. If your total recoverable value is ₹5 lakh/month and a CRO agency retainer is ₹1 lakh/month, the economics work comfortably. If recoverable value is ₹80,000/month, they don't and a one-time audit is the better model.
How to set realistic expectations. Recoverable revenue is what's achievable over 6–12 months of sustained work, not next month. Sharing this number with stakeholders upfront prevents the month-three conversation where nobody understands why revenue hasn't moved yet.
Want a quantified view of where your store's recoverable revenue actually sits, calculated on tracking we've validated first? Talk to FunnelFreaks.