Google Ads · Automation

Google Ads Scripts: Which Ones to Run, and When a Script Is the Wrong Tool

Google Ads scripts explained, plus a decision grid: scripts vs automated rules vs a dashboard, which scripts earn a slot, and when to skip them.

VC
By Vitalii ChornyiKampaioNovember 19, 2026 · 10 min read

Google Ads scripts are JavaScript programs that run inside your account on Google's servers, on a schedule you set. They read performance data, change bids, budgets and statuses, and pull in outside data such as Sheets. They pay off for stable, mechanical rules, and lose to built-in tools elsewhere.

Quick answer: what Google Ads scripts are and when they pay off

Scripts run on Google's cloud at no additional cost, and only entry-level JavaScript is needed (Google Ads Scripts, Product overview, 2026). So the price tag is not the issue. The cost that matters is upkeep: someone has to own each script after it ships.

What Google Ads scripts can do, and the limits that decide fit

Scripts live under Tools > Bulk actions > Scripts and run V8 JavaScript.

What a script can touch

A script can manage campaigns, ad groups, keywords and ads, adjust bids, budgets and statuses, and run GAQL reports. It can read and write Sheets, call outside APIs with UrlFetchApp, and run across child accounts as a manager script.

On scheduling, Google's developer docs say "hourly, daily, weekly, monthly, or on demand", while the Help Center says "once, daily, weekly or monthly" (Google Ads Help, 2026). We keep the two lists separate.

Limits worth knowing before you write a line

30 min
single-account run time
60 min
manager scripts, only with executeInParallel and a callback
50
accounts in parallel per executeInParallel
50,000
entities: default cap per iterator (reports exempt)
250
authorized scripts per account
Source: Google Ads Scripts, Limits, updated 2026-11-16.

Two of these matter more than the numbers suggest. A timed-out script keeps its earlier work ("All of the changes made before the script was cancelled will be applied"), so a half-run write script leaves a half-changed account. And Google warns that "these limits can change at any time without warning."

Scripts, automated rules, a dashboard or the API: which to use

The right tool depends on the job, not the technology. Google itself splits the options into scripts, the API, BigQuery transfer, and rules, bulk uploads and Google Ads Editor (Google Ads Scripts, Product overview, 2026).

The decision grid

Kampaio Dashboard is our product. The other columns follow Google's own "right product" table; the dashboard column covers only what it does today.

JobScriptsAutomated rulesKampaio DashboardEditor, bulk upload, BigQuery
Alert on spend jump or stopped conversionsGood fitPossibleGood fit: built-in checksNot built for it
Change things by a rule on Ads data onlyGood fitGood fit: no-codePossible: no custom rulesPossible: manual
Change things using outside dataGood fit: Sheets, APIsNot built for itNot built for itNot built for it
Review search terms, add negativesGood fit: Sheet reportNot built for itGood fit: previewNot built for it
Edit budgets across many accountsPossible: no undoNot built for itGood fit: rollbackPossible
Bulk-edit many rows offlinePossibleNot built for itNot built for itGood fit
Pull reports into a warehousePossible: BigQueryNot built for itNot built for itGood fit

Scripts, rules and Editor columns follow Google's "Are Google Ads scripts the right product for me?" table (Google Ads Scripts, Product overview). The Kampaio Dashboard column describes the product as of November 2026.

In short: pick scripts if you need outside data or custom logic (scripts); no-code scheduled changes (rules); checks and previewed edits with no code to maintain (dashboard); offline bulk editing or a warehouse pipeline (Editor, bulk, BigQuery).

Pick by who will maintain it

Rules and dashboards are maintained by the vendor; a script by whoever wrote it. That makes ownership the real cost driver, and Google's own warning that limits can change without notice is the evidence. The cheapest script is the one nobody has to touch for a year.

The Watch, Report, Act ladder: which scripts earn a slot

Once scripts are the right tool, the next question is which ones. Watch and Report scripts earn a slot; Act scripts must clear a higher bar. The split follows what a script does to the account.

Watch
Risk: low (read-only)
Looks at the account and tells you.
Worst case
False alarm email
Run it if
You can name the condition
Example
No-conversions alert
Report
Risk: low (read-only)
Writes findings to a Sheet, changes nothing.
Worst case
Stale Sheet
Run it if
A human reads the Sheet
Example
Search-term mining
Act
Risk: high (writes, no undo)
Changes the account by itself.
Worst case
Wrong change at scale
Run it if
You pass the bar below
Example
Auto-pause

Watch: read-only alerts, run these first

Watch scripts only look and tell you: no-conversions and spend-spike alerts, a broken landing-page check. Nils Rooijmans, a script practitioner, calls the Google-published Broken Link Checker "the script I install the first day when taking over a new account" (Nils Rooijmans, 2024).

In one r/googleads thread (Nov 2025), a commenter described a no-conversions-in-the-last-two-days email alert built with ChatGPT's help that had "been solid really reliable". One commenter is not a survey. For the full alerting stack, see the anomaly-alert guide.

Report: search-term and conflict reports to a Sheet

Report scripts write findings to a Sheet and change nothing in the account; a human reads the Sheet first. Rooijmans on the negative-keyword conflict check: "It's very easy to make mistakes with negatives. It happens to me all the time." See our search terms report and negative keywords guides.

Act: scripts that write, and the bar they must clear

Act scripts (auto-pause, scheduled bid changes, auto-added negatives) must clear five conditions: Preview first, one named owner, a log review after each early run, a stop condition, and acceptance that there is no undo.

Aegis, our risk-review agent, is in development and does not run on live accounts. It would start from this line:

🛡️Aegis· Risk review
In developmentGoogle's own help page says, 'Keep in mind that changes to your scripts can't be undone.' I'd run any write script in Preview first and read the log before the first live run.Source: Google Ads Help, Using scripts to make automated changes, read 2026-11-19.

Preview is a rehearsal, not an undo: only AdsApp calls are simulated, so emails and Sheets writes still happen (Google Ads Scripts, Preview, 2026). Blocking a converting query is the typical failure, which is why auto-added negatives need the strictest review of the three.

When a script is the wrong tool

A script is the wrong tool in four situations. The Script Test asks: does the job need logic or outside data that no built-in feature has? Is the rule stable enough for one sentence? Does a named person own the script and read its logs? Is it read-only, or reversible enough to survive a partial run? Fewer than four yes answers: pick another tool from the grid.

1Does the job need logic or outside data that no built-in feature has?
No: pick another tool from the grid
↓ Yes: next question
2Is the rule stable enough for one sentence?
No: pick another tool from the grid
↓ Yes: next question
3Does a named person own the script and read its logs?
No: pick another tool from the grid
↓ Yes: next question
4Is it read-only, or reversible enough to survive a partial run?
No: pick another tool from the grid
↓ Yes
Four yes answers: a script is justified. Ship it with the five steps below.

Nobody will own it

A script nobody owns breaks silently: the alert never fires and nobody notices. If its author is disassociated from the account, "the script will stop running but remain available" (Google Ads Scripts, Authorization, 2026).

The rule needs judgment

Judgment calls do not fit in one sentence: is this term a customer or a researcher, is this dip seasonal. Run those as tests instead: see Google Ads experiments.

A built-in feature already does it

Google points people without scripting skills to automated rules (Google Ads Help, 2026). Do not script what a rule does. A dashboard check covers many standard failures too, as in this budget-not-spending diagnosis.

The script was written by AI and nobody read it

The r/googleads commenter's ChatGPT-assisted scripts were read-only alerts and reports. That supports the ladder (AI-written Watch and Report is low-risk), not AI-written Act scripts. Read any code before authorizing it: Google tells you to "click Authorize so the script can access the account on your behalf" (Google Ads Scripts, Get started, 2026). Free store scripts follow the same rule: free is not reviewed.

How to ship a script without breaking the account

If you decide a script is justified, three things fail silently: a timeout leaves a half-changed account, limits shift, and a script whose author lost access stops running.

  1. Pick the class and write the rule in one sentence. If it needs "it depends", stop.
  2. Preview before running. Tools > Bulk actions > Scripts > Preview, then read Changes and Logs.
  3. Authorize once, run it manually, read the log. Authorization is per script.
  4. Schedule it. Frequency per the developer docs or Help Center lists above.
  5. Read the first runs' logs, then set an owner and a review date. Check for a timeout.

If the job is a previewed edit with a rollback rather than custom code, Kampaio Dashboard covers it. Free during early access.

Where Kampaio Dashboard fits next to scripts

Kampaio Dashboard covers the repeatable checks and edits most accounts script first, with a preview and a rollback. It does not run custom code and does not pull external data such as inventory feeds, weather or Sheets, so it does not replace a script that needs them.

Today it offers all your Google Ads accounts on one screen; 14 automatic campaign checks (spend without conversions, campaign stopped, spend spike, conversions gone and more); a search-terms report with negatives and preview; a Shopping/PMax product audit; budget, target, status, geo and keyword edits with preview and rollback; and a change log.

The contrast with scripts is plain: per Google, a script's changes can't be undone, while a dashboard edit shows a preview and can be rolled back. AI agents, Aegis among them, are in development. For tool comparisons, see Google Ads management software and Google Ads optimizer software compared.

Frequently asked questions

What are scripts in Google Ads?

Scripts are JavaScript programs that run inside a Google Ads account on Google's servers, on a schedule you choose, reading data and changing bids, budgets and statuses.

Are Google Ads scripts free?

Yes. Google says scripts run on its cloud infrastructure at no additional cost (Google Ads Scripts, Product overview, 2026). The cost is the time to write and maintain each one.

Do I need to know how to code to use Google Ads scripts?

Only entry-level JavaScript, according to Google (Google Ads Scripts, Product overview, 2026). Prebuilt templates exist, and AI can draft code. Either way, read any script before you authorize it, because authorization gives it access to your account.

Can I undo what a script changed?

No. Google Help states that "changes to your scripts can't be undone." Preview is a rehearsal, not a rollback, and a timed-out script keeps the changes it made before cancellation.

How often can a script run, and how long can it run?

A single-account script can run 30 minutes; a manager script 60 minutes with executeInParallel and a callback (Google Ads Scripts, Limits, 2026). Developer docs list hourly through monthly schedules; the Help Center lists once, daily, weekly or monthly.

Scripts or automated rules: which should I use?

Use automated rules for no-code scheduled changes on Google Ads data, and scripts for outside data or custom logic. Google recommends rules to people without scripting skills (Google Ads Help, 2026).

Where can I find Google Ads scripts examples?

Start with Google's script library and Examples pages, then Nils Rooijmans' shortlist. Read any code before authorizing it.

Next step: check your account before you script it

Run the Script Test on one job you were about to script. If it fails, a built-in check may cover it. Open Kampaio Dashboard and see which of the 14 campaign checks already flag your accounts. Free during early access.

Before scripting anything, run the PPC audit checklist and read Google Ads optimization.

See which checks already cover your accounts

Connect your Google Ads accounts and run 14 automatic campaign checks on one screen.

Open the dashboard

Free during early access.

Sources:

  1. Google Ads Scripts, Product overview: https://developers.google.com/google-ads/scripts/docs/start
  2. Google Ads Scripts, Limits (updated 2026-11-16): https://developers.google.com/google-ads/scripts/docs/limits
  3. Google Ads Scripts, Preview: https://developers.google.com/google-ads/scripts/docs/concepts/preview
  4. Google Ads Scripts, Authorization: https://developers.google.com/google-ads/scripts/docs/concepts/authorization
  5. Google Ads Scripts, Get started: https://developers.google.com/google-ads/scripts/docs/getting-started
  6. Google Ads Help, Using scripts to make automated changes (188712): https://support.google.com/google-ads/answer/188712?hl=en
  7. Google Ads Help, Automated rules: https://support.google.com/google-ads/answer/2472779?hl=en
  8. Nils Rooijmans, "What Google Ads scripts should I be using?": https://nilsrooijmans.com/google-ads-scripts-faq/what-google-ads-scripts-should-i-be-using/

Keep reading