πŸ€–chiliad
ClaudePricing
Help CenterScripts and deployment

How to roll back a Google Ads script to an earlier version

Google Ads keeps no usable history of script code. Here is how versions and restore work in chiliad.

Edit a script directly in Google Ads and the previous code is gone. If the change breaks something, you are left to remember what it used to say.

Versions in chiliad

Every save creates a version. Each one records:

  • the full code at that point,
  • who saved it,
  • where the change came from: the dashboard, Claude, a restore, or a marketplace update.

Open a script and go to the Versions tab to see the list.

Comparing

Click Compare on any version to see it side by side with the current code, with the differences highlighted. This is usually the fastest way to find what changed between "worked on Monday" and "fails today".

Restoring

Click Restore on the version you want back. It becomes the current code, and every account that runs the script uses it on the next run. Nothing has to be done in Google Ads.

A sensible routine

  1. Before a risky change, note the time of the current version.
  2. Save the change and watch the next run in the History tab.
  3. If it fails, restore the earlier version first, then investigate at leisure.

Settings have a history too

Per-account values are tracked separately. The Config changes list on the same tab shows which value was changed for which account, by whom and when β€” useful when a script suddenly behaves differently for one client only.

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

Budget Pacing Monitor

Enabled
ScriptVariables (3)VersionsHistoryAccounts (3)

Code versions

Latest savedΒ· 2h agoAnna K.Claude (MCP)1

var MONTHLY_BUDGET = 5000; var ALERT_EMAIL = …

CompareCurrent
Version 3Β· 3d agoAnna K.Dashboard

var MONTHLY_BUDGET = 5000; var ALERT_EMAIL = …

Compare2Restore3
Version 2Β· 9d agoMarco D.Marketplace update

var MONTHLY_BUDGET = 5000; var ALERT_EMAIL = …

CompareRestore
  1. 1

    Each version records the author and the source: the dashboard, Claude, a restore or a marketplace update.

  2. 2

    Compare shows a side-by-side diff against the current code.

  3. 3

    Restore makes an old version current again.

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 update a Google Ads script in every account at once
  • How to use different script settings for each account
  • 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.