Debug before you panic. Use Google Ads' built-in debugging tool to diagnose issues.
In your MCC Script area (Google Ads UI → Tools → Scripts), you'll see two buttons: “Run” and “Preview”.
The logs display in real-time as the script executes. You'll see exactly which accounts are processing, what data is being pulled, and where failures occur. No waiting for the script to finish, then discovering it failed on account #1 of 15.
Script errors happen. API limits, permission issues, configuration mismatches, Google Ads platform changes. The difference between a 5-minute fix and a 2-day troubleshooting nightmare is the quality of information you provide.
Response time: One business day typical, often much faster. The better your logs, the faster I can diagnose and provide a fix.
Each line in the logs shows:
When you send me these logs, I can see exactly where the process breaks down. Maybe it's a permission issue on account 3 of 10. Maybe the folder ID doesn't match. Maybe an API quota was hit. The logs show everything.
If the script runs successfully for some accounts but fails on others, copy the logs for both successful and failed runs. Comparing the two makes diagnosis much faster.