Skip to main content

Troubleshooting

  • Cause: Developer token access level, non-MCC account, or endpoint not enabled
  • Fix: Use test manager + client accounts or apply for Basic/Standard access; verify developer token approval
  • Backend logic returns demo/guidance entries when 501 occurs

Missing Authorization/Org Headers​

  • Symptom: 401 on backend routes; account creation fails
  • Fix: Use apiClient in frontend so Firebase Bearer and x-organization-id are added automatically

404/401 on Google Ads API​

  • Ensure request includes:
    • Authorization: Bearer <OAUTH2_ACCESS_TOKEN>
    • developer-token: <GOOGLE_ADS_DEVELOPER_TOKEN>
    • Content-Type: application/json

Redirect URI Mismatch​

  • Ensure provider consoles have redirect URIs matching deployed hosts and backend routes
  • Google Ads backend callback is /api/google-ads/auth/callback; if proxying via app.ostenai.com, ensure path maps correctly