Not revenue lost
Start with the sentence under the report's title, because it is the one most easily misread:
Blocked cart value How much demand your rules are shaping. Not revenue lost, since a blocked cart was never a completed sale.
A blocked cart is a cart that did not meet a rule. Many of those shoppers fix the cart and check out. Some were never going to buy. Some are exactly the orders you set the rule to stop. So the total is not money your rules cost you. It is the size of the demand your rules are steering, which is what tells you whether a rule is worth a second look.
Where it is
On the Dashboard, below the free stats, on the Pro plan. It follows the Dashboard's date range picker, so changing the range there changes every number in the report.
What it contains
Summary tiles
| Tile | What it shows |
|---|---|
| Blocked cart value | The total value of blocked carts in the range, "across {count} valued attempts". |
| Largest single block | The most valuable single blocked cart. |
| Rules involved | How many rules blocked at least one attempt. |
Daily trend
A chart of blocked cart value by day across the range, to show whether a rule change, a campaign or a season moved it.
Per-rule breakdown
| Column | What it shows |
|---|---|
| Rule | The rule's name. |
| Type | Quantity, Order value or Weight. |
| Blocked attempts | How many attempts the rule blocked in the range. |
| Blocked cart value | The total value of those attempts. |
Click Detail on a row for that rule alone: customers and guest visitors affected, Why it's blocking (for example "80% of blocks are because" followed by the reason, such as below minimum quantity), Products affected, a trend, and Recent activity. Recent activity also lists shoppers who hit the limit on the product page but never clicked, marked Browsed only.
CSV export
Export summary downloads the figures on screen. Export raw events downloads each blocked attempt as a row. "Raw event export is capped at 90 days per file", so for a longer history, export in 90-day pieces.
Two notices to read before trusting a total
Both appear in the report when they apply.
Value tracking started {date} Blocked attempts before that date were counted but not valued, so there is no history to show for them.
Prime MOQ started recording cart values on a specific date. Attempts before it still appear in the free Blocked attempts counts, but have no value. A range reaching back before that date shows a lower total than the attempt count suggests, and that is expected.
This shop sells in more than one currency The totals above are in {currencyCode} only. Other currencies are not converted or mixed in.
On a store that sells in several currencies, the report totals one currency and leaves the others out, rather than converting them at a rate you did not choose. The figure is real, but partial: blocked carts in other currencies are not in it.
Free and Pro
| Free on every plan | Pro |
|---|---|
| Blocked attempts column on the Rules list | Blocked cart value report |
| Last 7 days card on the Dashboard | Per-rule detail and daily trend |
| CSV export |
The free counts answer "is this rule doing anything". The report answers "how much is it shaping". See Seeing How Often Your Rules Block Checkout.
Common mistakes
- Reporting the total as lost sales. It is not. A blocked cart was never a completed sale, and many are fixed and bought.
- Comparing value with attempts from before tracking started. Older attempts are counted but carry no value.
- Reading a multi-currency total as the whole store. It is one currency only.
- Expecting one export file for a year. Raw events export 90 days per file.
- Forgetting your own tests. Blocked attempts you made while testing a rule are counted and valued too.