Connect RevenueCat

RevenueCat sends SpendDaddy the subscription revenue and lifecycle events that recommendations are scored against. SpendDaddy connects through RevenueCat OAuth, so you do not need to create or paste a RevenueCat secret API key.

Authorize SpendDaddy

1. In SpendDaddy, open Add app and choose RevenueCat under Revenue events.
2. Select Connect RevenueCat.
3. Sign in to RevenueCat if prompted.
4. Grant SpendDaddy access to the projects that contain the apps you want to add.
5. Return to SpendDaddy and wait for the RevenueCat connection to show Valid.
6. Select Review apps, pick the matched app, and adjust its name if needed. SpendDaddy suggests the RevenueCat project name.

SpendDaddy requests these RevenueCat permissions and no others:

RevenueCat permission	Why SpendDaddy needs it
project_configuration:projects:read	Find the projects available to the connection.
project_configuration:apps:read	Discover apps and confirm their bundle IDs.
project_configuration:integrations:read_write	Find or create the app-scoped webhook.
charts_metrics:charts:read	Import recent revenue history per Apple Ads keyword from RevenueCat Charts.

App discovery skips any project you did not grant to the OAuth connection. If the intended app is missing, reconnect RevenueCat and grant access to its project.

Token handling and revocation

RevenueCat returns a one-hour access token and a rotating refresh token. SpendDaddy encrypts both at rest and refreshes them on the server. Neither token reaches the browser or the app configuration.

To disconnect SpendDaddy, revoke its OAuth connection in RevenueCat Account → Security → Active OAuth tokens. Reconnect from SpendDaddy before the current authorization expires if you still need RevenueCat access.

Webhook setup

SpendDaddy creates the app-scoped RevenueCat webhook automatically during app creation. If automatic setup fails, SpendDaddy displays a tokenized URL in this form:

https://api.spenddaddy.app/webhooks/revenuecat/<token>

Open the matching RevenueCat project, add a webhook integration for the matched app, and paste that URL. The URL is unique to the app. Treat it as a secret. If you rotate it later in Settings → Connections, replace the old URL in RevenueCat right away, because the old URL stops working.

Historical data

The webhook only sends new events. SpendDaddy fills in history in two ways.

RevenueCat Charts (automatic). Right after the app is created, SpendDaddy imports cohort proceeds for the previous 90 days from RevenueCat Charts, per Apple Ads campaign, ad group, and keyword. Overview shows an import screen while this runs, and SpendDaddy emails you when your first numbers are ready. Charts are rate-limited, so large accounts can take longer. Keywords that RevenueCat Charts cannot match stay without imported history.

Transactions export (recommended). For complete history beyond 90 days, and for refunds and corrections, upload a RevenueCat Transactions scheduled export. Until a period has revenue history, SpendDaddy does not propose cuts (lower bid, pause keyword, lower budget) that rely on it, and past proceeds and ROAS may be understated.

1. In RevenueCat, open the matching project and follow the Scheduled Data Exports setup guide.
2. Create a scheduled export to email or cloud storage, enable the Transactions feed, and choose CSV format. Use a full export for the initial backfill; an incremental file alone may omit older transactions.
3. Allow up to 24 hours for the first delivery. Download the CSV or CSV.GZ file.
4. Upload it in the last step of Add app, or later in Settings → Connections → RevenueCat → Historical RevenueCat data.

SpendDaddy recalculates metrics after the upload. The export can be skipped during app setup, but historical ROAS should not be relied on until it arrives.

Validation checklist

• RevenueCat shows SpendDaddy under Active OAuth tokens.
• The OAuth connection includes the project containing the intended app.
• SpendDaddy shows the intended RevenueCat project and app during matching.
• RevenueCat webhook setup reports success, or the manual webhook URL has been added to the matched app.
• Revenue figures appear on Overview and in Needs attention.

RevenueCat documents the authorization flow, scopes, token lifetime, and revocation in its OAuth guide.