🧯 Troubleshooting
📖 2 min read📦 ResultsAiX ADs
- Error 400: redirect_uri_mismatch (Google): add the redirect address shown on the Google Ads tab, exactly, to your OAuth client in Google Cloud.
- Google says the project is on Test access, or "not approved" (HTTP 403): press Check my access on the Google Ads tab, then Apply for Explorer access in Google Cloud. Or connect with the Google Ads script instead, which needs no access level at all. With the script connected, ADs notices Test access by itself and lets the script do the work (campaigns, audiences list, conversions) until Google approves the project, then switches back.
- The analyst or the AI builder says Claude wants a different thinking setting: ADs now learns the right setting from Claude's own answer and retries straight away, so this fixes itself.
- The Google Ads script box is not green: open the script in Google Ads and press Run, and check Frequency is Hourly. Waiting jobs run on its next run. ADs emails you if the script has not reported for two days.
- Your Google account is not in the list, or shows no access: type its id in step 3, or give the connected Google login Admin access to that ad account in Google Ads.
- Customer Match refused: Google's reason is shown on the list. Usually the account needs more history or good standing.
- Meta Custom Audience terms: accept them once per ad account with the link on the Facebook & Instagram tab.
- A network refused the token: paste a new one on its card. Conversions resume on the next hourly run.
- A list "too small": networks need 100 to 1,000 matched people before they show ads to it.
- No sales showing: check Settings, Ad click tracking is on, and that your sales plugin is listed in "What I found".
- An Audience Vault list is missing: it needs the Vault to be on the same site; an older Vault shows only the segments it supports.
- The AI stopped: check Settings, AI budget and spend; the provider's own message is in Logs.