Skip to main content

Troubleshoot setup

Start with Settings → Connections for the affected app. It shows which connection needs attention without revealing credentials.

The overview still shows the import screen​

  • The first Apple Ads and RevenueCat imports usually finish in a few minutes. RevenueCat Charts are rate-limited, so accounts with many keywords take longer.
  • SpendDaddy emails you when your first numbers are ready.
  • If the import failed, the screen says so. Reconnect the affected service in Settings → Connections.

Campaigns do not appear​

  • Confirm Apple Ads shows as connected.
  • Check that the authorized Apple Ads user can see the expected organization.
  • Confirm that the campaigns promote the app selected during setup. SpendDaddy assigns campaigns by App Store ID.

Revenue does not appear​

RevenueCat​

  • Confirm RevenueCat shows as connected in SpendDaddy.
  • If the intended app is missing during setup, reconnect RevenueCat and grant access to the project that contains it.
  • If RevenueCat authorization was revoked or expired, select Reconnect RevenueCat and authorize it again.
  • Send a test webhook from RevenueCat and check that RevenueCat reports a successful delivery.
  • Make sure the webhook is configured for the same RevenueCat app you connected in SpendDaddy.
  • If the URL may be stale, rotate the webhook in Settings → Connections and replace it in RevenueCat.

SpendDaddy API​

  • Send events from your backend, not directly from a mobile app.
  • Confirm the request uses the API key for the correct SpendDaddy app.
  • Include a positive amount and the correct currency for purchases, renewals, conversions, and refunds.
  • Check the status code against the event API guide.

Needs attention is empty​

  • Wait for campaign and revenue data to finish the first refresh.
  • Check Overview for import failures or data warnings.
  • Review your thresholds in Settings → Targets. A high minimum spend or strict CAC and ROAS targets can leave nothing to propose.
  • For RevenueCat apps, cuts (lower bid, pause keyword, lower budget) wait until SpendDaddy has revenue history for the period. Upload a RevenueCat Transactions export in Settings → Connections → RevenueCat to fill gaps. See Historical data.
  • An empty list can be correct when the evidence does not support a change.

The autopilot didn't do anything​

Open Activity, set Show to Autopilot, and read the reason on each row. The Autopilot track record in Settings → Agents also lists why picks were skipped. Common causes:

  • Autopilot mode is Off, or it is Shadow. Shadow records what it would do and changes nothing. See Autopilot.
  • The execution policy is not enabled, or it has expired. The autopilot only runs on an enabled, unexpired policy.
  • The campaign or action is outside the policy ("Outside your policy"), or a bid or budget limit stopped it.
  • "Daily action limit reached": the policy's daily limit was used up.
  • "Apple Ads changes are switched off": your organization does not allow Apple Ads changes. An owner can allow them again in Settings → Agents → Apple Ads changes, which asks for a confirmation. While changes are off, Undo on a guarded change still works.
  • "Apple Ads changed since the review": SpendDaddy skips a change when the live state differs from what the review saw.
  • "Paused after a backfired raise" or "Earlier raises had no effect": past outcomes hold back raises on that keyword or campaign.
  • "The evidence had expired": the recommendation was too old to act on.
  • No recommendation of a supported kind (bid, keyword pause, or daily budget) came out of the daily review.

A recommendation I dismissed came back, or one is missing​

  • A dismissal hides that recommendation for 14 days. Wrong intent hides it for 90 days and Already handled for 30.
  • Open the Memory tab of the campaign or placement to see what is held back and until when.
  • After a raise backfires, or after two raises with no effect, raises on that keyword or campaign are held back. See How SpendDaddy learns from outcomes.

App Store Connect metrics do not appear​

  • App Store Connect is optional. If you skipped it during setup, add it in Settings → Connections.
  • Confirm the Team key has the Admin role so SpendDaddy can create the Analytics Report request.
  • Apple takes about 24–48 hours to generate the first report after setup. See Connect App Store Connect.
  • Apple reports can arrive later than Apple Ads data or revenue events.
  • SpendDaddy keeps using Apple Ads and revenue data while this connection is unavailable.

A credential was rotated​

  • Replace the old credential everywhere it was used.
  • Rotating the RevenueCat webhook, the SpendDaddy API key, or an agent key invalidates the previous value immediately.
  • RevenueCat OAuth tokens rotate automatically; reconnect only after revocation, expiration, or when changing project access.
  • Return to Settings → Connections and confirm the connection is ready.

If the problem continues, contact the SpendDaddy team with the app name, affected connection, approximate time, and the user-visible error message. Never include private keys, API keys, or complete webhook URLs.