GOOGLE ADS & PAID LOCAL · September 2026 · ~11 min read
Google Ads scripts and automation worth using
For a small local account, automated rules do almost everything worth automating and require no code. Scripts are useful for three jobs: watching your budget, catching a broken landing page, and alerting you when conversions stop. Most of what sits beyond that is an agency demonstrating sophistication rather than saving you money.
On this page
- 01What should I automate first?
- 02What should I automate second?
- 03Why do automated pause rules keep pausing the wrong keywords?
- 04What is not worth automating in a small account?
- 05How do I judge a tool that claims to see more than the interface?
- 06Who maintains this after it is built?
- 07What to do this week
- 08When you do not need this
- 09Sources
- 10Related reading
- 11Questions about what to automate?
The distinction matters because the two get sold as the same thing. Automated rules are built into Google Ads, configured in a form, and available to anyone. Scripts are JavaScript that runs against your account on a schedule, and they need someone who can maintain them.
Maintenance is the part nobody mentions. A script that nobody owns eventually breaks after a platform change and fails silently, which is worse than no script at all.
01What should I automate first?
Alerts, not actions. Start by automating what you notice, not what you change.
The three highest value monitors for a local account are the same three every time.
Conversion drop alerts. If your account records no conversions for a day or two when it normally records several, something broke. Usually a tag lost in a website update. Without an alert you find out in three weeks, after spending three weeks blind.
Landing page checks. A script can request each landing page and email you if any return an error. Sending paid traffic to a broken page is the fastest way to waste money and the slowest thing to notice manually.
Budget monitors. An alert when spend passes a share of your monthly figure before a share of the month has passed. That is the mid-month cliff caught early enough to decide about.
Automate the thing you would be embarrassed to discover late. That is the whole selection criterion.
02What should I automate second?
Scheduled changes, because they remove the dependence on your memory during your busiest week.
Seasonal turn-on and turn-off dates. Budget increases timed to demand rather than to the day you noticed. Pausing campaigns for a holiday closure. All of these are built-in rules, no code, ten minutes each.
The one that pays for itself fastest is scheduling. Ads that run when nobody answers the phone buy calls you throw away. A rule that matches your ad hours to your coverage hours is trivial and most accounts do not have it.
Search term reporting can be automated too, and this is where a script genuinely beats the interface. A weekly email listing new search terms with cost above a threshold turns a task you forget into a task you skim. It does not replace reading the search terms report properly, but it means nothing expensive runs for a month unseen.
03Why do automated pause rules keep pausing the wrong keywords?
Because at local volume, a run of clicks with no conversions is completely ordinary, and a rule cannot tell ordinary from bad.
Here is the arithmetic that settles the argument, and it is worth doing once because every vendor selling you rule-based optimization is hoping you never do it.
Take a realistic conversion rate. LocaliQ, which publishes annual search advertising benchmarks under the WordStream name, puts the 2026 average conversion rate across all industries at 8.18%. Those figures are medians across a large campaign sample, LocaliQ sells advertising management, so treat that as a shape rather than your number. Call it roughly one conversion in twelve clicks.
Now ask what a healthy keyword looks like on a bad run. If a keyword truly converts at 8.18%, the chance it produces zero conversions across twelve clicks is 0.9182 multiplied by itself twelve times, which is 36%derived. More than one time in three, a perfectly good keyword will look dead after a dozen clicks.
Extend the window. Across 25 clicks, the chance of a healthy keyword showing zero conversions falls to 12%derived. Across 40 clicks it falls to 3%derived.
So a rule that pauses any keyword after 12 clicks with no conversion will, on average, kill roughly a third of your healthy keywords along with the genuinely bad ones. A rule set at 40 clicks kills very few. That is the whole design question, and it is one line of arithmetic: take one minus your conversion rate, raise it to the number of clicks, and read the answer as the probability you are about to make a mistake.
Rerun it with your own conversion rate. If your rate is lower than 8%, every threshold in that paragraph needs to be larger.
The same reasoning is why measuring conversion honestly when your traffic is small matters more than any automation you could install. It is also why split testing is out of reach for most local accounts, and the arithmetic there has the same shape as the arithmetic above. Sample size is a function of the metric's variance and of the effect you want to detect, not a fixed traffic number. At 95% confidence and 80% power the two-proportion constant is 2 × (1.96 + 0.84)², or about 16, and the conversions you need per variant is that constant divided by the square of the relative lift: 100 for a 40% improvement, 400 for 20%, 1,600 for 10%derived. A local account at 300 to 800 monthly visits and a 3% conversion rate produces nine to twenty-four leads a month, and reaches none of those.
The 10,000-visitor floor you have heard quoted deserves one sentence of provenance, because it gets quoted hardest at people running accounts exactly this size. It is not a study. It appears as reference [29] in Kohavi, Deng, Longbotham and Xu's KDD 2014 paper, where it resolves to Neil Patel, "11 Obvious A/B Tests You Should Try," QuickSprout, 14 January 2013, and the four Microsoft and LinkedIn authors qualify it on the spot: "the guidance should be refined to the metrics of interest." A blog post, promoted to an industry threshold by repetition.
04What is not worth automating in a small account?
Bidding, mostly, and anything that makes decisions for you at low volume.
Custom bid management scripts were valuable when manual bidding was the norm. Google's Smart Bidding now sets bids at auction time using signals a script cannot access, including device, location, time of day, browser and query context. Writing your own bidding logic to compete with that is a project with a poor return for a local advertiser.
That said, automated bidding has its own volume problem, and it is worth knowing before you switch strategies. Target CPA and similar strategies learn from conversions, and an account producing under a dozen conversions a month gives them very little to learn from. The honest sequence is conversion tracking first, enough volume second, automated bidding third. Skipping to the third is how accounts end up bidding confidently toward nothing.
Anything that acts on small samples is actively harmful, for the reason worked out above. Automating a decision you should not be making manually just makes the mistake faster.
Also, automation cannot see the parts of your marketing that are not in the account. Word of mouth, a truck people recognize, a yard sign in the right neighborhood. Those influence your search volume and your close rate without appearing anywhere Google can read, which is one reason offline presence still shows up in your results in ways no report will attribute.
05How do I judge a tool that claims to see more than the interface?
By asking what data it has access to, and by knowing the answer in advance for one specific class of claim.
Google's own guidance to site owners is unusually blunt on this point. In its documentation on optimizing for generative AI features, Google writes: "Be wary of third-party tools that promise ranking success or claim to use 'internal' Google metrics. No third-party tool has access to our internal ranking or AI systems." That sentence is about search rather than ads, and the principle transfers directly. A script or dashboard reads the same API your account exposes. It can read it faster, arrange it better and email it to you. It cannot see auction internals, and any vendor implying otherwise is selling a story.
What a good tool actually offers is time. It watches something you would forget to watch. Priced against the hours it saves, that is often a fair trade. Priced against a promise of proprietary insight, it is not.
06Who maintains this after it is built?
Whoever built it, or nobody, and nobody is the usual answer.
Ask this before agreeing to any script. Who owns it, where does the code live, what happens if that person leaves, and how will you know if it stops running. A script that emails you when something is wrong looks identical to a script that has silently stopped emailing.
Build a dead man's check into anything important. A weekly all-clear message is better than silence, because silence is ambiguous and an absent message is noticeable.
If you pay for management, ask what is automated and what is done by hand. This is a fair question about what your fee buys, and what management should cost depends heavily on what it covers. Automation that saves the agency time is not automatically a saving for you.
If you run the account yourself, the calculation is different. Every alert you set replaces a check you would otherwise have to remember, and what managing ads yourself actually takes drops considerably once the monitoring is handled.
07What to do this week
Set three automated rules in the Google Ads interface. No code required for any of them.
One, an email alert when account conversions for a day fall to zero. Two, an alert when spend crosses a threshold you choose partway through the month. Three, an ad schedule that matches the hours somebody answers your phone.
Then work out your own pause threshold using the arithmetic above, before you let any rule pause anything. Take one minus your conversion rate, raise it to the click count you were about to use, and see how often that rule would be wrong.
Then open each of your landing pages on a phone and confirm none of them error. If you have more than a handful, that is the point where a link-checking script is worth asking someone to set up.
Write down what you automated and where it lives. In four months, when an alert has not arrived in a while, you will want to know whether that means all is well or that something quietly stopped.
Be honest with yourself
When you do not need this
If you have one campaign, a small budget, and you log in weekly anyway, alerts add little. You are already the monitor.
If your account has no conversion tracking, do not start with automation. An alert about conversions requires conversions to be recorded. Fix the tracking first.
If somebody is proposing a package of custom scripts for a small local account, ask what each one will change about your results. Most of the answers will be about efficiency inside the account rather than customers in your calendar. That is not nothing, but it is rarely worth what it costs at this scale.
And if you are still deciding whether to advertise at all, none of this is your next step. Automation makes an account cheaper to run, not more likely to work. What decides that is whether the page and the phone behind the ad can carry the traffic, because paid search amplifies whatever they already do. Get those right first, even if it means waiting a quarter to start.
Sources
- Google Ads Scripts, product overview. Platform documentation for what scripts are, how they run on a schedule, and what account data they can reach.
- Google Ads Help, "Set up automated rules". Platform documentation for the no-code alternative to most scripts.
- Google Ads Help, "About Smart Bidding". Google's description of auction-time bidding and the signals it uses, which is the case against writing your own bid logic.
- LocaliQ / WordStream, "Search Advertising Benchmarks for Every Industry," 2026 edition, last updated 1 June 2026. The conversion rate used in the pause-threshold arithmetic. Vendor research; averages are medians. The 2025 edition of the series disclosed 16,446 US campaigns; the 2026 edition does not publish its sample.
- Google Search Central, "Optimizing your website for generative AI features on Google Search". Source of the quoted warning about third-party tools claiming access to internal Google metrics. Platform operator documentation.
- Kohavi, Deng, Longbotham and Xu, "Seven Rules of Thumb for Web Site Experimenters," KDD 2014. Peer reviewed, generalising from thousands of controlled experiments at Amazon, Booking.com, LinkedIn and Microsoft. Source of the principle that minimum sample size follows from the metric's variance and the sensitivity you want, and of the reference [29] trail back to the QuickSprout post of 14 January 2013. Desktop web-scale data, not local business data, as the authors say themselves.
Related reading
- Conversion tracking setup before you spend a dollar. The prerequisite for every alert described here, and the reason most conversion-drop alerts never fire.
- Budget pacing and why your ads stop mid-month. The specific problem the budget monitor is meant to catch, explained from the settings side.
- When a metric moves, telling signal from noise. The general version of the pause-threshold arithmetic, applied to every number in your reporting.
- Negative keywords and the money they save. The manual work the weekly search terms email is meant to prompt, and where the actual savings land.
Questions about what to automate?
Email me at eric@seod.com with the one recurring ads task that eats the most of your week, described in a sentence or two. I will tell you whether a built-in rule handles it, whether it needs a script, or whether it is a task you should stop doing entirely.
Third answer comes up more than you would think. It takes me five minutes and there is no pitch attached.
Or keep reading more on paid search for local businesses.