How do I analyse ARPU (average revenue per user) with iDBQuery?
Ask iDBQuery 'What is ARPU this month, and how has it trended over the last year by plan?' It divides revenue by active users across your billing and account tables, returns the trend as a chart, and cites each month's figure back to the source rows.
ARPU (average revenue per user) tells you how much revenue each active customer generates on average, and its trend reveals whether growth is coming from more users or richer accounts. iDBQuery computes it without you writing a line of SQL.
- You'd ask iDBQuery: 'Show monthly ARPU for the last 12 months, split by plan, and flag the biggest change.'
- It joins revenue to your count of active users, calculates the ratio per period, and returns a trend chart plus a table.
- Every value is cited to its underlying rows, so you can confirm 'March ARPU = $58' against the exact revenue and user counts used.
The useful part is the follow-up. Ask 'Is ARPU rising because of upsells or because low-value users churned?' and iDBQuery keeps the thread, decomposing the change. Because active-user data and revenue often live in different systems, its one live model joins them directly, no export needed. You can pin ARPU alongside MRR and churn on a live dashboard, or define it once as a governed metric so every team's number agrees. If a period looks anomalous, the Analyst agent can dig into which segment moved and show its work.
Updated 2026-06-22
Related questions
- How do I calculate customer lifetime value (LTV/CLV) with iDBQuery?
- How do I measure net revenue retention (NRR) and gross retention (GRR) with iDBQuery?
- How do I report MRR and revenue with iDBQuery?
- How do I analyse unit economics with iDBQuery?
- How do I do week-over-week and month-over-month analysis with iDBQuery?