On this page
Scripts, automated rules or the API
Google Ads gives three ways to automate. Automated rules are point-and-click for simple conditions, such as pausing an ad group when cost per conversion passes a number. Scripts are JavaScript in the browser for custom logic. The API is for software outside Google Ads and takes more engineering.
Scripts sit in the middle: more flexible than rules, simpler than the API. They suit one-person and agency teams. They can run in a single account or, from a manager account, across many. See Google Ads MCC.
Google also has built-in options such as bid strategies and scheduled changes. Automated bidding is the largest piece of automation most accounts use, so learn it before you write code. See Google Ads bidding strategies.
There is also a third level of automation in the account: automated bidding and the recommendations Google proposes. Those run on Google’s side and need monitoring, not code. See auto-applied recommendations before you let them apply on their own.
Pick a first job
Good first scripts are read-heavy and low risk: check final URLs for errors and email a list, send a daily spend and conversions summary, alert when spend is zero or far above pace, or write a search terms export to a sheet. These deliver value without changing anything.
Once they run reliably, move to scripts that make changes: adding negatives from a list, pausing ads that fail a rule, or adjusting budgets from a spreadsheet. Keep changes small and logged. Ad spend pacing is a natural fit for the alerts.
Write each script to do one thing, name it clearly, and put a comment at the top saying what it does and who owns it. Six months later, that comment is what keeps it from being deleted or trusted blindly.
Do not automate a decision you do not yet understand. If you cannot say by hand when a keyword should be paused, a script will pause the wrong ones faster. Do the job manually for a few weeks, write the rule down, and then encode it.
Want this on a schedule?
Runs recurring checks on a schedule you set. Every change waits for your approval.
Write, preview and authorize
Open Tools, then Bulk actions, then Scripts, and create a new script. Reports use Google Ads Query Language through the AdsApp search method, and helpers such as UrlFetchApp, SpreadsheetApp and MailApp reach the web, sheets and email.
Use Preview first. A preview runs the logic without applying changes and shows the log. Then authorize the script when prompted, and run it for real. Start with a copy of the sample scripts Google provides, and edit from there.
Test on a small, low-stakes account or a single campaign first. If you run an agency, try a script on one client before rolling it out across a manager account, since a mistake there repeats across every account it touches.
Schedule it and know the limits
Set a frequency: hourly, daily, weekly or monthly. Scripts have execution time limits, so process data in batches and avoid scanning every row when a filter will do. Check the current documentation for quotas that apply to your account.
Turn on email notifications for failures and read the logs. A script that fails silently is worse than none, because you think a check is running.
Keep scripts short and well commented. Google’s documentation lists the current limits on run time, calls and records. Check it when a script stops finishing, since a script that processes a growing account may start hitting the ceiling.
Scripts worth writing first
A broken-link checker loops through your ads and keywords, fetches each final URL and emails you any that return an error. It protects spend from sending people to dead pages, and it is a short script.
A spend alert compares today’s cost so far with a threshold or with the same time yesterday, and emails you if it is far off. It catches a budget error or a stopped campaign within hours rather than at month end.
A search terms exporter writes new terms with cost and conversions to a sheet each week, ready for review. It does not change anything, so it is safe, and it makes the manual job faster. A negative keyword script can then add terms from a reviewed list.
Keep it safe
Keep scripts that edit your account conservative: cap how many items one run may change, log every change, and review them weekly. Use the change history to see what ran. Pair automation with human review for budgets and bids.
If you would rather not maintain code, Sprites reads and edits Google Ads accounts, including search terms, negatives, budgets and keywords, and can run checks on a schedule. Every change is proposed as an approval card first.
Add a dry-run flag at the top of every script that makes changes. When it is on, the script logs what it would do and changes nothing. You can switch it off once the logs match what you would have done yourself.
Questions
What are Google Ads scripts?
JavaScript programs that run inside a Google Ads account to read data, make changes and send results by email or to a sheet. They need no server of your own.
Do I need to code to use Google Ads scripts?
Some JavaScript helps, but you can start by adapting Google’s sample scripts. For simple conditions, automated rules need no code at all.
Are Google Ads scripts free?
Yes. They are a built-in feature of Google Ads. You pay only your ad spend, plus whatever you pay if you connect to outside services.
What can I automate in Google Ads?
Reports, alerts, URL checks, negative keywords, budget and status changes, and bid adjustments from a sheet. Review risky changes before they apply.