In short: a script is JavaScript that Google runs inside your own account, with your permissions: it reads any report, writes changes, fills spreadsheets and sends emails. It has clear limits (30 minutes per run, once an hour) and you don't need to code to use one. Scripts fill the gap Google leaves: watching, cleaning, excluding, cross-checking and alerting.
The same sentence has come up throughout this whole course: "a script does this every night". This last module of the Intermediate level explains exactly what that is, what it can do and how you put one to work in an account — without writing a line of code.
What is a Google Ads script?
A Google Ads script is a JavaScript program that you paste into Tools and settings → Bulk actions → Scripts and that Google runs for you, inside your account, with your user's permissions. It does not run on your computer or on an external server: it runs on Google's infrastructure, with direct access to campaigns, ad groups, keywords, ads, reports, budgets and bids… and to Google Sheets and email.
Think of it as an employee who logs into the account every night with a list of precise instructions, reads the reports, makes decisions according to rules, writes the outcome into a spreadsheet and emails you if there is anything you need to see.
What can a Google Ads script do?
| Read | Write | Communicate |
|---|---|---|
| Any report (GAQL): search terms, placements, hour-of-day performance, auction data… | Pause/enable campaigns, ad groups, keywords, ads | Write to Google Sheets (dashboards, history) |
| The account's full structure | Change budgets, bids and bidding strategy targets | Send emails (alerts, reports) |
| The state of conversions, quality, IS | Add/remove negatives, placement exclusions, audiences | Call external services (APIs, AI) |
| Historical metrics by day | Create campaigns, ad groups, ads, keywords | Read configuration sheets that you edit |
What can't a script do?
- Run for more than 30 minutes per execution (60 in some manager account scripts): long jobs are split into batches.
- More than one scheduled run per hour per script.
- Access data your user cannot see.
- Some interface resources are not exposed to scripts (or arrive late): certain PMax reports, the full auction insights, some new features.
- Replace judgement: a script does what its rules say, exactly, every night — including whatever is wrong in those rules.
How do you install and schedule a script?
- Tools and settings → Bulk actions → Scripts → +: you paste the code and give it a name.
- Authorise: Google asks for permission for the script to act in the account (and in sheets/email if it uses them). You grant it with your user.
- Preview: it runs without applying changes, leaving a log of what it would have done. That is how you test.
- Run it manually, or schedule it: hourly, daily at a set time, weekly, monthly.
- Logs: every run leaves a log of what it did and any errors. The account's change history flags whatever the script did.
What is the difference between an account script and an MCC script?
- Account scripts: they live in one account and act on it.
- Manager account (MCC) scripts: they live in the MCC and walk through the linked accounts on every run — a single one can watch 30 accounts — with an extended time limit and parallel execution. This is the professional way to run a portfolio: the code lives in one single place and the accounts never see it.
Why are scripts worth using?
Google automates what suits Google (bids, combinations, splitting across networks) and leaves unautomated what suits you: watching, cleaning, excluding, cross-referencing data with your business, alerting. Scripts are the only tool that fills that gap with first-hand access to the account, without paying for an external platform or handing credentials to a third party, and with the power of a full programming language. In the hands of someone who can write them, they are the cheapest multiplier there is; for those who do not program, there are ready-written suites.
💡 Ninja trick: the whole Ninja Scripts Suite is made of Google Ads scripts: each one reads what the interface hides, applies rules that you configure in a spreadsheet, writes the results into that spreadsheet and alerts you by email. They run in your account (or in the MCC) as your user, and nothing they do leaves Google except what you choose to send to an external service (the AI, for example). The next lessons explain what each one solves and how they are installed.
What you should remember
- A script is JavaScript that Google runs inside your account, with your permissions.
- It reads any report, and writes to the account, to spreadsheets and by email.
- Limits: 30 min per run, one run per hour, some resources not exposed.
- Preview to test; scheduling to operate; the MCC for fleets.
- They fill the gap Google leaves: watch, clean, exclude, cross-reference, alert.