Adgent

Every account move, its before-state and what happened next.

The Change Ledger is Adgent's record of every account move it applied, with the before-state and what happened next. Adgent keeps the owner, time, value replaced and execution status in one row. For supported reversible changes, it prepares the inverse from that history for your approval.

PricingWho changed this?

Change Ledger

Real rows · one live Meta account · 26 Aug 2026
  1. Writtenwith what it replaced
  2. Inverse draftedby the agent, from the row
  3. Owner decidesapply or not now
  4. Its own rowthe way back is logged too

Today · 26 Aug

Youfrom the ledger Geo exclusion removedMeta · ad set LT: excludedLT: not excluded Put back
Youin chat Geo exclusionMeta · ad set LT: not excludedLT: excluded

Yesterday · 25 Aug

Youin chat StatusMeta PAUSEDACTIVE Way back open

Nothing is drafted. Press Revert with agent on the 22:33:25 row. The agent builds the inverse here, ready to review.

Drafted from row 22:33:25Meta · Geo exclusion

Put Lithuania back into this ad set's targeting.

CurrentLT: excluded
ProposedLT: no longer excluded

Built from the before-state on the ledger row, with the original and inverse values side by side.

Ready to apply.

29 s

from change to way back, applied both times. Both rows stay on the ledger.

Real rows, one live Meta account, 26 Aug 2026; account not named.

Settled by a dated row, not by whoever sounds most confident.

A client, a freelancer, a platform automation and your own team all touch the same campaigns. The ledger answers with a time, an owner and the old number.

How agencies run accounts with it
Monday, the client call

ClientDidn't we raise the search budget last week? Why is it back down?

FreelancerNot me. I only touched the ads.

Your buyerI'm fairly sure it never went up.

Daily budget raisedGoogle · search campaign · approved in chat $30.99$34.09
Daily budget put backGoogle · same campaign · from the ledger $34.09$30.99

Both happened. Both are on the ledger. Both kept the old number.

Rows: one live Google Ads account, 18 Aug 2026 (₺1,500 → ₺1,650 → ₺1,500 a day, at 48.4069 TRY/USD).

“Who changed this?” deserves an answer you can put back.

The before-state is written at the moment of the write. That is what the agent reads to draft the inverse.

Todaya change historyWalkthrough

YesterdayAd set · targeting edited
2 days agoAd group · status changed
Last weekCampaign · budget edited

It shows something changed. Putting it back is a new edit by hand, from memory.

With Adgentthe Change Ledger

Exclude a country on an ad set · Meta26 Aug · approved by you

BeforeLT: not excluded
AfterLT: excluded

Revert with agent

Not a walkthrough. One live Google Ads account, during testing:

  1. AppliedAd group ENABLED → PAUSEDon approval
  2. LoggedWith the state it replacedin the Change Ledger
  3. Put backPAUSED → ENABLEDchecked in Google Ads

A hand edit in Ads Manager is recorded in the platform change log, not undone.

The before-state is written at the moment of the write, or never.

A ledger started later is empty for every change before it. Adgent logs every write from the first.

  • Changes Adgent makesThe before-state stays ready.Change Ledger
  • Edits in Ads Manager or Google AdsRecorded, not undone.Platform change log
  • Platform automationsRecorded, not undone.Platform change log
See the platform change log

The ledger, plainly.

Can I undo an edit made in Ads Manager?
No. Those are recorded in the platform change log, not undone. Adgent can prepare the old value as a new account move.
Is putting a change back one click?
No. For supported reversible changes, the agent prepares the inverse from the recorded before-state. You approve it, and the put-back lands as its own row. Some action types cannot be reversed through Adgent.
Can I put back something from last week?
For supported reversible changes, earlier rows retain their before-state so the agent can prepare the way back for approval. A recorded history does not make every action type reversible.
Who can see the change history?
Everyone with access to that account's workspace sees the same rows, each with a date and a source. Per-person roles and seats aren't built yet. The history stays with that one company and never appears in another client's account.
How much of this has run on live accounts?
7 of 27 write action types end to end, as of 9 Sep 2026. Put-backs ran on one Meta and one Google Ads account.

See every account move and what it replaced.

Your first applied change lands here with its before-state, owner, time and execution status.

  1. 1
    Connect Meta and Google AdsAdd GA4 or Search Console when useful.
  2. 2
    Adgent reads the accountWith GA4 and Search Console for context.
  3. 3
    You get the decisionsRanked by money, with the evidence under each one.
Pricing