---
name: keep-a-change-log
description: Use when reviewing, debugging, or scaling a paid campaign, or when an AI agent is about to edit live ads. Builds or reads a change log (who, what, when) and rolls back or flags any change that cannot be explained.
---

# Keep a change log

Every edit should have a who, what, and when. If you can't explain a change, roll it back.

## Instructions

1. **Before you scale or debug,** pull the change history for the relevant campaign and date range.
2. **For each edit, record:**
   - Who made it (person, agent, or platform automation)
   - What changed (field-level if available: budget, bid, targeting, creative, status)
   - When it changed
3. **Flag anything unexplained.** If a change has no actor, no reason, or does not match a known approval, highlight it and recommend a rollback. Do not keep an unexplained change in place just because performance looks fine.
4. **When you make an edit yourself,** write the same who / what / when entry, including why, and only after the human has approved the change (unless they have explicitly authorized a narrow, pre-approved action).
5. **Platform coverage.** Google Ads exposes a native account change history. On other platforms, if no comparable log exists, maintain a written log in the session (and any doc or spreadsheet the human designates) and say clearly that you are not reading a native platform log.

## Optional: Synter MCP

If Synter MCP is connected, use `get_account_changelog` to read Google Ads change history. This tool is Google Ads only. For other platforms, follow step 5.