Project ID + a read-only V2 secret key — step by step, with the exact pages to open and the V1-vs-V2 trap explained.
Why this mattersRevenueCat turns recommendations into revenue decisions, not install or CPI guesses.
Where to paste itOnboarding step 2, or later in Settings → Integrations → RevenueCat.
What unlocksRevenue charts, country splits, campaign attribution, daily spend decisions, and better plans.
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_.
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.
Turn on the webhook (required for revenue charts)
The V2 key above pulls your aggregate totals (MRR, revenue, trials) on a schedule. But the dashboard's Overview, revenue trend, top apps/countriesand per-campaign attribution are built from individual transactions — those arrive through RevenueCat's webhook. Without it, those sections stay empty even though your MRR shows up elsewhere.
Open WebhooksIn RevenueCat: your project → Integrations → Webhooks → + New.
Copy the AdsBuddy valuesIn AdsBuddy, open Settings → Integrations → RevenueCat → RevenueCat webhook. Copy the URL, then click Generate token and copy the full Authorization header shown there.
Set the URLPaste https://adsbuddy.app/api/v1/webhooks/revenuecat.
Set the Authorization headerPaste the full header from AdsBuddy, including Bearer . The token is shown once; if you lose it, rotate it in AdsBuddy and update RevenueCat.
Send a test eventIn RevenueCat's webhook screen, use the test action if available. AdsBuddy will switch from Waiting for first event to Receiving once RevenueCat posts successfully.
Refresh app IDs if neededBack in Settings → Integrations → RevenueCat, use Refresh app IDs only if AdsBuddy says event routing is not ready. New purchases, renewals and trials flow in within minutes (no backfill of purchases from before the webhook was added).
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.