Inside Dozenfold

Understand the journey.
Follow the result.

Errors, slow scripts, shopper journeys and the release you just shipped. Connect what shoppers experience to what your team changes—and what happens afterward.

Explore five connected workflows

northstar-outdoor / product tourIllustrative data · No live store connected

Issues & impact

Your next fix, in context.

See which shoppers are affected, where they struggle and the revenue evidence available.

PRIORITY ISSUE Cart

Cart update fails after a delivery change

A recurring request failure, concentrated on Mobile Safari.

486 affected sessions↑ 39% occurrences vs previous period

Estimated revenue impact$18,420Measured loss · Selected 30 days

Measured

A gap you can rely on

The whole 95% interval of the conversion gap is above zero, against clean sessions at the same journey stage.

Directional

A signal, clearly labelled

The gap is positive but its interval still includes zero. Worth a look; keep watching as evidence builds.

Still collecting

The issue stays visible

Investigate failures and affected shoppers while the inputs for a revenue estimate build up.

Each amount belongs to one issue and its selected period. Overlapping issues are not added into a store total.

Follow this issue

Sessions & developer brief

Give your developer
somewhere to start.

Move from the affected journey to the request, environment and source context. Bring the evidence into your team’s own workflow.

One affected journeyCaptured events

12:41:58
Viewed a product/products/ridge-jacket
12:42:11
Added a variant to cartShopify funnel event
12:42:46
Changed delivery optionStorefront cart action
12:42:47
Cart update failed
POST /cart/update
Observed request failure
The request and captured TypeError appear in this journey. Inspect their timing and source context to establish how they relate.
Mobile Safari · production
storefront@2.18.4
Request bodies, response bodies and typed values are not part of this example.

Pages, actions and outcomes. No typed values.

With error-session replay turned on, a masked recording of the minute before this failure and the rest of the session plays beside the timeline.

Developer evidenceMapped source

Try the source-map states Uploaded Not uploaded

Cannot read properties of undefined

Mobile Safaristorefront@2.18.4

cart.ts:184
182  const rate = rates.find(matchRate)
183  setPending(true)
184  rate.handle
185  await updateCart(rate)

theme.min.js:1:4281

The stack is here.
Your source map connects the rest.

Upload the map for this release to resolve minified locations to original source.

See source-map setup ↗

Original source is available when a usable source map is uploaded.

A brief you can take with you.

Open the issue’s Developer brief as a Linear or GitHub issue, or hand it to your developer or coding assistant: stack, source context, environment and the observed path to the failure. Or connect the assistant directly: through MCP it reads the same issue, session and release evidence.

Connect your AI tools ↗Download example brief

Take the observed failure into Linear, GitHub or your coding assistant, then follow the issue after your team ships a change.

Developer guide ↗Watch the follow-up →

Pages & performance

Find the page.
Then find the friction.

Look beyond one error. See where shoppers land, arrive from and leave, the LCP split behind each page group, device and browser patterns, and the linked sessions and issues.

Storefront pagesLast 30 days

Page groupLandingsLCP · p75Affected sessions

Product pages/products/[product]8,9403.6s126

Collections/collections/[collection]5,2102.1s42

Cart/cart6101.8s486

PRODUCT PAGES · MOBILE

3.6sNeeds improvement

Largest Contentful Paint

How long the main content takes to appear for real visitors.

Good2.5s4s

p75 · 2,100 captured measurements

Friction findings carry their own conversion comparison; performance findings are useful without a revenue estimate. Browser and device concentration help choose where to investigate.

Pages guide ↗Performance guide ↗

Releases & recurrence

Keep an eye on
what you just shipped.

See new and returning issues around a deployment, inspect early changes, and follow the current release for as long as it stays live.

Current releaseDeployed 2 days ago

storefront@2.18.5

Early impactFirst 2 daysCompared at equal release age

Release lifetime2 days & countingContinues until the next release

2.18.4 · Failure observedDF-1876 first appeared after the earlier release

↗

2.18.5 · Change deployedThe team ships a delivery-selector change

✓

Keep the issue on watchNew occurrences can bring it back into view

DF-1876 / ILLUSTRATIVE FOLLOW-UP

Did this issue come back?

After a proposed fix, review recurrence alongside traffic that reached the affected journey.

0Captured recurrences

346Observed cart journeys
including 72 on Mobile Safari

Two days of observation are an early signal. Continued activity and coverage matter; this does not claim recovered revenue.

Release guide ↗Check collection health →

Setup & collection health · Shopify integration example

Installed is a step.
Receiving data is the proof.

Confirm the theme embed and Shopify Pixel are connected, then check that both are delivering fresh evidence to your workspace.

✓

Theme embedStorefront monitoring enabled

Active

✓

Shopify PixelFunnel connection configured

Connected

✓

Fresh evidenceRecent SDK and Pixel receipts

Receiving

COLLECTION HEALTH

A quiet store is different
from a broken connection.

Settings distinguishes recent activity, quiet traffic, paused collection and unavailable data. Session continuity helps check whether SDK and Pixel journeys join.

If data is missing

Collection follows Shopify analytics permission. Guided setup includes checking the first real evidence together.

Shopify installation guide

CONNECTED PRODUCT WORKFLOWS

A storefront engine. Six ways to put it to work.

Start with your team’s question. Follow the evidence across the product.

Issue analytics

Find the pattern inside an issue.

Performance & scripts

From slow pages to scripts worth inspecting.

Shopper journeys

Follow a drop-off into captured evidence.

Developer evidence

Turn an issue into a useful technical handoff.

Release intelligence

Keep watching after the deployment.

Revenue impact

Give the next fix a business context.

YOU BRING

Your store and the person who ships.

One critical shopping journey, storefront access for guided setup and a developer or agency who can own changes.

WE WORK THROUGH

Evidence worth a first review.

Verified collection, a prioritized issue review and a technical handoff when a useful finding emerges.

YOU LEAVE WITH

A clear next action.

An agreed owner and follow-up: investigate, ship a fix or collect the missing evidence. Findings depend on observed traffic.

Get ready for your first review

Your store.
Our next useful finding.

Turn real storefront evidence into a practical plan for your team. Bring the person responsible for your theme or development, and we’ll review the first meaningful findings together.

Session-based pricingAll core features in every planDirect founder support

Book a demo Estimate your price and contact us →

DF-1876 / DEVELOPER HANDOFF

Take the evidence with you.

A technical brief for your developer or coding assistant. Review it here, then copy or download it into your own workflow.

Illustrative issue · No shopper identity or revenue figures

# Dozenfold — example developer brief

Illustrative product-tour data. This is a fictional issue, not a customer incident.
Use it to see the kind of evidence you can take from Dozenfold into your team's workflow.

## Issue

DF-1876 — Cart update fails after a delivery change

- Error: TypeError: Cannot read properties of undefined
- Observed environment: production, Mobile Safari
- Release: storefront@2.18.4
- Affected surface: storefront cart delivery selector

## Observed journey

1. 12:41:58 — Viewed /products/ridge-jacket
2. 12:42:11 — Added a variant to the cart
3. 12:42:46 — Changed the cart delivery option
4. 12:42:47 — POST /cart/update failed; TypeError captured

These are captured events, not a screen recording or a guaranteed reproduction.
No shopper identity, typed value, request body or response body is included.

## Original source context

Available in this example because a usable source map was uploaded.

```ts
// cart.ts:184 — illustrative source
const rate = rates.find(matchRate);
setPending(true);
rate.handle; // captured failing line
await updateCart(rate);
```

## Investigation starting point

Inspect how the delivery selector handles a missing matching rate. Check the captured browser
and release context against your implementation. The evidence locates an observed failure;
it does not establish its root cause or prescribe an automatic fix.

## Product guides

- Developer evidence: https://docs.dozenfold.com/docs/developer-evidence
- Source maps: https://docs.dozenfold.com/docs/source-maps
- Sessions and journeys: https://docs.dozenfold.com/docs/sessions-and-journeys

The live product's brief is scoped to the selected issue and occurrence. This public example
contains no live investigation link and no financial estimate.

DF-1876 / CLIENT REVIEW

A decision you can explain.

Client review: cart delivery update

Northstar Outdoor · DF-1876 · Selected 30 days

Illustrative working example prepared for a client conversation. This is not a customer result or an automatically generated client report.

The decision

Prioritize investigation of the cart delivery selector with the team responsible for the storefront. Shoppers changing a delivery option encounter a recurring failure, concentrated on Mobile Safari in storefront@2.18.4.

Why this issue

486 affected sessions in the selected period.
$18,420 measured revenue loss, associated with this issue in USD.
480 affected sessions were compared with clean sessions at the same journey stage, device and environment. Within the same 30-minute window, 10% of affected sessions purchased against 34% of clean sessions.
The pooled gap is 24.0 points with a 95% interval of 21.2–26.8 points, entirely above zero. About 115 missed purchases are valued at the $159.90 clean average order value. The 6 affected sessions without a comparable clean group are not priced. This is not confirmed lost revenue or a store-wide total.

Inspect the example calculation

The proposed next step

The storefront developer investigates the delivery selector using the observed journey and uploaded source map at cart.ts:184. Check how a missing matching delivery rate is handled; the evidence does not yet establish the root cause.

The technical brief carries the stack, environment and source context. It deliberately excludes financial estimates so it can be shared in the developer’s own workflow.

Open the technical investigation

What we will review after a fix

Record the actual deployment and look for this issue on the new release, including relevant traffic and browser coverage. If it recurs, reopen the investigation. An absence of errors without observed activity is not evidence of a successful fix.

Current status: investigation proposed. No fix, recovered revenue or post-fix outcome is claimed in this review.

# Client review: cart delivery update

**Northstar Outdoor · DF-1876 · Selected 30 days**

Illustrative working example prepared for a client conversation. This is not a customer result or an automatically generated client report.

## The decision

## Why this issue

- **486 affected sessions** in the selected period.
- **$18,420 measured revenue loss**, associated with this issue in USD.
- **480 affected sessions** were compared with clean sessions at the same journey stage, device and environment. Within the same 30-minute window, 10% of affected sessions purchased against 34% of clean sessions.
- The pooled gap is 24.0 points with a 95% interval of 21.2–26.8 points, entirely above zero. About 115 missed purchases are valued at the $159.90 clean average order value. The 6 affected sessions without a comparable clean group are not priced. This is not confirmed lost revenue or a store-wide total.

[Inspect the example calculation](https://dozenfold.com/product#revenue-calculation)

## The proposed next step

The technical brief carries the stack, environment and source context. It deliberately excludes financial estimates so it can be shared in the developer's own workflow.

[Open the technical investigation](https://dozenfold.com/product#investigate)

## What we will review after a fix

**Current status: investigation proposed.** No fix, recovered revenue or post-fix outcome is claimed in this review.

Understand the journey.
Follow the result.

Your next fix, in context.

Cart update fails after a delivery change

A gap you can rely on

A signal, clearly labelled

The issue stays visible

Give your developer
somewhere to start.

The stack is here.
Your source map connects the rest.

A brief you can take with you.

Find the page.
Then find the friction.

Largest Contentful Paint

Keep an eye on
what you just shipped.

storefront@2.18.5

Did this issue come back?

Installed is a step.
Receiving data is the proof.

A quiet store is different
from a broken connection.

A storefront engine. Six ways to put it to work.

Your store and the person who ships.

Evidence worth a first review.

A clear next action.

Your store.
Our next useful finding.

A priority you can look into.

What happened after the failure?

Take the evidence with you.

A decision you can explain.

Client review: cart delivery update

The decision

Why this issue

The proposed next step

What we will review after a fix

Your next fix, in context.

Cart update fails after a delivery change

A gap you can rely on

A signal, clearly labelled

The issue stays visible

Give your developersomewhere to start.

The stack is here.Your source map connects the rest.

A brief you can take with you.

Find the page.Then find the friction.

Largest Contentful Paint

Keep an eye onwhat you just shipped.

storefront@2.18.5

Did this issue come back?

Installed is a step.Receiving data is the proof.

A quiet store is differentfrom a broken connection.

Your store and the person who ships.

Evidence worth a first review.

A clear next action.

Your store.Our next useful finding.

Give your developer
somewhere to start.

The stack is here.
Your source map connects the rest.

Find the page.
Then find the friction.

Keep an eye on
what you just shipped.

Installed is a step.
Receiving data is the proof.

A quiet store is different
from a broken connection.

Your store.
Our next useful finding.