How Sentry was configured to show user journey funnels, not just stack traces
A development team found that despite having Sentry installed and tracking errors, no one could determine whether checkout failures stemmed from the payment step, coupon logic, or a tracking pixel. The core problem was that installation was mistaken for instrumentation — raw stack traces were being captured without context about what the user was actually doing. The team restructured their error events to include domain, phase, and action fields, allowing engineers and product managers to filter by user action before ever opening a stack trace. This change made it possible to distinguish revenue-threatening failures from post-sale noise within the same dashboard. As a result, checkout conversion data became visible alongside error data, aligning engineering alerts directly with product OKRs.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in