Analytics & Conversion
Payment funnel
Section titled “Payment funnel”For paid routes, each request moves through these stages:
402 issued → payment sent → payment verified → settled → upstream served → response completedDrop-off between any two stages tells you where revenue is lost.
Core metrics
Section titled “Core metrics”| Metric | Formula |
|---|---|
| Attempt rate | payment_attempted / requires_payment |
| Verification success | payment_verified / payment_attempted |
| Settlement success | settled / payment_verified |
| End-to-end conversion | response_completed / requires_payment |
| Revenue per paid request | sum(settled_amount) / count(settled) |
What to track per event
Section titled “What to track per event”Every event should carry a shared request_id plus:
route_id— which routestatus_code— HTTP status at this stagepricing_mode—static,rule-based,token-based, orcustom-fnsettlement_mode—before-responseorafter-response
For failure events, include failure_code and failure_reason so drop-off reasons are explicit rather than inferred from missing success events.
Segment by
Section titled “Segment by”route_id— which routes convert bestupstream_id— upstream health impact on conversionpricing_mode— how pricing strategy affects conversionnetwork/asset— payment method performance
Key signals
Section titled “Key signals”- Gap between verification and settlement — check facilitator health
- Gap between settlement and 200s — upstreams are failing after payment (see Refund Protection)
- High 402 rate with low attempt rate — clients aren’t paying, could be price too high or SDK issue