Digital Quality
Rank bugs by the people they cost you.
A stack-trace count tells you which error logs the most. Session impact tells you which one is quietly costing you a cohort. The loudest error is rarely the costliest, and the order changes the moment you sort by sessions affected.
Error Analysis
Prioritize technical errors, UX friction, and product-flow issues by session impact.
Showing 3 of 128 issues
Sorted by damage
Sessions affected, not occurrences. A retry loop firing ten thousand times in one session is one problem, not ten thousand.
With the context attached
The screen it happened on, the release it appeared in and the device class it prefers.
One click from the recording
Open a session that hit the error and watch what the user was doing when it broke.
What Error Tracking does
Impact-ranked
The ordering that makes a backlog triageable instead of overwhelming.
- Errors ranked by sessions affected across web and mobile
- Occurrence counts kept alongside, not instead of, session impact
- Trend per issue, so a new regression separates from a long-standing annoyance
Enough context to reproduce
Most of the time lost on a bug is spent working out when it happens.
- The screen or page the error was raised on
- Release, platform and device class
- Frequency over time, so an intermittent fault is visible as one
The evidence, not just the trace
A recording of the session that hit it answers questions a stack trace cannot.
- Open a replay of an affected session directly from the issue
- See the error flagged on the session timeline
- Check whether the user recovered or abandoned
Better with the rest of it
Every module reads the same identity, events and sessions, so an investigation that starts here does not have to be rebuilt to continue somewhere else.
Frequently asked questions
Is this a replacement for Sentry or a similar tool?
It answers a different question. A dedicated error tracker is built for the stack trace and the fix; this is built for deciding which error to fix first, by showing how many real sessions each one spoils and letting you watch one.
Why rank by sessions rather than occurrences?
Occurrence counts reward errors that fire in loops. Sessions affected counts people, which is what the prioritisation argument is actually about.
Does it cover mobile as well as web?
Yes. Web errors appear here, and iOS and Android crashes are covered in more depth on the mobile crash reporting page.