Get your first useful signal

After installation, use this short path to confirm that Dozenfold is useful—not merely connected.

Check monitoring status

Open Settings and confirm that the storefront setup does not require recovery. Then open Overview and choose a 7-day window while evidence is new.

The first sessions may produce valid zeros or early evidence. These states are different:

Collecting data means the required denominator has not arrived yet.
No issue observed means the query completed and no matching problem was found.
Unavailable means Dozenfold could not load that evidence family.

Follow one problem end to end

Open Issues.
Start with Prioritized or Needs review.
Open an issue with recent affected sessions.
Read the issue summary for impact and environment concentration.
Open Reproduce to inspect the common path and affected anonymous sessions.
Open Developer for the technical fingerprint, stack, release and source context. Use Developer brief beside the issue actions to copy the technical handoff.

If there are no issues yet, use Analytics, Sessions and journeys, and Performance to confirm that field evidence is arriving.

Avoid an early conclusion

A new installation does not immediately have enough issue and control sessions to calculate commercial impact. Dozenfold keeps raw affected-session and occurrence evidence visible while impact readiness develops. See Revenue impact methodology.