All your RevenueCat projects in one list
RevenueCat's dashboard works per project, and most indies end up with one project per app. Seeing total MRR across five apps means switching projects five times and adding the numbers yourself, and none of those screens show the downloads or the 1-star review that explain a drop in trials.
Ertori takes one read-only key per project and puts each app's MRR, subscriptions and trials in the same row as its App Store and Google Play numbers. Apps are matched to store listings by bundle ID, so the iOS and Android builds of one product end up in one project.
What you get
- MRR, Subscriptions and Trials: RevenueCat's MRR, active subscriptions and active trials charts, shown as the value at the end of the period.
- Revenue: gross revenue from the revenue chart, before store fees and taxes.
- Proceeds: revenue after RevenueCat's estimate of store commission and taxes.
- New customers: first-time customers per day.
- Numbers per app inside each project, refreshed hourly; RevenueCat marks the newest period incomplete until it closes.
| In Ertori | From RevenueCat |
|---|---|
| Revenue | Charts: revenue (gross) |
| Proceeds | Charts: revenue, proceeds |
| MRR | Charts: MRR |
| Subscriptions | Charts: active subscriptions |
| Trials | Charts: active trials |
| New customers | Charts: new customers |
Good to know
One key per project
RevenueCat secret keys are scoped to a single project, so four projects mean four keys and four sources. RevenueCat's OAuth would cover all projects at once, but third-party OAuth clients need manual approval from RevenueCat, so keys are the route that works today.
Choose V2 when you create the key
v1 keys don't work with the v2 API, and both start with sk_, so you can't tell them apart by looking. Pick API version V2, set Charts metrics and Project configuration to Read only and Customer information to No access. Only project Admins can create secret keys.
Expect small gaps against the stores
RevenueCat counts only receipts it has seen, converts prices to USD at the purchase-date rate and estimates taxes and commissions. Google counts trials as active subscriptions; RevenueCat doesn't. Charts use production data only and UTC days. Treat proceeds as a trend, not a tax figure.
Questions
- If I connect RevenueCat and App Store Connect, is revenue counted twice?
- No. Each metric on each platform is counted from one source. For app revenue RevenueCat comes first, ahead of App Store Connect and Google Play, while the stores still provide downloads, page views and reviews.
- What can the key see?
- With Charts metrics and Project configuration on Read only and Customer information on No access, it reads charts and the list of apps but no customer records, and it can't change products or offerings. It is stored encrypted and deleted with its data when you disconnect.
- RevenueCat also tracks my Stripe web purchases. Will that double up?
- It can. On the web, payment sources add up, because Stripe and Paddle on one project are normally different money. If RevenueCat already includes your Stripe sales, connect one of the two for that product, not both.
- Can I ask Claude about subscriptions?
- On Pro. Ask your Claude for MRR by app, which project gained the most trials this month, or how subscriptions moved after a release, and it answers from the same numbers the dashboard uses.