How to debug a Google Ads script with Claude
Let Claude read the failed run, find the cause and fix the script, without copying error messages around.
Debugging a script normally means opening Google Ads, finding the failed run, copying the error, pasting it into a chat, pasting the fix back and waiting for the next run. With the connector, Claude does the reading and the fixing itself.
The short version
Ask:
"ROAS Bid Adjuster failed last night. Find out why and fix it."
Claude then:
- looks up the script and its recent executions,
- reads the error message and which accounts failed,
- reads the current code,
- if needed, runs a read-only GAQL query to check the data the script depends on,
- saves a corrected version and tells you what it changed.
The fix is live on the next run. You do not touch Google Ads.
Getting better results
- Say what you expected. "It should have paused 12 keywords and paused none" is more useful than "it does not work".
- Mention recent changes. A renamed campaign, a new conversion action or a deleted spreadsheet is often the cause.
- Ask for the reasoning. "Explain the cause before changing anything" lets you catch a wrong diagnosis.
- Ask for a narrow fix. "Change only what is needed" keeps the diff small.
What Claude cannot see
Execution results reported to chiliad include status, duration, account and error message. The detailed Logger.log output stays in Google Ads; if the cause is not clear from the error, paste the relevant log lines into the chat.
Check the result
Open the script's Versions tab to compare the fix with the previous code, and watch the next run on the History tab. If the fix made things worse, restore the earlier version.