Revenue reporting
Read payments, refunds, customers and revenue over time.
On this page
Connect the payment source
Open Integrations, choose the provider you actually use, and configure its required credentials and verified webhook. A tracker alone does not ingest payment transactions. See the provider directory.
Read the summary
Revenue reporting includes total revenue, refunds, transactions, customers, subscriptions, ARPU, revenue per visitor and visitor-to-customer conversion. Treat named revenue and refund fields according to their labels; do not assume every total is net revenue after refunds or fees.
Currency rules
Set the site's reporting currency deliberately. Tool results explicitly identify their currency. Fields named Cents contain minor units; get_revenue_summary converts its money fields to major units using the returned currency, including zero-decimal currencies. Never add different currencies or divide a major-unit value by 100 again.
Review transactions
Transaction lists are paginated using limit and offset. Compare purchases and refunds with the provider dashboard, checking the time window, currency, event status and sync coverage. Historical sync support varies by provider.
Attribution is a second question
Revenue can be present without a matched visitor journey. Use the attribution guide to understand touchpoints and choose a model.
API equivalents
get_revenue_summary, get_revenue_timeseries, list_transactions.
Still looking for an answer? Try troubleshooting or get in touch.