πŸ€–chiliad
ClaudePricing
Help CenterScripts and deployment

How to update a Google Ads script in every account at once

Why pasted scripts drift apart, and how to change a script once and have all accounts use the new version.

A script pasted into Google Ads is a copy. Twenty accounts mean twenty copies, and every bug fix or improvement has to be made twenty times. Sooner or later they stop being the same script.

Hosting the code once

The fix is to keep a single copy of the code outside Google Ads and have each account load it when it runs. That is what the chiliad loader does: the snippet in Google Ads stays the same, and it downloads the current code on every run.

Updating a script

  1. Open the script in chiliad and edit the code.
  2. Click Save.

That is the whole procedure. Every account that runs the script β€” whether its loader sits in the client account or in a manager account β€” picks up the new code on its next run. You do not open Google Ads.

Doing it safely

  • Test first. Duplicate the script, assign the copy to one account and run a preview there before changing the original.
  • Use versions. Every save is stored. If the new code misbehaves, open the Versions tab and restore the previous one; the rollback applies on the next run as well.
  • Watch the next runs. The run history and failure alerts tell you quickly whether the change worked everywhere.

Changing a setting instead of the code

Often what needs to change is a value β€” a threshold, an email address β€” not the logic. Change the variable's default to affect every account, or override it for one account in the Configure table. Values, like code, apply on the next run.

The one case that needs Google Ads

If the new code uses a Google service the script did not use before, copy the loader again and re-authorize it. Google only asks for permissions it can see in the pasted code.

app.chiliad.io/scripts/budget-pacing-monitor

Budget Pacing Monitor

Enabled
ScriptVariables (3)VersionsHistoryAccounts (3)
1
Script CodeLoaderAnalytics
2
3Save*
var MONTHLY_BUDGET = 5000;
var ALERT_EMAIL = "you@example.com";

function main() {
  var spend = AdsApp.currentAccount()
    .getStatsFor("THIS_MONTH").getCost();
  if (spend > MONTHLY_BUDGET * 0.9) notify(spend);
}
  1. 1

    Tabs for the code, variables, version history, execution history and assigned accounts.

  2. 2

    Switch between your Script Code, the Loader to paste into Google Ads, and the Analytics snippet.

  3. 3

    Save publishes immediately: accounts pick up the new code on their next run. The amber dot means unsaved changes.

Part of the guideScripts and deployment

More on this topic

  • How to add a script to Google Ads
  • How Google Ads script authorization works
  • How to schedule a Google Ads script
  • Preview vs Run in Google Ads scripts: what is the difference?
  • Google Ads script limits: execution time, accounts and quotas
  • How to run one Google Ads script on multiple accounts
  • How to use different script settings for each account
  • How to roll back a Google Ads script to an earlier version
  • How a Google Ads script is structured: main(), settings and helpers
  • How to use Google Sheets from a Google Ads script
  • How to send email alerts from a Google Ads script

Still stuck?

Send us a question from the help center β€” we read every message.

Ask a question
πŸ€–chiliad

The platform for managing and automating Google Ads scripts at scale. Built for PPC agencies and freelancers.

chiliad β€” Google Ads Script Management - Monitor and manage Google Ads scripts across every account | Product Hunt

Product

  • Use Cases
  • Features
  • Claude connector
  • Pricing
  • Marketplace
  • Blog
  • About
  • Roadmap
  • Changelog

Support

  • Contact Us
  • Help Center
  • Terms of Service
  • Privacy Policy

Β© 2026 chiliad. All rights reserved.