Google AdsCoNote

Google Ads change history, on a timeline that outlasts the report.

Google Ads keeps a change history — but it’s buried inside the account, where the rest of the company never looks. CoNote puts every budget change, pause, and status edit on one shared timeline, beside the deploys and tracking changes from the same day.

Start your logbook See how it works

Google Adspublished a change

Your timelineToday

Spring sale — daily budget raised to $450

Google Ads· 10:12

Deployed storefront v2.4.0 (main → 3a7f2c1)

GitHub· 09:41

Finding your history

Your Google Ads change history: today, and from now on

The manual way · inside Google Ads

Where to find it today

It’s all there — if you go digging:

1
Sign in to Google Ads
Open ads.google.com and pick the account you need — each account keeps its own separate change history.
2
Open the Change history report
Click the Tools icon, then Change history under Bulk actions. Every edit is listed with who made it, what changed, and the exact time.
3
Set the date range
Use the date picker to widen the window — the report defaults to a recent range, so extend it to cover the day your KPIs moved.
4
Filter by change type or user
Narrow to budget changes, status changes, bid edits, or a single user to cut through the noise of routine edits.
5
Cross-reference the dates by hand
There’s no view across accounts or against your deploys and analytics, so you line each change up with the rest of your stack yourself.

The CoNote way · one timeline

Where to find it from now on

Connect Google Ads once. After that it’s seconds:

1
Open your CoNote timeline
Every campaign change is already waiting — no Ads login, no account-by-account hopping.
2
Jump to the day it moved
Scan the day your spend or conversions shifted; the budget change or pause is stamped there to the minute.
3
See it beside everything else
The change sits right next to that day’s deploys, tracking changes, and incidents — the cause is obvious.

Start your logbook

Sound familiar?

Google Ads change history works — until you need it.

#marketingMonday, 09:10

Mia09:10

Ad spend nearly doubled over the weekend. Did someone change a budget?

Jonas09:14

Maybe? A few campaigns were edited last week.

Sara09:18

Which campaign, and what was the old budget?

Jonas09:23

I’d have to dig through the change history account by account.

So the account-by-account digging begins.

#paid-searchWednesday, 11:30

Lena11:30

Our top campaign stopped delivering on Tuesday. Was it paused, or did the budget run out?

Jonas11:34

Not sure — someone might have touched the status, or it’s a budget cap.

Lena11:37

Who changed it, and exactly when?

Jonas11:41

Let me pull up the change history and filter by status…

Nobody can say what stopped it, or when.

#growthThursday, 15:50

Clara15:50

CPA jumped 40% since midweek. Did bids or budgets change, or is it tracking?

Tom15:54

Could be the GTM publish too — hard to tell which came first.

Clara15:58

Right — was it the Ads change or the tag change? And on which day?

Tom16:03

Two different tools, two different histories. I’ll line them up by hand.

The Ads change and the tag change never sit on one screen.

#marketingMonday, 09:10

Mia09:10

Ad spend nearly doubled over the weekend. Did someone change a budget?

Jonas09:14

Maybe? A few campaigns were edited last week.

Sara09:18

Which campaign, and what was the old budget?

Jonas09:23

I’d have to dig through the change history account by account.

So the account-by-account digging begins.

It answers “what changed in this account?” — never the question you actually have: “what changed across everything around the day my spend or conversions moved?”

One account at a time — no single view across accounts
Locked inside Google Ads, where leadership and the rest of the team never look
Never lined up against the deploy or tracking change from the same day
Cold months later — when the agency or the person who changed it has left

With CoNote, the change that did it is already on the timeline — “Spring sale — daily budget raised to $450” — stamped to the minute, next to every other change from that day.

How it works

Connect once. Then it logs itself.

01
Authorize with Google
A two-click Google authorization — no scripts, no account edits. CoNote reads your account’s change history, nothing else.
02
Every change logs itself
CoNote checks for new changes on a schedule. Each budget edit, pause, and status change lands on the timeline with what changed and the moment it went live — a readable entry, not a raw log row.
03
Read it in context
The change sits beside that day’s deploys, tracking changes, and incidents. When spend or conversions move, you scan one page instead of four tools.

What lands on your timeline

Budget changes — the campaign and the new amount
Campaign and ad group status changes — paused, enabled, removed
The moment each change went live, to the minute

In your week

What teams use it for.

Spend spiked — who changed the budget?
Costs jump overnight. You open the day it happened and see the budget raised to $450 at 10:12, with the campaign named — instead of a five-person hunt through account histories.
Prove what the agency changed
Every budget, bid, and status change is logged and dated — so months later, even after the agency rotates people, you can show exactly what they touched and when.
Ads or tracking — which moved the KPI?
The Google Ads budget change sits next to that day’s GTM publish and deploy, so you can tell a campaign edit from a tracking change at a glance.
End the cross-team “was it us?”
Marketing’s budget change, the deploy, and the conversion dip all land on one page — so the team reads one timeline instead of pointing at each other.

Side by side

Native change history vs. your logbook.

See budget, bid, and status changes

Google Ads change history

Inside Google Ads

CoNote

On your timeline

One view across every account

Google Ads change history

One account at a time

CoNote

All in one place

Lined up against deploys, tracking, incidents

Google Ads change history

Google Ads only

CoNote

Side by side

Visible to the whole team and leadership

Google Ads change history

Needs Ads access

CoNote

Team-wide

Searchable months later

Google Ads change history

Filter by date range

CoNote

Search and filter

Setup

Google Ads change history

Built in

CoNote

Two-click Google auth

Capability

Google Ads change history

CoNote

See budget, bid, and status changes

Inside Google Ads

On your timeline

One view across every account

One account at a time

All in one place

Lined up against deploys, tracking, incidents

Google Ads only

Side by side

Visible to the whole team and leadership

Needs Ads access

Team-wide

Searchable months later

Filter by date range

Search and filter

Setup

Built in

Two-click Google auth

On the timeline

The change in context.

A budget change on its own is a shrug. Next to the deploy and the conversion dip from the same day, it’s an answer.

Tuesday, June 9

Deployed storefront v2.4.0 (main → 3a7f2c1)
GitHub· 09:41
Spring sale — daily budget raised to $450
Google Ads· 10:12
Checkout conversion tracking stopped firing
Uptime· 15:02

Questions

Google Ads change tracking, answered.

Sign in to Google Ads, click the Tools icon, then open Change history under Bulk actions. Every edit is listed with who made it, what changed, and the time — use the date picker and the filters to narrow by change type, user, or campaign.

A standard two-click Google authorization that lets CoNote read your account’s change history — read-only in practice. It never edits your campaigns, budgets, or anything else in your account.

Budget changes, campaign and ad group status changes, and similar account edits — each as a plain-language entry with the time it went live. CoNote only reads your change history; it never changes your campaigns.

No. Connecting Google Ads is a two-click Google authorization in CoNote — no scripts, no changes to your account, no developer time.

Google Ads’ history lives inside Google Ads, one account at a time, and only people with account access ever see it. CoNote puts those changes on a shared timeline next to your deploys, tracking changes, and incidents — so the whole team can line a budget change up against the day a metric moved.

Only your team. Every entry is scoped to your team, and connecting Google Ads doesn’t expose your account to anyone outside it.

Open the logbook.

Free plan, no card. The next time someone asks “what changed?”, the answer is one search away.

Start your logbook

Google Ads change history, on a timeline that outlasts the report.

Your Google Ads change history: today, and from now on

Where to find it today

Sign in to Google Ads

Open the Change history report

Set the date range

Filter by change type or user

Cross-reference the dates by hand

Where to find it from now on

Open your CoNote timeline

Jump to the day it moved

See it beside everything else

Google Ads change history works — until you need it.

Connect once. Then it logs itself.

Authorize with Google

Every change logs itself

Read it in context

What teams use it for.

Spend spiked — who changed the budget?

Prove what the agency changed

Ads or tracking — which moved the KPI?

End the cross-team “was it us?”

Native change history vs. your logbook.

The change in context.

Google Ads change tracking, answered.

Track the rest of your stack.

Open the logbook.