Skip to main content

Connect RevenueCat

RevenueCat supplies subscription revenue and event signals used in recommendation scoring.

Required inputs​

  • RevenueCat API key
  • (Optional at setup) RevenueCat app identifier is discovered from project context and saved as rc_app_id

Webhook setup (mandatory for live)​

During app creation SpendDaddy generates a tokenized URL in this form:

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

This URL is unique and should be configured in each RevenueCat app.

Important:

  • The token is shown once at creation.
  • Store the token output where your team can rotate it intentionally.
  • Token mismatch or unknown token returns 404 from the webhook.
  • If the payload includes event.app_id, it must match your configured app id.

Polling behavior​

  • poll_on_run_hourly is initially disabled for live runs.
  • Live revenue is expected from RevenueCat webhooks.
  • Use historical backfill/import when you need legacy data.

Historical data backfill​

For historical RevenueCat CSVs:

  • Use the app setup/import flow that supports CSV and .csv.gz.
  • If you have a large historical gap, run an admin import and wait for refresh.

Validation checklist​

  • RevenueCat integration shows api_key_status: stored and webhook_token_status: stored_hash
  • /webhooks/revenuecat/<token> returns status: ingested on test payloads
  • Recent revenue-based tiles populate in overview and recommendation views