How Sentry came to show the funnel. The journey before the stacktrace
Pessoal, o SDK tava verde. O TypeError chegou. A jornada, não. Dashboard cheio. Ninguém sabia se era o clique de pagar, o cupom ou o pixel. Três stacks iguais. Três donos diferentes. A próxima pessoa abria o evento e ia pro arquivo no bundle. Conversão do checkout era OKR de produto. O Sentry não falava a língua do OKR. O denso do +10% no checkout é o dinheiro. Este texto é o contrato que faz o…
A technical issue was causing a TypeError and impacting the conversion rate of a checkout process. The problem was that the Sentry tool was not providing enough information to identify the cause of the issue, as it was only showing stack traces. To resolve this, the team modified the events sent to Sentry to include the user's action, such as "checkout.pay.submit" or "pixel.purchase.track", in addition to the stack trace.
This allowed them to filter the events and see that the issue was related to a timeout on the payment step, which was causing a 10% increase in conversion rate. The team was able to measure the impact of the change and align it with their OKR (Objective and Key Results) for product conversion.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
