Google Ads Change History Report - A Guide for Agencies

Google Ads change history report - a guide for agencies

A client emails on a Tuesday: "Why did leads drop off a cliff last week?" You open the account and everything looks normal. Nothing is paused, budgets are intact, campaigns are running. Somewhere between last Monday and this one, something changed, and nobody wrote it down.

The Google Ads change history report is the fastest way to answer that with evidence instead of a guess. It logs every edit made to the account, who made it, when, and what the value was before and after. For agencies running multiple accounts across multiple team members, it is the closest thing Google gives you to a proper account audit trail for PPC.

This guide covers what the report records, where to find it, how to run a change history export for audits and handovers, and how to fold change context into the client reports you already send. Our Google Ads integration exists precisely because this context rarely survives the trip from platform to client inbox.

Last updated: August 2026

Key takeaways

• The Google Ads change history report is a searchable log of every change made to an account, showing the date, the user, the item affected, and the old and new values.
• Google Ads Help documents change history as covering roughly the last two years of activity, so it is a medium-term audit trail, not a permanent archive.
• You can filter by date, user, campaign and change type, then download the results as a CSV for audits, disputes and client handovers.
• The Google Ads API change_event resource returns only about the last 30 days, so automated tracking must run on a schedule rather than retrospectively.
• Change history does not capture what happens outside Google Ads: GA4 conversion settings, tag changes, feed edits and landing page updates all sit outside its scope.

Table of contents

1. What is the Google Ads change history report?
2. Where to find change history in Google Ads
3. What the report records and what it misses
4. How to run a change history export
5. Five ways agencies use the audit trail
6. The limits every agency should know
7. Getting change context into client reports
8. FAQs

What is the Google Ads change history report?

The Google Ads change history report is a built-in log that records changes made to a Google Ads account, including who made each change, when it happened, and the value before and after the edit. It is not a performance report. It answers "what did we do?" rather than "how did it perform?", which is why it pairs so well with everything else in the account.

Each row typically shows a timestamp, the user or system responsible, the campaign, ad group or item affected, the change type (budget, bid, status, keyword, ad, targeting, setting) and the before and after values.

The important part for agencies is the user column. In a single-operator account, change history is a memory aid. In a five-person media team with a client-side marketing manager who also has access, it is an account audit trail for PPC work: the record you reach for when a result needs explaining and three people had the keys.

Its scope has widened over time to include automated changes made by Google itself. That part matters more than most agencies realise, and we come back to it below.

Where to find change history in Google Ads

Change history lives in the Tools section of Google Ads, and the most reliable way to reach it is the search bar at the top of the interface. Google has reorganised the navigation more than once in recent years, so menu paths published even a year ago are often wrong.

Here is the process that survives interface changes:

1. Sign in and select the client account you want to inspect. Change history is account-level, so a manager (MCC) account will not show you a single client's edits until you drill into that account.
2. Type "Change history" into the Google Ads search bar and open the result. Faster and more durable than hunting through menus.
3. Set your date range. Default views are usually short, so widen this to the period you are actually investigating before you read anything into the results.
4. Apply filters for user, campaign, change type or specific item. Filtering by change type is how you go from a wall of rows to a usable answer.
5. Use the download icon to export the filtered view as a CSV or spreadsheet.

For the current official view of the interface, Google Ads Help is the source to check (support.google.com/google-ads), because it updates when the navigation does. We would rather send you there than pin an exact menu path that breaks next quarter.

What the report records and what it misses

Change history records manual and automated edits to campaign structure, settings, bids, budgets, keywords, ads and targeting. It does not record everything that can affect performance, and knowing where the boundary sits saves you from confidently telling a client the wrong thing.

The right-hand column is the one that catches agencies out. A performance drop with a clean change history usually means the cause sits outside Google Ads: a tag stopped firing, a form broke, a conversion action was redefined, or a feed disapproval knocked out half the product range. Google's guidance on conversion setup (Google Analytics Help) is where to verify that side of the picture.

Two definitions for anyone newer to this. An account audit trail is a dated record of who changed what, borrowed from finance and used here for platform governance. Reporting cadence is how often a client hears from you, and it matters because change context is only useful while the client still remembers the period it covers.

How to run a change history export

A change history export is a CSV download of the filtered change history view, and it is the format you want for audits, disputes and account handovers. Reading changes on screen is fine for a quick check. Anything you need to keep, share or annotate should be exported.

The workflow we recommend for a client audit:

1. Set the window deliberately. Match it to the performance period in question, then add two weeks either side. Changes rarely show their effect the same day, especially with learning periods on automated bidding.
2. Export the unfiltered view first. Get the complete record before you narrow, so you still have the raw file if the question changes shape.
3. Then export by change type. Budget, bid strategy and status changes as separate files make the pattern obvious far faster than one giant sheet.
4. Filter by user for accountability. Not to point fingers, but because "the client's in-house marketer paused three ad groups on the 14th" is a complete answer and "performance declined" is not.
5. Store it with the account file. A quarterly export turns into a real audit trail after a year, long before you need one.

This is standard practice on any serious PPC audit report for clients, and it pairs naturally with a search terms report export from the same period. Changes explain intent, search terms explain reality, and reading them side by side is where most account diagnoses actually happen.

To track Google Ads changes programmatically, the API exposes a change_event resource (Google Ads API documentation), with one significant catch covered below.

Five ways agencies use the audit trail

Change history earns its keep in five specific situations, and each one saves a conversation that would otherwise cost you goodwill.

Diagnosing sudden performance drops. Before you theorise about seasonality or auction pressure, check whether someone changed something. It takes ninety seconds and resolves a meaningful share of "what happened?" questions outright.

Finding automated changes you did not make. Auto-applied recommendations can change match types, budgets and ad content without anyone on your team touching the account. Google documents these controls in Google Ads Help, and change history is where you see them land.

Client account handovers. Inheriting an account with no documentation is normal. A two-year export tells you what the previous agency actually did, which is usually more informative than the strategy deck they left behind.

Multi-user accountability. When the client's in-house team has edit access, change history is the difference between a professional conversation and an argument. You are not accusing anyone; you are reading the log.

Billing and dispute evidence. If a client questions a spend spike, budget change rows with timestamps and usernames settle it. Pair this with a reporting time savings calculation when you price the account management time these investigations consume.

We built ReportsMate after years around agency reporting, and the pattern we kept seeing is that the evidence always existed, it just lived in a platform the client never logged into. Google Ads is the most-connected platform on our own system, making up roughly 40% of every platform account agencies have connected.

The limits every agency should know

Change history has four hard limits, and planning around them is easier than being surprised by them mid-audit.

The retention window. Google Ads Help documents change history as covering approximately the last two years. That is generous compared with most platform logs, but finite. If you are reconstructing a three-year account story, the earliest chapter is gone. Quarterly exports solve this permanently.

The API window is much shorter. The change_event resource returns a far shorter window than the interface, on the order of the last 30 days, and caps rows per request. Automated change tracking therefore needs a scheduled job collecting continuously. You cannot query the API for last year's changes and expect an answer.

Smart Bidding is invisible at auction level. Automated bidding adjusts bids per auction, and those adjustments are not logged as individual changes. You will see the strategy change, the target change and the budget change, but not the millions of bid decisions in between. That is expected behaviour, not a gap in your access.

Nothing outside Google Ads appears. Tag changes, GA4 configuration, Search Console settings, feed updates and site changes all sit outside the report. This is the biggest reason a clean change history does not mean nothing changed.

Getting change context into client reports

The reason change history rarely reaches clients is not that it lacks value, it is that it lives behind a login clients do not use. That is the whole argument for email-first reporting, and why we built ReportsMate to deliver white-labelled reports into the inbox rather than behind another dashboard URL.

White-labelling means the report carries your agency's branding, logo, sender identity and custom domain, so the client sees your work rather than a tool's interface. Sender identity is the from-name and address the email arrives under, which is what makes a report feel like it came from you and not from software.

The habit worth adopting: when a report goes out, the commentary should reference the changes that drove the numbers. "Search impression share rose after we lifted the budget cap on 12 August" is a report a client understands. A chart with a line going up is a chart.

Whether you use ReportsMate, AgencyAnalytics, DashThis, Whatagraph, Swydo, Supermetrics or a Looker Studio build, the principle holds, and yes, we have an obvious stake in this view, so weigh it accordingly. Those tools are capable, and several do dashboard work better than an email ever will. Our position is that the report which lands in the inbox is the one that gets read. Across more than two thousand delivered report emails in our own logs, about a third are recorded as opened by the recipient. Open tracking is imperfect, but it is a number you can see, which is more than a dashboard login gives you. More on that in our post on tracking which clients read your reports.

Want to see how automated delivery works first? See how it works or check the plans and pricing.

FAQs

Q: How far back does Google Ads change history go?

A: Google Ads Help documents change history as covering approximately the last two years of account activity. That covers most agency use cases, including annual reviews and handovers, but it is not permanent. If you need a longer record, run a change history export quarterly and store the CSV with your client files. Agencies that inherit accounts often discover those two years are all the documentation that exists, so building the export habit early costs almost nothing.

Q: Can I see who made a change in Google Ads?

A: Yes. Change history shows the user associated with each change, usually the email address of the person who made it. Automated changes made by Google systems, including auto-applied recommendations, are attributed to the system rather than a person. This is the most valuable column for agencies, because multi-user accounts with client-side access are the norm. When a client's in-house marketer edits campaigns directly, the log records it, which turns a potentially awkward conversation into a factual one.

Q: How do I export Google Ads change history?

A: Open change history, set your date range, apply filters for user, campaign or change type, then use the download icon to export as a CSV or spreadsheet. Export the unfiltered view first so you have the complete record, then run separate filtered exports by change type. Budget, status and bid strategy changes in separate files make patterns visible much faster than one combined sheet, particularly on high-activity accounts where a month can produce thousands of rows.

Q: Does change history show automated and Smart Bidding changes?

A: It shows automated account changes such as auto-applied recommendations, but not the individual bid adjustments Smart Bidding makes at auction time. You will see when a bid strategy was changed, when a target CPA or target ROAS was adjusted, and when a budget moved. The per-auction decisions are not stored as account changes. If performance shifted with no corresponding entry in the log, a bidding learning period or an external factor is usually the explanation.

Q: Why does change history show no changes when performance dropped?

A: Because much of what affects Google Ads performance happens outside Google Ads. Tag changes, GA4 conversion configuration, landing page edits, form breakages, feed disapprovals and site outages are all invisible to change history. A clean log is genuinely useful information: it tells you to stop looking inside the account and start looking at tracking, the site and the feed. Reconciling Google Ads and GA4 conversions for the same window is usually the next step.

Q: Can I track Google Ads changes automatically?

A: Yes, through the Google Ads API change_event resource, though it returns a much shorter window than the interface, on the order of the last 30 days, and limits rows per request. Automated change tracking therefore has to run on a schedule and store results continuously; you cannot query it retrospectively for older periods. For most agencies, a scheduled export plus change commentary in the regular client report covers the need without building anything custom.

Q: Should change history go into client reports?

A: The raw log, no. The context, absolutely. Clients do not want a thousand-row CSV, but they do want to know why a number moved, and "we raised the budget on the 12th" is the sentence that makes a chart meaningful. The practical version is a short commentary section in each report referencing the two or three changes that mattered. Automated reporting handles the numbers; your job is the sentence next to them.

Final tips

Check change history before you check performance. It takes under two minutes and it reorders your entire diagnostic process, because knowing whether anything changed tells you which half of the problem space to search.

Export quarterly for every account you would hate to lose. The two-year window feels long until the day it does not, and a folder of CSVs is cheap insurance for handovers and disputes.

Filter by user on any account where the client has edit access, and watch for auto-applied recommendations, which are the most common source of "the account changed itself" confusion.

Then put the context in the report, not the log. The Google Ads change history report is a diagnostic tool for you and a translation job for your client. Do the translation and your reporting stops being a chart delivery service and starts being account management they can see.

Stop losing your Sundays to client reports. Start your free 14-day trial - no credit card, no setup, cancel anytime. Your clients get branded reports in their inbox automatically, with the context that explains the numbers.