AppCradle

Integration setup

Connect RevenueCat without double-counting subscription income

RevenueCat adds a subscription-focused view to your workspace. Its figures can describe purchases already present in store reports, so the integration keeps those sources separate.

By AppCradle Updated

Two translucent report panels flow into a single blue revenue chart.

The key idea

Use RevenueCat to understand subscription health. Do not add its revenue or subscriber counts to overlapping store totals.

1. Prepare read access

Your apps must already send purchases to RevenueCat. Create a V2 secret API key with project_configuration:projects:read, project_configuration:apps:read and charts_metrics:charts:read permissions. A public SDK key cannot be used for this reporting connection.

A company owner or administrator can verify the key in Settings → RevenueCat and select a project. Repeat for additional projects; each retains its own report.

RevenueCat: API access and permissions

2. Select apps and start the first import

Choose supported iOS and Android apps, optionally confirm store-app mappings, then select Save apps. Mapping is informational; AppCradle does not match purchases across providers or merge projects by app name.

Open Settings → Imports and choose Start first import. The worker loads the last 90 completed UTC days. Follow progress there, retry failures, or refresh manually without waiting for the automatic daily update.

  • Use a secret V2 read key.
  • Save your selected apps.
  • Start the import in Imports.
  • Check the reporting dates and publication time.

3. Read snapshots and period totals correctly

Statistics → RevenueCat offers 7, 15, 30 and 90 completed days, with 15 selected by default. MRR, active subscriptions and trials are snapshots at the final reported date. Revenue and refunds cover the selected period only when its daily data is complete.

MRR is a monthly run rate, not a payout. New paid subscriptions can include resubscriptions and product changes, so they are not unique new users. Supported conversion and churn measures remain daily provider rates rather than averaged percentages.

Unavailable charts and missing dates remain unknown. If a refresh fails, the previous published report stays available; check its publication time before using it.

4. Keep overlapping sources separate

Overview adds a Subscription health summary for each project with MRR, active trials, new paid subscriptions and refunds. These figures do not change consolidated store revenue or subscriber totals.

Compare definitions, dates, currency and app scope when checking RevenueCat against stores. Differences alone do not prove an import error, and estimated proceeds should not be treated as bank payouts.

RevenueCat: reporting differences

Bring your revenue reports together.

Explore revenue and subscriptions in one workspace, with visibility into report coverage. Free during early access. No payment details required.

Keep exploring

All guides

Revenue workflow

How to track AdMob and subscription revenue together

Build an app revenue view with store proceeds and estimated ad earnings, while keeping currency, dates, report coverage and overlapping totals clear.

Read guide

Troubleshooting

Why app revenue numbers differ across dashboards

Investigate app revenue discrepancies with a checklist for metric definitions, dates, currencies, refunds, report coverage, and app filters.

Read guide