ISSUE ANALYTICS & BREAKDOWNS
One issue.
Eleven ways into the why.
“It works on my machine” is a starting point. See where an issue actually appears, which shoppers it touches and where your team should look next.
Change the lens. Keep the issue.
Explore the same cart failure across several dimensions. Each view keeps the issue and observation window in place.
DF-1842 · CART UPDATE FAILED
Where does this issue appear?
Start with Mobile Safari when reproducing this failure.
Follow the evidence →Check the mobile delivery selector and the cart interaction.
Follow the evidence →Compare the captured iOS path with the other environments.
Follow the evidence →A narrow layout is a useful reproduction starting point.
Follow the evidence →Open the cart page and follow the delivery-change action.
Follow the evidence →Use the captured page location to narrow your investigation.
Follow the evidence →Follow the shopping paths associated with these sessions.
Follow the evidence →Campaign association helps you choose a path to inspect.
Follow the evidence →Share of this issue’s captured occurrences. Channel and campaign describe association.
Separate the issue from the noise.
Grouped JavaScript, promise, resource and request failures give you a consistent place to investigate, including errors thrown inside browser callbacks and Error objects passed to console.error. The same problem stays one issue across deploys. Track activity over time, open captured occurrences and prioritize using affected sessions and the available revenue evidence.
Put the priority in business contextChoose the environment worth reproducing.
Browser, device, operating system, coarse viewport, country, connection type and device memory breakdowns show where the issue was recorded. Compare occurrence counts, affected sessions and occurrence share to choose a useful testing environment. A concentrated issue becomes a specific debugging starting point.
Open the developer workflowFind where the journey meets the failure.
Page groups and privacy-safe URLs show where the error appears. Channel and campaign context connect it to the session’s acquisition. Use these patterns to decide which page and shopping path to inspect, then open captured session evidence. Acquisition describes association; it does not establish that a campaign caused the error.
Follow the affected journeyA LITTLE MORE DETAIL
Good questions.
Useful answers.
Is every error a bug in my store?
Not always. Each issue shows the share of its occurrences from social apps’ in-app browsers (Instagram, Facebook, TikTok, Pinterest, Snapchat), from shoppers who were offline, and from browser-extension code. When extensions or lost connections dominate, the issue says so before anyone starts debugging.
Which issue breakdowns can I explore?
Browser, device, operating system, coarse viewport, country, connection type, device memory, page group, URL, channel and campaign. The issue stays in focus as you switch dimensions, so your investigation can move from an environment to a page or acquisition pattern.
Which errors does Dozenfold capture?
Uncaught errors and unhandled promise rejections, errors thrown inside browser API callbacks such as timers and event listeners, Error objects passed to console.error, and failed requests and resources. When an error has a cause chain or is an AggregateError, the linked errors stay with it. Your developers can also report handled errors with captureException.
What does occurrence share mean?
It is the share of this issue’s captured occurrences in the selected evidence window. It describes the issue’s composition. Compare it with traffic context when deciding whether an environment is disproportionately affected; a large share alone is not a failure rate.
Where do I go after finding a pattern?
Open captured occurrences and affected sessions, inspect the environment, breadcrumbs and stack, then bring the selected evidence into a Developer brief. Keep the same issue on watch after the release.
Will my team hear about a new issue?
Yes, in Slack. Add one or more channels and pick the alerts each one receives: checkout-stage errors, cart API failures, new issues, regressions, spikes and Core Web Vital degradation. When they are ready, an alert shows the issue’s estimated revenue impact and its likely owner: your theme, Shopify, a third-party script or a browser extension. Quiet hours hold alerts during a recurring time window.
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.PUT YOUR STOREFRONT IN FOCUS
Your store.
Your next useful fix.
Bring the shopper journey you want to improve and the person who ships your changes. We’ll connect the first evidence and work through the findings together.
Book a demo Estimate your price and contact us · Guided setup