The Google Ads Change Event connector brings the change history of your Google Ads accounts into Funnel: who changed what, when, where the change was made and the values before and after. This article explains what the connector does, how to work with its data and what to expect.
For the full field list, see Google Ads Change Event: Dimensions and metrics.
What the connector does
The connector reads Google Ads change events, the same kind of information you see under Change history in Google Ads. Each row is one change, for example:
A campaign was paused
A budget was raised
A keyword or ad was added or removed
A bid strategy or target was changed
Common uses:
Explaining performance shifts: see which changes happened just before a jump or drop in cost or conversions
Auditing: keep a record of who changed what, across all your accounts
Agency and team reporting: show the work done in each account
How data sources are set up
The connector uses your existing Google Ads connection.
There is one data source per Google Ads account. Accounts under a manager account (MCC) are grouped under it when you connect. Manager accounts themselves, hidden accounts and test accounts aren't listed.
Each data source has a single report, Change Event Report.
How history works
Google Ads only keeps change events for 30 days. The connector downloads the last 30 days several times a day.
When you connect the data source, you get the changes from the last 30 days.
Funnel keeps every change it has downloaded. Your history builds up from about 30 days before the day you connected.
Changes older than that can't be retrieved, so connect the data source as early as possible.
If you remove the data source and connect it again, the new data source only has the last 30 days.
What the data looks like
The report has dimensions only, no metrics. Each row describes one change:
Change Datetime | Change Resource Type | Resource Change Operation | Changed Fields | Client Type | User Email |
2026-10-14 09:12:31 | CAMPAIGN | UPDATE | status | GOOGLE_ADS_WEB_CLIENT | |
2026-10-14 11:40:05 | CAMPAIGN_BUDGET | UPDATE | amountMicros | GOOGLE_ADS_EDITOR |
Because there are no metrics, the data works best as a table of changes in a dashboard, or exported to your data warehouse.
Working with the data
Filter on what matters
Change Resource Type: focus on one kind of item, for example CAMPAIGN_BUDGET for budget changes or AD_GROUP_CRITERION for keyword changes.
Resource Change Operation: separate new items (CREATE), edits (UPDATE) and removals (REMOVE).
Client Type: separate changes people made in Google Ads or Google Ads Editor from automated ones, such as GOOGLE_ADS_SCRIPTS, GOOGLE_ADS_AUTOMATED_RULE, GOOGLE_ADS_API or GOOGLE_ADS_RECOMMENDATIONS (auto-applied recommendations).
User Email: see the changes made by one person.
Read the before and after values
Old Resource and New Resource only contain the fields that changed, as text with the Google Ads field names. For example, pausing a campaign shows status as ENABLED in Old Resource and PAUSED in New Resource.
Old Resource is empty when an item was created, and New Resource is empty when an item was removed.
Money values are in micros: divide by 1,000,000 to get the amount in the account's currency. For example,
amountMicrosof 50000000 is a budget of 50.00.To pull a single value into its own column, such as the new status or budget, create a custom dimension with a regex pattern on New Resource or Old Resource.
Connect changes to performance data
Campaign, Ad Group and Asset are Google Ads resource names, for example customers/1234567890/campaigns/111222333. The last number is the ID.
To report changes next to cost and conversions from the Google Ads connector, create a custom dimension with a regex pattern such as campaigns/(\d+) to get the Campaign ID, and match it to Campaign ID in your Google Ads data. Use adGroups/(\d+) for the Ad Group ID.
Not every change is tied to a campaign or ad group. For example, account-level changes have an empty Campaign, and campaign-level changes have an empty Ad Group.
Dates and time zones
Change Datetime is in the Google Ads account's time zone, and Date is the date part of it. If your accounts use different time zones, keep that in mind when you compare changes across accounts.
What to expect
Not everything is a change event. Google only records changes to the item types it supports. Adjustments that Google's automated bidding makes during auctions aren't changes, so they don't appear.
The connector can show less than Change history. The Change history page in Google Ads can include some items that Google doesn't make available as change events.
One action can create several rows. For example, creating a campaign can create rows for the campaign, its budget and its criteria. A bulk upload or script can create many rows with the same timestamp.
Busy accounts are supported. The connector downloads one day at a time and pages through large days, so accounts with many changes get all of them. In the rare case that more than 10,000 changes share exactly the same timestamp, Google can't return them all and the data source shows an error. Contact support if this happens.
Connection errors
If a data source shows Invalid credentials, please reconnect, the Google login used for the connection has expired or lost access. Reconnect the data source with a Google user that has access to the Google Ads account.