Skip to content

Action Log & Restore

Every change you apply through Aliveo — from a chat, a workflow, or an agent — is recorded in the Action Log: a full, auditable history of what changed, from what to what, who applied it, and where it came from. From the log you can measure the impact each change had, and restore most changes with one click if you want them undone.

The Action Log works the same across every actioning platform — Google Ads, Facebook (Meta), Apple Search Ads, LinkedIn, Amazon Ads, Snapchat, and TikTok.

1. The Action Log

Open Action Log from the sidebar. Entries are grouped by day (Today, Yesterday, then dates), one row per applied action — if you applied a table of 3 keyword bid changes in one go, that's one row covering 3 keywords.

Each row shows:

Column What it shows
Action What kind of change it was — e.g. Keyword bid update · 3 keywords, Campaign daily‑budget update, Ad group status update — with the time it was applied
Account The ad platform and account the change was applied to
Actor Who applied it
Source Where it came from — a workflow, a chat, or a restore — linked so you can jump back to the conversation or run that produced it
Status How many entities succeeded, e.g. 3 OK or 2 OK · 1 fail
Impact What the change did to performance (see Impact)

Expanding a row lists every entity in the batch with its field, before → after values, and whether it's reversible. Failed entities show the attempted value and the platform's error message.

Filters along the top narrow the history: date range (up to 6 months back), accounts, actor (All actors / Me), action type, source, and status (OK / Failed).

Clicking a row opens a detail sheet with the full provenance (actor, account, source, success count), the impact summary, and a card per entity showing exactly what changed. You can jump to the originating chat or workflow from its footer. The same sheet opens when you click an Applied badge on any action table elsewhere in Aliveo.

2. Restore

Applied something you want back the way it was? Restorable actions carry a Restore button on the row (and Restore this action in the detail sheet).

How it works

  1. Click Restore. Aliveo re‑reads the live values from the ad platform and builds a preview — so you're deciding against what the account looks like now, not a stale snapshot.
  2. The preview lists each field it can put back, pre‑selected, with the exact effect spelled out: now X → restore to Y. Fields that belong together (e.g. a bidding strategy and its target) share one checkbox and are restored together.
  3. Deselect anything you want to keep, then click Restore N.
  4. The restore is applied through the same pipeline as any other action — validated, sent to the platform, and recorded as a new Action Log entry with source restore, pointing back at the action it reverts. The original row flips to Restored (or offers Restore rest if you only restored some entities).

What's restorable

  • Value changes (budgets, bids, goals…) are reverted to the recorded previous value.
  • Status changes are toggled back (e.g. re‑enable what was paused).
  • Created entities (keywords, negatives, campaigns…) can't be un‑created — restore pauses them instead. The preview calls this out before you confirm.

A few things are held back, each with a plain‑language reason in the preview:

  • Fields that are already at their previous value, or that had no recorded prior value.
  • Fields the platform treats as immutable after creation.
  • Entities already reverted by an earlier restore — restore is one‑shot per entity, so you can't ping‑pong a value from the log.
  • Entities whose current value can't be verified against the platform.

If the value changed again after your action, it's still restorable — the preview warns you that the current value no longer matches what you changed it to, and restoring overwrites it with the recorded previous value.

Permissions. Restoring is actioning, so it follows the same rules as applying a change: primary users can restore by default, secondary users need actioning permission for that account or platform, and read-only users can't. Anyone with actioning access on the account can restore any action on it, not just their own. See Actioning Permissions.

3. Impact

The Impact column answers "what did this change actually do?" — comparing each entity's performance in the 7 days after the change against the 7 days before.

  • Fresh changes show Pending until the 7‑day window matures.
  • Measured changes show a headline delta (e.g. CPA −18%) with cost, impressions, clicks, and conversions in the tooltip. CPA headlines carry a quick read — Good, Neutral, or Watch (worth a look, not necessarily wrong).
  • Created entities show their first‑7‑days totals instead of deltas — there's no "before" to compare against.
  • Some changes can't be measured cleanly and say so: Superseded (the entity changed again within the window) or No traffic (no spend or impressions on either side). A * marks entities whose baseline includes another recent change.

Impact is informational — it never blocks a restore or a new change; it's there so you can close the loop on whether an optimization did what you expected.

Apply with confidence: everything is logged, most things can be restored, and the log tells you whether each change paid off.