Skip to main content

Verify first-run health

Run through this checklist right after you add an app.

1. Connections​

Open Settings → Connections for the app and confirm:

  • Apple Ads is enabled and authorized.
  • RevenueCat is connected, or the SpendDaddy API key is stored on your server.
  • App Store Connect is enabled, if you configured it.
  • No connection reports a missing credential.

2. Data​

Overview shows an import screen until the first Apple Ads and RevenueCat imports finish; SpendDaddy emails you when they do. Then check:

  • Campaigns lists your active Apple Ads campaigns.
  • Overview shows impressions, spend, and installs, where permissions allow.
  • Needs attention lists proposed changes, or says that none are needed.

3. Webhook​

  • Send a test delivery from RevenueCat.
  • Confirm that RevenueCat reports a successful response.
  • If deliveries fail, rotate the webhook in Settings → Connections and replace the URL in RevenueCat.

4. Targets and first changes​

  • Confirm that the expected campaigns appear.
  • Review your CAC and ROAS thresholds in Settings → Targets.
  • Read the evidence and budget impact of each proposal before applying it.
  • If you enable an agent execution policy, leave Autopilot mode on Shadow at first. It records what it would change and changes nothing. Check Activity and the Autopilot track record before you consider Live.

If any check fails, work through Troubleshooting before you apply changes or give an agent write access.