agency
How to Set Up Change History Monitoring for Google Ads
Set up change history monitoring by defining which changes matter most (budget, bidding, campaign status), creating automated alerts for unauthorized or unexpected modifications, establishing team accountability through access controls and change documentation, and maintaining an audit trail that connects changes to performance outcomes.
Change history monitoring catches unauthorized modifications, tracks the impact of intentional changes, and creates accountability across teams and clients. Without it, you only discover problems after performance degrades — and by then, the cause is often buried under days of subsequent changes. This guide covers how to build a monitoring system that keeps you informed without overwhelming you with noise.
Key Takeaways
- Not all changes are equal — prioritize monitoring budget, bidding, and campaign status changes that have the highest performance impact
- Auto-applied recommendations from Google are a major source of unintended changes — review and restrict them proactively
- Change monitoring should correlate modifications with performance shifts, not just log what changed
- Establish clear ownership: every change should have a documented who, what, why, and expected outcome
- Multi-account monitoring requires centralized tools — per-account manual review does not scale
Introduction
Google Ads accounts are modified constantly — by managers optimizing performance, by automated rules executing on schedule, by Google’s own auto-apply recommendations, and sometimes by client stakeholders with account access. Each change has the potential to improve or degrade performance.
The challenge is visibility. A budget change at 2 AM from an automated rule, a keyword added by Google’s auto-apply, or a campaign paused by a client contact — any of these can cause significant performance shifts that are difficult to diagnose if you do not know the change happened.
Change history monitoring creates a safety net. It does not prevent changes (access controls do that), but it ensures nothing happens in your accounts without your knowledge and without a trail connecting the change to any performance impact.
Step 1: Define What to Monitor by Impact Level
Not every change deserves an alert. Categorize changes by their potential performance impact to avoid alert fatigue.
Critical changes (alert immediately):
| Change Type | Why It Matters | Alert Method |
|---|---|---|
| Campaign paused/enabled | Stops or starts all spend in a campaign | Immediate notification |
| Daily budget changed | Directly impacts spend and delivery | Immediate if > 20% change |
| Bid strategy changed | Alters optimization approach, triggers learning period | Immediate notification |
| Conversion action modified | Changes what Smart Bidding optimizes toward | Immediate notification |
| Account-level settings changed | Affects all campaigns | Immediate notification |
High-impact changes (alert same-day):
| Change Type | Why It Matters | Alert Method |
|---|---|---|
| Keywords added or removed | Expands or restricts traffic | Daily digest |
| Audience targeting changed | Shifts who sees your ads | Daily digest |
| Ad copy changed | Affects CTR and Quality Score | Daily digest |
| Negative keywords added/removed | Changes traffic filtering | Daily digest |
| Extensions added/removed | Affects ad visibility and CTR | Daily digest |
Low-impact changes (weekly review):
| Change Type | Why It Matters | Alert Method |
|---|---|---|
| Bid adjustments (manual) | Fine-tuning within existing strategy | Weekly summary |
| Label changes | Organizational only | Weekly summary |
| Ad group name changes | Organizational only | Weekly summary |
Step 2: Set Up Automated Rules and Alerts
Google Ads provides basic change history but limited alerting. Build a monitoring system using a combination of built-in tools and external monitoring.
Using Google Ads change history (built-in):
- Navigate to Change history (under Reports or the three-dot menu)
- Filter by date range, user, and change type
- Review critical changes daily and all changes weekly
Limitations of built-in change history:
- No real-time alerts — you must actively check
- No cross-account view from the MCC level
- No automated correlation with performance changes
- No differentiation between intentional and accidental changes
- Change history shows what changed but not whether it helped or hurt
Setting up automated rules for monitoring:
While Google Ads rules cannot alert on changes made by others, they can catch the effects:
- Create a rule that alerts when daily spend exceeds 150% of your expected level (catches budget increases)
- Create a rule that alerts when a campaign’s status changes (catches pauses/enables)
- Create a rule that alerts when conversion volume drops more than 30% week-over-week (catches tracking or targeting changes)
Google Ads scripts for change monitoring:
Scripts can query the change history API and send notifications:
- Run daily at the MCC level to check all accounts
- Filter for critical change types (budget, bidding, campaign status)
- Send email or Slack alerts with change details
- Log changes to a spreadsheet for audit trail
Doing this manually across even 10 accounts means checking 10 separate change history logs daily. At 30+ accounts, it is not feasible. Lyra’s Change History Alert system monitors changes across all connected accounts in real-time, categorizing by impact level and alerting on critical modifications with context about who made the change and the performance trend before and after.
Step 3: Restrict and Monitor Auto-Apply Recommendations
Google’s auto-apply feature automatically implements Google’s optimization recommendations unless you opt out. This is one of the most common sources of unintended changes.
Common auto-apply categories and risks:
| Category | What Google Does | Risk Level | Recommendation |
|---|---|---|---|
| Add responsive search ads | Creates new RSAs automatically | Medium | Disable — you should control ad copy |
| Add keywords | Adds keywords Google thinks are relevant | High | Disable — can add irrelevant terms |
| Use broad match | Switches keywords to broad match | High | Disable — changes traffic quality |
| Adjust bids | Modifies manual bids | Medium | Disable if using manual CPC |
| Set target ROAS/CPA | Changes bid strategy targets | High | Disable — strategy changes need human review |
| Use optimized ad rotation | Changes ad serving preference | Low | Can leave enabled |
| Remove redundant keywords | Pauses duplicate keywords | Low | Can leave enabled with monitoring |
How to review and restrict auto-apply:
- Navigate to Recommendations in your Google Ads account
- Click “Auto-apply” in the top right
- Review each category’s status (on/off)
- Disable any category where you want manual control
- Check this setting quarterly — Google occasionally adds new auto-apply categories
Monitor auto-applied changes:
Even after restricting categories, check what has been auto-applied:
- Go to Change history
- Filter by “User: Google Ads system”
- Review all system-made changes
- Reverse any that conflict with your strategy
Step 4: Establish Team Accountability and Access Controls
Change monitoring is only useful if you can identify who made each change and hold them accountable for the outcome.
Access control best practices:
| Role | Access Level | Can Change |
|---|---|---|
| Account Manager | Standard | Keywords, ads, bids, negatives |
| Strategist | Standard | Campaigns, budgets, bid strategies, audiences |
| Team Lead | Admin | All settings including conversion tracking and access |
| Client Contact | Read-only or Standard (restricted) | Depends on agreement — document clearly |
| Billing | Billing only | Payment methods only |
Setting up access:
- In Google Ads, go to Admin > Access and security
- Invite users with the appropriate access level
- Use individual accounts — never share credentials
- Remove access immediately when someone leaves the team or client relationship
Change documentation standards:
For every intentional change, document:
| Field | Purpose | Example |
|---|---|---|
| Date/time | When the change was made | 2026-04-09, 10:30 AM |
| Who | Person responsible | Jane Smith |
| What | Specific change made | Increased Campaign X budget from $100 to $150/day |
| Why | Business rationale | Campaign is budget-limited with CPA 30% below target |
| Expected outcome | What should improve | 50% more conversions at similar CPA |
| Review date | When to evaluate impact | 2026-04-23 (2 weeks) |
This documentation creates a learning loop. When you review the outcome, you learn whether the hypothesis was correct, building institutional knowledge about what works.
Step 5: Build an Audit Trail That Connects Changes to Outcomes
The highest-value change monitoring does not just log changes — it connects each change to its performance impact. This transforms change history from a forensic tool (used after something breaks) into a learning tool (used to improve decision-making).
Building the connection:
- Log the change — Record what changed, who changed it, and when
- Snapshot performance before — Record key metrics (CPA, ROAS, conversion volume, impression share) at the time of the change
- Set a review date — Based on the expected lag for the change to take effect (typically 1-4 weeks)
- Snapshot performance after — Record the same metrics at the review date
- Evaluate — Did the change improve, degrade, or have no effect on performance?
Practical implementation:
Maintain a change log spreadsheet or database with these columns:
| Column | Purpose |
|---|---|
| Date | When the change was made |
| Account | Which account |
| Campaign | Which campaign |
| Change type | Category (budget, bidding, targeting, creative) |
| Change detail | Specific modification |
| Changed by | Who made it |
| Rationale | Why it was made |
| Pre-change CPA | Performance baseline |
| Post-change CPA | Performance after maturation |
| Impact assessment | Positive, negative, neutral |
| Learning | What we learned from this change |
Forensic use:
When performance drops unexpectedly:
- Check change history for the affected campaign and date range
- Cross-reference with your change log for documented changes
- Identify any undocumented changes (these are your problem candidates)
- Reverse suspicious changes one at a time, waiting for impact assessment between each reversal
Maintaining this level of change tracking manually across multiple accounts is impractical for most agencies. The sheer volume of changes across 20+ accounts makes comprehensive logging and performance correlation a full-time job. Lyra’s Change History Alert automatically logs all changes across connected accounts, correlates them with performance shifts, and highlights changes that coincided with significant performance deviations — both positive and negative.
Practical Example
An agency discovers a sudden 40% CPA increase in a client’s primary Search campaign. Here is how change monitoring helps diagnose the issue:
Investigation timeline:
| Step | Action | Finding |
|---|---|---|
| 1 | Check campaign performance timeline | CPA spiked starting April 3 |
| 2 | Review change history for April 1-3 | Three changes found |
| 3 | Change A: Budget increased 20% (April 1, by account manager) | Documented, expected |
| 4 | Change B: Conversion tracking action modified (April 2, by Google Ads system) | Auto-applied, not documented |
| 5 | Change C: 15 broad match keywords added (April 2, by Google Ads system) | Auto-applied, not documented |
| 6 | Root cause identified | Auto-applied keyword additions brought irrelevant traffic; conversion tracking change altered what Smart Bidding optimized for |
Resolution:
- Reversed the auto-applied keyword additions
- Restored the original conversion action configuration
- Disabled auto-apply for “Add keywords” and “Conversion action modifications”
- CPA returned to normal within 5 days
Without change monitoring: The agency would have spent days testing hypotheses — was it a competitor change? A landing page issue? A seasonal shift? — while the real cause (auto-applied changes) continued degrading performance.
Common Mistakes
- Not monitoring auto-apply — Google’s auto-apply recommendations are the most common source of unexpected changes. Review and restrict them proactively in every account.
- Alert fatigue — Alerting on every change overwhelms your team. Categorize by impact level and only send immediate alerts for critical changes. Use daily digests for medium-impact and weekly summaries for low-impact.
- No documentation standard — If changes are not documented with rationale and expected outcomes, you cannot learn from them or diagnose problems efficiently.
- Granting too much access — Every person with account access can make changes. Restrict access levels to match roles, and use read-only access for stakeholders who need visibility but should not make modifications.
- Checking change history only when something breaks — Proactive daily or weekly reviews catch problems before they compound. Reactive-only monitoring means every issue has already cost you money before you discover it.
Lyra’s Change History Alert monitors 60+ accounts simultaneously, categorizing changes by severity, flagging auto-applied modifications, and correlating each change with performance metrics to build a comprehensive audit trail without manual effort.
Frequently Asked Questions
What changes should I monitor in Google Ads? +
How far back does Google Ads change history go? +
Can Google's auto-apply recommendations make changes without my knowledge? +
How do I track changes made by automated bid strategies? +
Try Lyra Free
19 Google Ads optimization tools. 14-day free trial.
Start Free TrialNo credit card charged until trial ends
Start Optimizing Your Google Ads Today
14-day free trial. All 19 tools included. No credit card charged until trial ends.
Start Free Trial