RELEASE INTELLIGENCE
You shipped the change.
Now follow what changed.
Keep issues, performance, requests and shopper journeys connected to your releases. Give every deployment a follow-up your team can actually investigate.
One release. A connected set of signals.
Compare the early window, then keep observing the release while it stays live. Open the signal that needs a closer look.
STOREFRONT@2.18.5
The deployment is the start of the follow-up.
DF-1876 · PROPOSED FIX FOLLOW-UP
Keep the issue in view.
Read the early impact in context.
Compare releases at equal early ages, with errors, exposure, Core Web Vitals, requests and journey evidence nearby. See what appeared or changed around a deployment and choose the next investigation with the observation window in view.
Investigate a performance changeKeep observing beyond the first day.
Release lifetime evidence continues while the release is current. It gives the team a wider view than a single post-deploy check. Retained release comparisons preserve useful context as new versions take over the storefront.
Follow shopper outcomesAsk whether the issue came back.
After a proposed fix, review recurrence alongside traffic that reached the affected path and environment. New activity can bring a resolved issue back into view. A quiet issue is more useful when you can see the relevant observation behind it.
Return to the issue evidenceA LITTLE MORE DETAIL
Good questions.
Useful answers.
How does Dozenfold know when we deployed?
Your CI marks each deploy with the Dozenfold CLI (npx dozenfold releases create) or the Dozenfold/cli@v1 GitHub Action, which can upload the release’s source maps in the same job. New storefront events then carry that release, so early impact and lifetime evidence start at the deploy.
What can I compare around a release?
Errors and affected activity, Core Web Vitals, endpoint health and shopper journey evidence. They provide connected investigation paths rather than a single score that hides which signal changed.
What is the difference between early impact and release lifetime?
Early impact compares a bounded beginning of each release at a comparable age. Lifetime evidence keeps following the current release until the next release takes over.
How do I judge a proposed fix?
Review whether the issue recurred and whether enough relevant shopping activity was observed, including the affected environment. The follow-up helps the team decide whether to keep watching or investigate again.
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