DEVELOPER EVIDENCE & SOURCE MAPS
Less back-and-forth.
A better place to start.
Bring the error, observed path, environment and source context into the same conversation. Give the person shipping the fix something concrete to work with.
The handoff has a trail behind it.
Start with a captured occurrence. Keep its request, environment and original source connected as you prepare the next action.
SELECTED OCCURRENCE · MOBILE SAFARI
From the observed path to original source.
- Product viewed/products/ridge-jacket
- Delivery option changedCaptured storefront action
- Cart update failedPOST /cart/update · TypeError
Cannot read properties of undefined
cart.ts:184
182 const rate = rates.find(matchRate)
183 setPending(true)
184 rate.handle
185 await updateCart(rate)Original source when a usable source map is uploaded.Choose an occurrence worth opening.
An issue can appear in more than one environment or path, and the same error stays one issue across deploys. Inspect selected captured examples with their timing, browser, release and breadcrumbs, and see the likely owner: your theme, Shopify, a third-party script or a browser extension. With error-session replay turned on, the recommended occurrence is one with a masked recording, and it plays from 10 seconds before the error beside the session timeline. Keep the source context tied to the occurrence and frame you are actually investigating.
Choose an environment to investigateGet from the stack to your code.
Upload source maps for the matching release to resolve minified locations to original source, including the linked causes of an error. Third-party callbacks are wrapped so fewer failures arrive as an opaque “Script error.”, and handled errors can be reported with captureException. Inspect frames and surrounding code alongside the observed error. The request and session timeline provide context for the developer to establish how the events relate.
Explore captured session evidenceTake the evidence into your workflow.
Open the Developer brief as a prefilled Linear or GitHub issue, copy it for your developer or a coding assistant, or connect the assistant directly through MCP so it can read the issue, session and release evidence itself. Share the stack, selected source context, environment and observed path in one handoff. Once the team ships a change, return to the issue and release evidence to see what happens next.
Follow the change after deploymentA LITTLE MORE DETAIL
Good questions.
Useful answers.
What is in the Developer brief?
The selected error and technical context: occurrence details, environment, stack, usable mapped source and the captured path leading to the failure. The public example is downloadable so you can review the format before connecting a store.
Can I watch what happened before the error?
Turn on error-session replay in Settings. Only sessions with an error upload a masked recording: the minute before the error, then the rest of the session until the shopper goes idle, for up to 30 minutes; a later error starts a new recording. Inputs are always masked and page text is masked by default. The replay opens 10 seconds before the error, and when an occurrence has none, the issue says why.
Can I send the brief to Linear or GitHub?
Yes. Create Linear issue and Create GitHub issue open your tracker with the brief filled in, under your own sign-in, and you choose the team or repository there. Dozenfold stores no tracker credentials.
Can my AI tools connect directly?
Yes. Create a read-only MCP key under Settings → AI agents and add it to Claude Code, Cursor or another MCP client. The tools return the same issues, sessions, releases and revenue estimates you see in the dashboard, can filter problems to the file you are editing, and check whether a shipped fix stopped a problem. We are also building Dozenfold’s own AI reliability engineer to investigate problems, work on fixes and follow outcomes within your permissions.
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