Skip to main content

Troubleshooting onboarding issues

Missing data right after setup​

No campaigns​

  • Apple Ads integration may be disabled or still syncing
  • Campaign scope may exclude all campaigns (check app and match_app_store_id / include-exclude lists)

No RevenueCat revenue​

  • Verify webhook URL matches RevenueCat endpoint config
  • Confirm webhook payload app_id (if present) matches configured RC app id
  • Ensure events are not rejected by app-level security in RC

No recommendation output​

  • Recommendations are muted when freshness gates fail
  • Check that required integrations report healthy data for the selected window
  • Review target thresholds (ROAS/conversion minimums can suppress all actions)

Common API/ingest failures​

404 from RevenueCat webhook URL​

Usually means the token has not been configured for the app or was rotated.

401 on webhook app-id checks​

Re-check that payload app id and configured rc_app_id match exactly.

First-party key missing​

If public_api_key_status is missing, rotate a key and wire it into your backend.

If webhooks are intermittent​

  1. Send one signed test event
  2. Confirm POST /webhooks/revenuecat/{token} returns status: ingested
  3. Check app settings and integration logs
  4. Verify app is still enabled in SpendDaddy and RevenueCat settings

If the issue persists, use manual logs from your deployment layer and check api.spenddaddy.app/healthz.