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.

northstar / issue analyticsLast 30 days

DF-1842 · CART UPDATE FAILED

Where does this issue appear?

486 affected sessions1,000 occurrences
BrowserAffected sessionsOccurrencesOccurrence share
Mobile Safari331680
Chrome111230
Firefox4490

Start with Mobile Safari when reproducing this failure.

Follow the evidence →
DeviceAffected sessionsOccurrencesOccurrence share
Mobile369760
Desktop102210
Tablet1530

Check the mobile delivery selector and the cart interaction.

Follow the evidence →
OSAffected sessionsOccurrencesOccurrence share
iOS302620
Android117240
macOS / Windows67140

Compare the captured iOS path with the other environments.

Follow the evidence →
ViewportAffected sessionsOccurrencesOccurrence share
Small mobile282580
Large mobile87180
Tablet / desktop117240

A narrow layout is a useful reproduction starting point.

Follow the evidence →
CountryAffected sessionsOccurrencesOccurrence share
United States212440
Canada148300
United Kingdom126260

Spread across countries in line with traffic: not a regional problem.

Follow the evidence →
ConnectionAffected sessionsOccurrencesOccurrence share
Unknown (Safari, Firefox)375770
4g88180
3g2350

Only Chromium reports connection. Mostly Safari here, so Unknown leads.

Follow the evidence →
Device memoryAffected sessionsOccurrencesOccurrence share
Unknown (Safari, Firefox)375770
8 GB or more61125
4 GB50105

Low-memory phones are not over-represented. Memory is not the lead.

Follow the evidence →
Page groupsAffected sessionsOccurrencesOccurrence share
Cart389800
Product73150
Collection2450

Open the cart page and follow the delivery-change action.

Follow the evidence →
URLsAffected sessionsOccurrencesOccurrence share
/cart389800
/products/ridge-jacket58120
/collections/outdoor3980

Use the captured page location to narrow your investigation.

Follow the evidence →
ChannelsAffected sessionsOccurrencesOccurrence share
Paid social219450
Organic search160330
Direct107220

Follow the shopping paths associated with these sessions.

Follow the evidence →
CampaignsAffected sessionsOccurrencesOccurrence share
Summer sale194400
Retargeting122250
No campaign captured170350

Campaign association helps you choose a path to inspect.

Follow the evidence →

Share of this issue’s captured occurrences. Channel and campaign describe association.

Illustrative product data Explore freely. No store connection required.

KEEP THE INVESTIGATION MOVING

From a pattern to a fix.

Read the product guide ↗
01

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 and locale-prefixed routes, and our own script’s frames never split it. Track activity over time with Auto, 15-minute, hourly or daily intervals, open captured occurrences and prioritize using affected sessions and per-day revenue evidence.

Put the priority in business context
02

Choose 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 workflow
03

Find 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 journey

A 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.

Will my team hear about a new issue?

Yes, in Slack or Telegram. Add one or more Slack channels or Telegram chats 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, and store owners get a weekly report by email.

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
DOZENFOLD / PRIVACY

Make yourself at home.