Cart update fails after a delivery change
Measured loss$614/dayOne issue · 30-day evidence window · USD
Illustrative calculation.
No live store connected.
486Affected sessions
480Compared with clean sessions
9,720Clean sessions
What happened after the failure?
Affected sessions hit the failure within 30 minutes of entering a journey stage. Clean sessions reached the same stage on the same device and environment without this issue. Purchases count in the same 30-minute window for both.
With this issue10%48 / 480 purchased
Clean sessions34%Same stage, device and environment mix
The interval decides the label.The pooled gap is 24.0 percentage points with a 95% interval of 21.2–26.8 points. The whole interval is above zero, so the loss is measured. Strata where affected shoppers converted better pull the gap down instead of being ignored.
See the inputs and calculation
480 compared sessions × 24.0% conversion gap = 115.2 missed purchases × $159.90 clean average order value ≈ $18,420 over the evidence window. The issue occurred on all 30 days, so it reads $614 per day.
The order value uses complete clean-session orders in USD. This example has uniform, full capture. The 6 affected sessions without a comparable clean group are not priced.
This estimates a difference associated with the issue. It does not identify confirmed lost orders or establish cause. The per-day amount averages the days the issue was seen; it is not a monthly projection. Every window, even the last 24 hours, compares at least seven days of sessions.
Read the complete methodology ↗