Live demo· sample data, no login — this is exactly what you’d see for your app. Get your key →

Needs your attention

You're losing checkouts to insufficient funds

16% of payment attempts failed — 12 declined.

How we knew
11 requests to /v1/checkout failed — your users are hitting errorsCheckout is converting at 80%
Total events
1.2Kexact
Payment attempts
74exact
Success rate
79.7%estimated
Declined checkouts
12exact

Event volume

1,180 events · 24h

Total
Failures

The annotated event

Response body → derived business event. Zero instrumentation.

0-code
Read from the response body
"DECLINED"
"insufficient_funds"
Drengr derived

payment_attempt

outcome
DECLINED
reason
insufficient_funds

You wrote 0 lines of tracking codefor this. Firebase, Amplitude and Segment can’t — they never see the response body.

Payment outcomes

12 declined · insufficient_funds

Captured59 · 80%
Declined12 · 16%
Pending3 · 4%

Event volume by kind

net
970
tap
100
payment_attempt
74
screen_view
53
net_fail
19

Top failing endpoints

Sorted by occurrence

/v1/checkout
api.acme.shop
402client11
/cart/checkout
api.acme.shop
500server6
/inventory
cdn.acme.shop
503server2

You wrote 0 lines of tracking code for any of this.

Firebase, Amplitude and Segment can’t show this 0-code — they never see the response body. Drengr does.

Start free →
See your own blind spots →Upload a .har of your app’s traffic and see the business events your analytics never named — scanned entirely in your browser, nothing uploaded.