ChangeEvent (Google Ads API)

ChangeEvent is a Google Ads API resource that makes changes from the past 30 days queryable with timestamp, user and old and new values.

ChangeEvent is an official term from Google’s developer documentation. It is aimed at people who evaluate accounts through code, and it has nothing to do with SEO.

Where the term comes from

The Google Ads API is the programming interface to Google Ads. It has resources for campaigns, ad groups, keywords and many other objects. change_event is one of those resources. It records what was changed in an account.

The “API” in the glossary term is not a separate service. There is no standalone “ChangeEvent API”, only a resource inside the Google Ads API.

How ChangeEvent works

You query the resource like a table and filter on the field change_date_time. According to the documentation, the date range must fall within the past 30 days. You also need a limit of at most 10,000 rows.

For newly created objects, an entry returns all new values. For updates, it returns old and new values. It also shows which client made the change and who made it. You only see the user if the change history in the interface shows it too.

New changes do not appear right away. According to the documentation, it can take up to three minutes.

How it differs from the change history

The change history in the Google Ads interface is the view for humans. ChangeEvent is the machine-readable access. Both show similar data, but not the same data.

Google writes that an entry may not include every row from the history and may render some changes differently. Changes made in Google Ads Editor are not supported through this resource. For a closer match to the history, or for changes at the criterion level, the documentation points to the change_status resource.

ChangeEvent has no fixed link to automation layering. It is only one possible data source when you want to monitor automated interventions.

What this means for your account

A typical question is why an account’s performance dropped from a certain day. With ChangeEvent, you find out who changed what on that day. That helps you separate self-inflicted causes from market swings.

When several people or agencies work in the account, a regular export helps. A script can write the entries from the last few days into a spreadsheet. There they stay available beyond the 30 days. Also use hints from budget pacing insights when spend deviates noticeably.

Limits and typical mistakes

The most common mistake is treating ChangeEvent as a complete audit log. According to the documentation, it is not. Queries must also respect the date range and the row limit.

The resource shows what changed, not why. Only the people on the team know the reason. An entry does not replace documenting your decisions.

Frequently asked questions

How far back does the change log go?

The query must fall within the past 30 days. The resource does not return older changes. If you want to look back further, you have to store the results regularly yourself.

Do I really see every change there?

No. The documentation says explicitly that an entry may not include every row from the change history in the web interface. Changes made in Google Ads Editor are also not supported through this resource.

Do I need a developer for this?

For querying through the API, yes, because it runs through code or scripts. For a quick look, the change history in the Google Ads interface is enough.