Google Ads
Google Ads Remembers Detailed Changes for 30 Days. Your Audit Trail Needs to Last Longer.

Updated: November 22, 2026
ChangeEvent provides field-level old and new values plus the client type and visible user, while ChangeStatus identifies resources that changed and only preserves the latest change in the requested period. They answer different audit questions. Use ChangeEvent for a human-readable ledger and ChangeStatus to find objects that require a fresh sync. Do not substitute one report for the other without documenting the missing detail.
Choose the evidence source for the question
ChangeEvent provides field-level old and new values plus the client type and visible user, while ChangeStatus identifies resources that changed and only preserves the latest change in the requested period. They answer different audit questions.
Use ChangeEvent for a human-readable ledger and ChangeStatus to find objects that require a fresh sync. Do not substitute one report for the other without documenting the missing detail.
Export detailed events before the thirty-day window closes
Google requires ChangeEvent queries to use a date range within the past thirty days. A monthly review performed late can permanently miss the field-level evidence needed to explain a budget, bid or targeting change.
Run a daily export with an overlap window, store the raw resource names and timestamps, and deduplicate the overlap in the warehouse. Monitor the last successful extraction date.
Operating control table
| Control | Evidence | Failure prevented |
|---|---|---|
| Owner | Named reviewer and decision | Unclaimed change |
| Configuration | Saved source state | Cannot reproduce |
| Validation | End-to-end fixture | Partial success accepted |
| Threshold | Success and rollback rule | Result reinterpreted |
| Evidence | Public or reporting read-back | Configured mistaken for delivered |
Page beyond the ten-thousand-row limit
ChangeEvent queries must include a limit of no more than ten thousand rows. High-change accounts or automated systems can reach that ceiling long before the reporting period ends.
Sort deterministically, record the timestamp and resource name of the final row, and continue from that boundary. Alert when a run returns the requested limit because silent truncation is likely.
Allow for reporting delay
Google notes that changes can take up to roughly three minutes to appear. An immediate post-mutation audit can therefore say no change exists even when the write succeeded.
Record the mutation receipt first, then poll the change feed after the documented delay. Reconcile the requested fields, the returned resource and the eventual live object.
Preserve source and actor context
A field change can come from the Google Ads web client, the API or another supported client. Treating every change as a manual optimization hides automation and makes incident ownership difficult.
Store client_type, user_email where available, resource type, campaign hierarchy and the automation job or approval ID. Route unrecognized clients or actors to review.
Re-query the current resource before reversal
ChangeStatus can tell you that an object changed, but the object may have changed several more times afterward. Reversing an earlier value from the ledger can overwrite a valid later decision.
Fetch the current resource by resource_name, compare it with the expected version and require approval for conflicts. Keep the ledger append-only so the full decision sequence remains visible.
Connect the control to the wider system
Use this process alongside the Google Ads API release-gate process. The platform setting, creative promise, measurement rule and downstream experience should describe the same decision.
Pre-launch checklist
- Write the decision and owner in plain language.
- Capture the source configuration and evidence.
- Test one realistic customer or reporting path end to end.
- Verify mobile presentation, links and accessibility.
- Record the success threshold and rollback trigger.
- Schedule the next review before material spend accumulates.
Run a cross-functional release review
Ask the channel owner, creative lead, analyst and conversion owner to inspect the same case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation.
Repeat the test on mobile and with one adverse condition. Resolve differences in the campaign brief and measurement plan before launch.
Set the review cadence before launch
Assign a monitoring owner, review frequency and evidence threshold before the change is released. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.
At the first review, reconcile the source platform, public experience and one downstream business system. Close the change only when all three support the same conclusion, and record any limitation that future analysts must preserve.
Frequently asked questions
Should this be automated?
Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.
What evidence should be preserved?
Keep the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.
When should the team roll back?
Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.
