Browse wiki · Funnel analytics
Funnel analytics
← All topicsUnderstand payment analytics
Free Reports shows created, viewed, started and confirmed invoices over 30 days, grouped by invoice creation day in UTC. Confirmations come from server records; browser stages are advisory, deduplicated per invoice and can be missing or manipulated. API payments need not pass through browser stages. There are no analytics cookies, fingerprints or buyer profiles.
Advanced Analytics costs 1,000 credits per 30 days or is included in Growth. Choose 7, 30 or 90 days, inspect the daily chart and table, compare the preceding period, see confirmed networks and failure signals, and export daily CSV including all breakdowns. The current day is partial. Daily aggregates are retained for approximately 90 days, so a preceding 90-day comparison is unavailable. Collection may have started later; empty historical days are not proof that collection was active.
Amounts and timing
Recorded volume is the exact USDC amount of covered confirmed invoices, not profit. Older payments are not backfilled: volume and timing coverage show how many confirmations have the newer metrics. Average time measures invoice creation to server confirmation, not blockchain latency. Median and p95 use bounded power-of-two-second histogram buckets and are approximate upper bounds. They are not exact percentiles.
Network counts measure successful payments only, so they do not establish network success rates. Checkout rejected/failed signals do not prove blockchain failure. Expiry counts are payment-window events; older pre-retirement invoice records may contribute more than one expiry. Cohorts change when an older invoice is paid later.
GET /analytics # billing:read; basic included
POST /features/analytics/purchase # billing:write + Idempotency-Key
GET /analytics?advanced=true&days=7 # active entitlement
GET /analytics?format=csv&days=90 # active entitlementUse 7, 30 or 90 for days. CSV includes daily totals, summed creation-to-payment seconds, covered USDC volume, timing coverage, approximate median/p95 and JSON-encoded network/failure maps. Financial fulfillment must use verified payment status or receipts, never browser analytics.