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
- Open the script in chiliad and edit the code.
- 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.
- 1
Tabs for the code, variables, version history, execution history and assigned accounts.
- 2
Switch between your Script Code, the Loader to paste into Google Ads, and the Analytics snippet.
- 3
Save publishes immediately: accounts pick up the new code on their next run. The amber dot means unsaved changes.