Google Ads change history: what it records, where it stops, and how to get more from it.
“Who changed this campaign?” is usually asked on the day results drop. Change history answers part of that question. This guide explains which part, shows a method for investigating a drop, and suggests what to record yourself so the rest of the answer exists when you need it.
Three things to remember.
Two years in the interface
Change history lists changes to the account, campaigns and ad groups for the past two years. Older data is not available.
Thirty days through the API
A tool reading changes through the Google Ads API can only query the past 30 days, 10,000 rows at a time.
What and who, never why
It records the change and, often, the user. It has no field for the reason, and none for who agreed.
What you will find in change history.
Google describes change history as a list of the changes made to your account, campaigns and ad groups: a campaign paused, a keyword added, a previous budget amount. Each change sits on a timeline next to impressions, clicks, conversions, click-through rate and cost, which is what makes it useful: you can see a change and the days that followed it on the same screen.
You open it from the Campaigns menu for the whole account, or from a single campaign or ad group. You can filter by date range and by type of change, for example budget adjustments or keyword edits.
The User column shows the email address of the person for changes made in the Google Ads interface. Changes made through the API appear as “Google Ads API” or under the name of a tool. Automated or internal changes appear under names such as “Google Ads system”.
Six limits worth knowing before you rely on it.
| What the documentation says | What it means in practice | |
|---|---|---|
| Duration | The past two years; older data is not available | A decision from three years ago leaves no trace unless you kept one |
| Changes through a tool | Shown as “Google Ads API” or a tool name | You see the tool, not the person who used it |
| Missing entries | Some account-level settings and changes made by Google representatives may not be listed | An empty history is not proof that nothing changed |
| Large changes | Details shown per entry are limited; Google suggests changes affecting fewer than 2,000 entities to see everything | A bulk upload can hide the one line that matters |
| Through the API | 30 days, 10,000 rows per query, not every row of the interface, and Google Ads Editor changes are not returned by change events | A third-party tool that started reading last month cannot rebuild last year |
| The reason | No field for it | The “why” lives in emails, chats and memories |
Documentation read on 12 October 2026. Platforms change: check the linked pages.
Investigating a drop in five steps.
The order matters: most people open change history first, and blame the most recent change they find. Start by checking that the drop is real.
Is the tracking intact?
Conversions at zero with stable clicks point to a tag or a conversion action, not to the campaign.
Date the break
Find the first abnormal day, by day rather than by week. Recent days may still receive late conversions.
Read the week before
Filter change history on the seven days before the break: budgets, bidding, keywords, ads, in that order.
Look beyond people
Check entries from tools, the system and auto-applied recommendations, then what the history cannot show: site releases, stock, prices, competitors.
Write the conclusion down
What changed, what you believe caused the drop, how sure you are, and what you decided. This is the record the history does not keep.
A change that precedes a drop is a candidate, not a culprit. Two things that happen in the same week are not always cause and effect.
The decision log: seven fields to record alongside the platform's history.
A shared spreadsheet is enough to start. One line per decision that matters, not per click.
| Field | Example | Why it matters later |
|---|---|---|
| Date and account | 3 March, main account, Brand campaign | Lets you find the matching entry in change history |
| The change | Daily budget from €80 to €100 | Before and after, not just “budget raised” |
| The reason | Campaign limited by budget four days out of seven | The one thing no platform records |
| What it was based on | Last 30 days, cost per conversion stable | Shows whether the decision was sound with what was known |
| Who decided, who agreed | Proposed by Léa, agreed by the client by email | Change history shows who clicked, not who agreed |
| What you expect | More conversions at the same cost per conversion | Without it, you cannot say whether it worked |
| When to review | 17 March | Turns a change into something you learn from |
Fictitious example.
Three ways to add an approval step before a change.
Change history tells you what happened. If you want a say before it happens, you need a step that the platform does not provide for campaign changes.
A rule within the team
Agree which changes need a second person, and note the agreement in the decision log. Free, immediate, and only as reliable as the team's discipline.
Campaign drafts
Google Ads drafts let you prepare changes to a Search or Display campaign without affecting it, then apply them. Useful for review, but a draft is not an approval: whoever can edit the campaign can apply it.
A tool with approvals
A tool that prepares each change, checks it and asks a named person before anything is applied. Look at how it records the reason, and at what it does when a check fails.
Where Plireo fits, and where it does not.
Plireo is being built around the third approach: a change to a Google Ads Search campaign is written as a before and after, checked, approved by a person with the approver role, and recorded with its reason.
It does not replace change history. Changes made directly in Google Ads are not imported into Plireo's record, so the platform's history remains the reference for everything done outside it.
Frequently asked questions
How far back does Google Ads change history go?
Two years in the Google Ads interface. Google states that data older than two years is not available. Through the API, change events can only be queried for the past 30 days.
Can I see who changed a campaign?
For changes made in the Google Ads interface, the User column shows the person's email address. For changes made through a tool, you will see “Google Ads API” or the tool's name, and will need that tool's own record to know who acted.
Does change history show changes made by Google's automation?
Automated or internal changes can appear under names such as “Google Ads system”. Auto-applied recommendations are listed in the History tab of the Recommendations page and in change history. Google also notes that some account-level settings changes may not be listed.
Does Google Ads have an approval step for campaign changes?
Not for campaign changes. Google Ads has multi-party approval for sensitive user actions: adding a user, removing one, or changing an access level requires a second administrator. Its documentation lists those actions, not budgets, keywords or ads.
Related pages
Be among the first to use Plireo.
Plireo is in pre-launch. Request early access to be told when it opens, or apply to take part in private testing. Access opens gradually, so a request does not mean immediate access.
Paid plans open once the Google Ads, Meta, GA4 and GTM integrations are operationally validated.
Request early access