How chiliad Works: From Script to Execution in 3 Minutes

chiliad makes Google Ads scripts manageable at scale. But how does it actually work under the hood? This post walks through the full flow — from writing a script to monitoring its execution across dozens of accounts.

The Two-File Architecture

Every script in chiliad is split into two parts:

1. Loader script — a small, auto-generated snippet you paste into Google Ads. It never changes.
2. Library script — your actual automation code, hosted on chiliad's servers. This is what you edit.

When Google Ads runs the loader, it fetches the latest version of your library code and executes it. This means you deploy once (paste the loader) and every future code change is picked up automatically — no more logging into each account to update scripts.

How the Loader Works

The generated loader script does three things:

1. Detects the account type — checks whether it is running inside a single account or an MCC (manager account), and handles both automatically.
2. Fetches your code — downloads the latest library from chiliad's CDN using UrlFetchApp.fetch().
3. Reports back — after execution, it sends a lightweight analytics ping back to chiliad with the execution status, duration, and which Google Ads account ran it.

The analytics ping is the magic that powers auto-linking and execution monitoring.

Auto-Linking: No Manual Account Assignment

This is the feature that confuses new users the most — in a good way. You do not need to manually assign scripts to accounts. Here is how it works:

1. You paste the loader into a Google Ads account (or MCC).
2. The script runs and calls chiliadAnalytics() at the end.
3. This function sends a report to chiliad that includes the Google Ads Customer ID of the account that ran it.
4. chiliad checks if that account exists in your workspace. If it does, it links the script. If not, it auto-creates the account and links it.

After the first execution, you will see the account appear in the Accounts tab of your script — fully linked, with execution history tracking from that point on.

This works for MCC scripts too. If your loader runs across 50 child accounts, all 50 will be auto-linked after a single MCC execution.

Execution Tracking

Every time a script runs in Google Ads, chiliad captures:

• Status — success or error
• Duration — how long the script took
• Account — which Google Ads account ran it
• Timestamp — when it ran
• Error details — if something went wrong, the line number and error message

This data powers the dashboard charts, the execution history on each script page, and the alerting system.

Failure Alerts

When a script fails, chiliad can notify you via:

• Email digest — daily or weekly summary of all script activity
• Slack alerts — real-time notifications to your team channel with error details and failure count

No more discovering a broken script two weeks later when a client asks why their bids have not changed.

The Marketplace

The script marketplace provides ready-to-use automations you can install with one click. When you install a marketplace script, chiliad copies the code into your workspace, generates a loader, and lets you customize configuration variables before deploying.

Marketplace scripts cover common needs: placement cleanup, budget pacing, search term mining, quality score tracking, and more.

Team Collaboration

chiliad workspaces support multiple users with role-based access. Everyone on your team shares the same script library and account connections:

• One person writes the script, everyone can deploy it
• Account access can be scoped — junior team members see only their assigned accounts
• Execution history is shared, so anyone can investigate failures

Getting Started

The whole setup takes about 3 minutes:

1. Create an account at chiliad.io
2. Pick a script from the marketplace or create your own
3. Copy the loader from the Script tab
4. Paste into Google Ads — Tools > Bulk Actions > Scripts > New script
5. Run it once — the account auto-links and you are live

From that point on, every execution is tracked, every failure is caught, and every code update is deployed instantly. No more spreadsheets tracking which scripts run where.

Try it free and see for yourself.