Change log

Open Change log in the sidebar of your workspace. It lists every change made to your ads through Roasby, newest first: by you, a teammate, an AI assistant, or Roasby itself. Pick one account with the Ad account menu, or keep All accounts. Change log on an ad account in Ad accounts opens it for that account.

The short version is in the safety model: A change log you can revert.

What each entry shows

• Change: the item (for example Campaign: Summer sale), what changed with the value before and after (for example a daily budget from $20.00 to $30.00), and the ad account with its platform. Ad text and keyword edits show each part that changed.
• By: who or what made the change, and when.
• Status: whether the ad platform applied it.
• Revert, for an applied change you may revert.

A change that failed shows the ad platform's reason in red under it.

Statuses

• Pending: Roasby sent the change and waits for the ad platform. The page updates on its own once it applies.
• Applied: the ad platform made the change.
• Failed: the ad platform refused it, with the reason.
• Reverted: a later revert put the value before back.

A batch shows as one entry: Applied, Partly applied or Failed. Open it to see each item. A batch is reverted only once it has finished.

A campaign settings change the ad platform took only in part shows Partly applied, with the parts it refused and why. The parts it took can be reverted.

An applied status, budget or bid change shows in Roasby at once. After a new campaign, Roasby usually syncs that ad account within a few minutes, so everything the platform made shows.

Revert a change

Anyone who may change ads (owners and admins, and members when the workspace allows it, see Workspaces) can revert an applied change:

1. Choose Revert on the change.
2. Read what the revert will do, and confirm.

The revert is a new change in the log. It goes to the ad platform like any other change and is Pending until it applies. For a batch, Revert batch puts back every item the batch applied, as a new batch; you can still revert one item of a batch on its own.

What a revert does

• A status, budget or bid: puts the value before back.
• A new campaign, ad group, ad or keyword: pauses it. Roasby never deletes anything.
• Added negative keywords: takes away exactly the ones that change added; ones that were there before stay. Reverting that adds them again.
• Ad text: writes the ad's old text back. The ad keeps its status, and the ad platform reviews the text again.
• A keyword edit: puts the keyword back as it was. When the edit replaced the keyword, the new one is paused and the old one comes back.
• Campaign settings: restores only the sections the change touched, such as countries or the ad schedule.
• Bidding and conversion goals: puts the strategy, every target and the goals back as they were. One exception: Microsoft Ads doesn't take a max cost per click again after a strategy switch, so the strategy comes back without it (the preview says so).
• A new asset link: pauses the link. On Microsoft Ads, which can't pause a link, the link is taken away; the asset stays.

Guardrails on reverts

A revert is checked by the same guardrails as any change, with one exception: a revert by a person skips the max change per step, because it restores a value the item already had. A revert by an AI assistant is held to the max change too.

So some reverts only a person can make, on the web. For example, when a bidding target is now beyond a guardrail (the max bid, max target CPA or min target ROAS) or the max bid change, your assistant's revert is refused with revert_past_guardrails; your own revert on the Change log page restores the exact target the campaign had.

What can't be reverted

A revert is refused with the reason when:

• the change isn't applied (not_applied);
• it was already reverted (already_reverted). A revert the ad platform refused can be tried again;
• the item changed again since (changed_since). Revert the newer change first;
• there is nothing to take away, for example negative keywords that already existed (nothing_to_revert);
• every item a batch added is still paused, so a revert would change nothing;
• the campaign now uses bidding Roasby could not set back (bidding_not_revertible).

The ad account's state counts too:

• Read-only: over the limit: only a person can revert, on the web. Your assistant can't.
• Read-only: set by support: every change is refused, reverts included.
• Disconnected: its change log is deleted, so earlier changes can no longer be reverted from Roasby.

Ask your AI assistant

Your assistant reads the log with list_ad_changes (one ad account with ad_account_id; one campaign, everything in it and the change that created it, with campaign_id; days with from and to; a batch's items with batch_id). It reverts a change like any other change, with a preview you confirm:

• one change: preview_revert_ad_change, then revert_ad_change;
• a batch: preview_revert_ad_change_batch, then revert_ad_change_batch.

Try "What did you change in my Google Ads account today?", "Which changes failed this week, and why?" or "Revert yesterday's budget change on the Summer sale campaign."

Limitations

• A change can be reverted once (a revert the ad platform refused can be tried again), and only while the item still has the value it set.
• An AI assistant's revert keeps the max change per step; a person's revert on the web doesn't.
• Reverting never deletes: new items are paused, and only negative keywords, targeting and (on Microsoft Ads) asset links a Roasby change added are taken away.
• The log shows changes made through Roasby only. Changes made in the ad platform itself show in Roasby after the next sync, but not in the log.

See every limit by platform on Limitations.