REVENUE IMPACT & PRIORITIZATION
A bug list is a backlog.
Know what deserves a fix.
Connect technical failures to affected shoppers and purchase evidence. Give your team a clear reason to choose one investigation over another.
A priority you can open up.
The amount is the start of the review. Inspect the sessions, purchase comparison and order value behind the example.
DF-1876 · CART UPDATE FAILURE
Choose the next fix with its evidence in view.
PURCHASES WITHIN 30 MINUTES
Gap 24.0 points · 95% interval 21.2–26.8.
Open the amount to inspect all inputs.
Put one issue in business context.
Review affected sessions, observed purchase outcomes and the revenue estimate together. Each amount belongs to one issue and reads per day the issue was seen, like $614/day, so a new issue is not diluted by the days before it existed. Every window, even the last 24 hours, compares at least seven days of shoppers.
Explore the issue behind the amountLook through the number.
Affected sessions are compared with clean sessions at the same journey stage, device and environment, with the same 30-minute purchase window. See both purchase rates, the pooled gap with its 95% interval and the clean order value behind the amount. The selected window stays attached to the estimate.
Understand the shopping pathRank by evidence, not by the biggest number.
Measured losses lead, ordered by missed orders per day at the cautious end of the interval; directional signals follow, ordered by affected sessions. When purchases are too few to compare, Dozenfold measures whether shoppers still reach the next step (≈ 15 fewer continue/day) and never puts money on it.
Prepare the developer handoffA LITTLE MORE DETAIL
Good questions.
Useful answers.
Does the amount mean that revenue was definitely lost?
It is an estimate based on an observed comparison. It is not booked loss or proof that the issue caused every missed purchase. The evidence and selected period remain visible so your team can judge the priority.
What if my store has few purchases?
Each issue also compares whether shoppers reached the next journey stage (product to cart, cart to checkout) within the same 30 minutes. That happens far more often than a purchase, so it reaches a clear answer sooner. It reads as shoppers lost per day and never carries money. Without order values, a purchase gap reads as missed orders per day.
Why per day?
Amounts are averaged over the days the issue actually occurred within the evidence window, which is the selected window or seven days, whichever is longer. That keeps a short window comparable with a long one and a new issue comparable with an old one. It is not a forecast.
Can I add all issue estimates into one store total?
Issue populations can overlap, so their amounts should not be summed into a store total. Use them to inspect and prioritize the individual issues, then review the relevant follow-up after a change.
CONNECTED PRODUCT WORKFLOWS
Follow the next connection.
An issue, a journey, a page or a release. Each view gives you a way into the next.SEE IT ON YOUR STORE
See it on your own store.
Install Dozenfold from the Shopify App Store and switch on the theme embed; the first sessions arrive within minutes. Custom storefront or prefer to talk first? Book a demo.
Install on Shopify Book a demo · See pricing