Shape
What happened during each period
Chart · Customers
Active Customers counts the customers whose app called RevenueDot on at least one day of the period, once per customer per period. Day resolution gives daily active customers, week gives weekly and month gives monthly. A customer is active when the SDK reaches the server, which usually happens when the app opens.
Formula
Active customers in a period = distinct customers with SDK activity on at least one day of the period
Shape
What happened during each period
API name
customers_active
Measures
Active Customers (Count)
Filter and segment by
Country, Platform, App version
Definition
RevenueDot writes one activity row per customer per UTC day on which the SDK called the server. The chart counts the distinct customers with a row in the period. A day counts when any part of it falls inside the period, so a partial first period still counts the days it touches.
Because each customer counts once per period, the numbers are not additive. A customer who opens the app on Monday and Thursday is one active customer for the week and two daily actives. You get daily, weekly and monthly active customers by changing the resolution, not by summing bars.
The chart offers country, platform and app version as filters and segments, and the sandbox switch does not change it. Daily activity rows exist from the day the feature shipped. Before that, RevenueDot only knows each customer's first and last seen day, so older history undercounts. You can open it in the dashboard under Charts or fetch it with GET /v2/projects/{project_id}/charts/customers_active. The response has the same shape as RevenueCat's Charts API, so scripts written for that API keep working. The secret key needs the charts_metrics:charts:read permission. The Charts guide lists every parameter.
Worked example
One week, three customers. A opens the app Monday and Thursday, B opens it Thursday, and C opens it the next Sunday.
| Resolution | How it is counted | Active customers |
|---|---|---|
| Day (Mon) | Only A opened the app | 1 |
| Day (Thu) | A and B opened the app | 2 |
| Week (Mon to Sun) | A and B, each once | 2 |
The two daily bars add up to 3, but the week shows 2 because A counts once.
Why it matters
Active customers is the audience your paywall can reach. A subscription app earns from the people who open it, so a drop here shows up in new trials and revenue a few weeks later. It also separates two different problems: fewer people arriving (New Customers) and fewer people coming back (Active Customers).
Dividing daily active customers by monthly active customers gives a stickiness ratio. Pull both from the API at day and month resolution and divide them in your own sheet. A rising ratio means the same people open the app more often.
API
Same path and response shape as RevenueCat's Charts API, so existing scripts keep working.
curl "https://api.revenuedot.app/v2/projects/$PROJECT_ID/charts/customers_active?resolution=day" \
-H "Authorization: Bearer $SECRET_KEY" # sk_... with charts_metrics:charts:read Reference: Charts guide · REST API v2
FAQ
Open the Active Customers chart and set the resolution to day. Each bar is the number of distinct customers whose app called RevenueDot that day.
Set the resolution to month. Each customer counts once per month, so the result is lower than the sum of the daily bars.
Any day on which the SDK called RevenueDot for that customer. It is a measure of app use, not of purchases.
RevenueDot began storing one activity row per customer per day at a point in time. Earlier days only have each customer's first and last seen day, so past activity is undercounted.
Get started
Connect your app to RevenueDot Cloud, free up to $10,000 a month in tracked revenue, and all 43 charts fill from your store history after import.
Already have an account? Sign in · Prefer your own servers? Self-host free