dozenfold Docs
DOZENFOLD DOCUMENTATIONView as Markdown

Understand what breaks for shoppers

Dozenfold monitors anonymous storefront sessions for recurring browser, network, commerce, and performance problems. It connects each problem to the journey where it appeared, the sessions that encountered it, and the technical evidence a developer needs to investigate it.

Dozenfold is designed to answer three questions:

  1. What is going wrong? Related failures are grouped into issues instead of shown as an alert stream.
  2. Why should we look at it now? Current activity, affected journeys, conversion evidence, and measured or directional revenue estimates help prioritize work.
  3. What will help us fix it? Browser context, release evidence, privacy-safe reproduction steps, stack information, and affected sessions stay connected to the issue.

Choose your integration

Shopify has a ready-made app integration. For a custom storefront, contact our team to agree the integration and rollout. The Shopify-specific setup, consent and checkout instructions in these docs apply to that integration. Custom implementations are scoped separately.

What Dozenfold monitors

  • JavaScript errors and unhandled promise rejections, including errors thrown inside browser API callbacks and Error objects passed to console.error
  • Failed cart, HTTP, GraphQL, image, script and stylesheet requests observable on the storefront
  • Shopify Pixel checkout and purchase funnel events; theme monitoring does not inspect every hosted-checkout interaction
  • Storefront funnel progression from visit to completed checkout
  • Anonymous session journeys and page transitions
  • LCP, INP, and CLS field measurements
  • Privacy-safe friction signals such as rage-click, dead-click candidate, repeated-submit, form-exit, and navigation-loop patterns
  • Release markers and captured release identifiers
  • Error context that separates store bugs from environment noise: in-app browsers, offline shoppers and browser-extension code
  • Conversion by country, connection type and device memory, with the segment that converts worst

What Dozenfold does not record

By default Dozenfold does not record the screen. It does not record input values, page text, mouse movement, full request bodies, authentication headers, or a persistent shopper identity. Sessions use a random identifier that expires after 30 minutes of inactivity.

Error-session replay is an optional module that is off until the store turns it on in Settings. When it is on, it records a masked page reconstruction only in sessions where an error happens: the minute before the first error, then the rest of the session until the shopper goes idle, for up to 30 minutes. Inputs are always masked and page text is masked unless the store chooses otherwise. Replays are kept for 30 days.

Read Privacy and data collection for the complete boundary.

Evidence, not invented certainty

Dozenfold distinguishes observed evidence from selected-period estimates. A relationship between an issue and lower conversion does not prove the issue caused every lost order. When the available sample cannot support a conclusion, the product shows the evidence as early or insufficient instead of filling the gap with zero or a guessed impact.

Choose your starting point

Search documentation

Start typing to search all documentation.