The Analytics page in the dashboard is webhook-driven, not batch — transactions appear within seconds of the underlying event.

​
What you get

ViewDetail
Headline cardsTotal volume, authorization rate, recovered revenue via failover (sum of captures where a failover occurred), active-gateway health
Auth rate by gatewayTime series comparing approval rates per gateway — the data that should inform your priority ordering
Decline-reason breakdownNormalized decline codes across gateways, with hard/soft classification
Failover event logEvery failover: original gateway, decline code, fallback gateway, outcome, elapsed ms
Transaction searchFilter by date, gateway, status, amount; drill into any payment’s per-attempt trail
Webhook logPer-event delivery attempts and statuses, with manual redelivery

​
Roles

Dashboard members with the Viewer role see analytics only — no keys, rules, connections, or settings. Use Viewer for finance/ops teammates who need reconciliation data but not integration credentials.

​
Recovered revenue

The headline number most merchants care about: the sum of captured payments whose first attempt failed. This is revenue that, without failover, would have ended as a declined checkout. If this number is consistently near zero, check that your rule set has a second verified gateway and that failover triggers are enabled — see Routing rules.