A report can move after a campaign setting, offer, landing page, or CRM rule changes. The team may remember that “something was updated,” but not which audience was affected, when the change went live, or what result it was meant to improve.
A light change log puts that context beside the performance review. It records what changed and why, then gives the team a fair way to inspect what happened. It does not prove that a change caused a result.
Use this log for intentional changes that may affect reach, spend, lead flow, or measurement. It complements the incident log for broken forms and tracking, which is for unexpected failures, and the review gate guide, which helps decide who should approve a change before it goes live.
Start with what belongs in the log
Record changes that could affect a marketing decision or the evidence used to make one. Examples include a budget or bidding adjustment, a targeting change, a new creative or offer, a landing-page revision, a conversion-action update, or a change to lead routing and lifecycle rules.
Routine work does not need a long entry. A typo correction can stay out unless it changes a claim, offer, audience, or measurement path. A material message or conversion change deserves a note even if it looks small in the page editor.
Keep the purpose clear:
- a campaign naming convention makes records easier to identify and join;
- a review gate determines whether a change needs approval;
- an incident log captures an unexpected failure and its repair;
- a change log records an intentional update and the context for evaluating it.
The campaign naming guide covers names and tracking fields. The log should link to those stable identifiers rather than trying to replace them.
Record the fact separately from the reason
A useful entry lets another person reconstruct the change without relying on the author’s memory. Capture the platform and object, the date and time the change took effect, the owner, and the exact before-and-after state where available.
Then record the reason as a separate field. “Raised daily budget from X to Y” is an observable change. “Needed more qualified pipeline” is the business reason. “We expect more eligible volume without changing the cost per qualified meeting” is a hypothesis to assess later; it is not a guaranteed outcome.
For each material update, include:
- the account, campaign, page, form, or CRM rule affected;
- the change time and the time zone used in reporting;
- the owner and the link to platform history, a version, or a saved configuration;
- the reason, expected result, and metric or guardrail to review;
- the planned review point and any rollback or stop condition;
- other changes or dependencies that could affect the same period.
If a change is part of an experiment, connect the log entry to the experiment brief. If a change was made to repair a failure, connect it to the incident record. Keep the fact of the update, its business rationale, and the later interpretation distinct.
Use platform history as evidence, not as the whole record
Ad platforms can provide useful details that a manual note might miss. Google Ads Change History can show account, campaign, and ad-group changes, including details such as who changed an item and when. Google says the history covers the past two years; some account-level changes or updates made outside the interface may not appear as expected.
Use the platform record to verify the exact event, then add the cross-system context the platform cannot provide. A campaign budget change may be visible in Ads, while a concurrent landing-page edit, CRM routing change, or conversion-definition update lives somewhere else. Link those records together when they describe one decision.
Where a platform has a limited history window, retain a small internal record for the period your organization needs to review. Keep links access-controlled and avoid copying unnecessary personal data into the log. If the source record is unavailable later, the entry should still tell the reader what changed and where to look next.
Place each change on the same timeline as the results
Use one time zone consistently or store the offset with the event. Record when the setting was changed and when it became effective if those are different. A report built by day can otherwise make an update appear to precede or follow the wrong results.
Define the evaluation window before inspecting performance. Give the data enough time to arrive and, where needed, allow the conversion or sales cohort to mature. Compare like with like: the same campaign scope, outcome definition, reporting period, and currency basis.
Mark measurement changes separately from demand changes. A new tag, attribution setting, CRM field, or lead-routing rule can change what the report observes even if buyer behavior has not changed. The guide to tracking coverage versus conversion performance explains why those checks should stay distinct.
If several changes go live together, log each one or create a parent entry with linked child records. That preserves the timeline without pretending the team can isolate one effect when multiple parts of the system moved at once.
Review the evidence without turning timing into proof
At the review, read the change history alongside spend, delivery, lead, and sales outcomes. Note what changed, what stayed stable, and what else happened in the same period. A before-and-after comparison can surface a useful pattern, but it does not establish what would have happened without the update.
Use cautious language in the record: “followed by,” “coincided with,” or “needs another review” when the evidence is observational. If the decision requires a causal estimate, plan an appropriate experiment before the change where possible. The holdout-test guide explains one way to compare an intervention with a control when the conditions support it.
Close each review with a decision: keep the change, revise it, roll it back, or gather more evidence. Add the decision date and owner. This helps the next reviewer understand why the current setup differs from the previous one.
Keep the routine small enough to maintain
A log becomes stale when it asks people to write a report for every minor edit. Set a materiality rule that fits the organization: changes to budget, audience, offer, conversion measurement, or lead handoff may qualify, while routine maintenance can be captured in platform history alone.
Ask the person making a qualifying change to add the entry while the details are fresh. Review the log alongside the regular performance review, and check for missing owners, vague reasons, and changes that never received a result review. Keep one searchable location with stable links; avoid separate copies that drift.
A practical entry can answer these prompts:
- When did it change, and when did it take effect? ______
- Which account, campaign, page, or process changed? ______
- What was the exact before-and-after state? ______
- Who made the change, and where is the source record? ______
- Why was it made, and what did the team expect? ______
- Which outcome and guardrail will be reviewed? ______
- When will the evidence be mature enough to review? ______
- What else changed, and what is the rollback decision? ______
A good change log makes performance reviews easier to investigate. It gives the team a shared timeline, preserves the reason behind an update, and leaves room to say when the available evidence is not enough.
If campaign reviews keep losing the context behind major updates, map the change history, reporting window, and decision owners.
Sources and scope
- Google Ads Help: About change history — change details, users, performance timelines, and limitations of the platform history.
- Google Ads Help: Review your account history — filters and history views for campaigns, users, change types, and tools.
Platform records differ in scope and retention. Confirm which changes your tools expose, preserve required context under your organization’s data rules, and avoid treating a sequence of events as proof of causation. Accessed October 9, 2026.
How did this article land?
Choose one reaction. You can change it anytime.