Why use a loader instead of pasting the script into Google Ads?
What the chiliad loader is, what it does on each run, and how it differs from pasting full script code.
When you paste a full script into Google Ads, that account holds its own copy of the code. A loader replaces the copy with a few lines that fetch the code at run time.
What the loader does on each run
- Downloads the current version of your script from chiliad.
- Applies the values set for this account, on top of the script's defaults.
- Runs the script.
- Reports the result — success or error, duration, account — back to chiliad.
At manager level it first asks chiliad which accounts the script is assigned to, and runs only those.
What that changes for you
- Updates are instant. Save a fix in chiliad and every account uses it on its next run. Nothing to re-paste.
- Settings live outside the code. Changing a client's budget threshold is a cell in a table, not an edit in Google Ads.
- You can see what happened. Runs from all accounts appear in one history, and failures trigger alerts.
- You can go back. Every save is a version; restoring an older one takes effect on the next run.
What stays in Google Ads
The schedule, the authorization and the script logs stay where they always were. The loader is an ordinary Google Ads script, so preview, run and frequency work as usual.
You need to copy the loader again only if the script starts using a Google service it did not use before, such as Sheets or Gmail, because Google Ads asks for permissions based on the code it can see.
- 1
Copy or download the loader in chiliad.
- 2
Paste it as a new script in Google Ads — in a client account, or in the manager account to cover many clients at once.
- 3
Authorize once, preview, then schedule. The schedule is always set in Google Ads.