Connect your dataConnect RevenueCat
Project ID + a read-only V2 secret key — step by step, with the exact pages to open and the V1-vs-V2 trap explained.
RevenueCat is AdsBuddy's ground truth for money: subscription revenue, trials, and which purchases came from Apple Search Ads. It's the one required connection — without it, recommendations would be based on installs instead of revenue.
What you need
- The Project ID — starts with
proj. - A V2 secret API key with read access — starts with
sk_.
Step by step
- Open your projectGo to app.revenuecat.com/projects and open the project for your app.
- Copy the Project IDIn Project settings → General. It's also in the dashboard URL right after
/projects/. - Create a V2 secret keyIn Project settings → API keys, scroll to the API keys (v2) section and create a key with read access. Copy it — it starts with
sk_. - Paste both in AdsBuddyIn onboarding step 2, or later in Settings → Integrations → RevenueCat. You can paste them as fields or as one JSON blob:
{ "projectId": "…", "secretKey": "sk_…" }.
⚠️The common trap: RevenueCat also lists legacy V1“Secret API keys” higher up on the same page. AdsBuddy uses the REST API v2, so a V1 key is rejected at validation. Make sure you're in the API keys (v2) section.
What AdsBuddy reads
- Revenue, MRR, active subscriptions and trials (read-only).
- Apple Search Ads attribution on purchases — this is what powers the “which campaigns made real money” view.
- Monthly history, for seasonality charts and smarter plans.
Keys are validated against RevenueCat before saving (a bad key is rejected immediately) and stored encrypted. Each app uses its own project key — adding more apps later just means pasting one more key.