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, Meta (Facebook & Instagram), LinkedIn, Apple Search Ads, Amazon Ads, Snapchat, TikTok, and Moloco. The one exception is Google Ads callout extensions and conversion actions: they're created straight away, without an Apply step, so they aren't logged (see Actioning Google Ads).

1. The Action Log

Open Action Log from the sidebar. It lists every change applied across your ad accounts from within Aliveo, newest first and grouped by day (Today, Yesterday, then dates). Each card is one applied action — if you applied a table of 3 keyword bid changes in one go, that's one card covering 3 keywords.

Each card shows:

Part What it shows
Action What kind of change it was — e.g. Keyword bid update, Campaign daily‑budget update, Ad group status update — and how many entities it covered, e.g. 3 keywords
Status How many entities succeeded, e.g. 3 OK or 2 OK · 1 fail
Impact What the change did to performance (see Impact)
Time, account and actor When it was applied (in UTC), the ad account (with its platform icon), and who applied it (initials — hover for the email)
Restore Shown on actions you can restore (see Restore)

Click the arrow on a card to expand it. You'll see each entity with its Field, Before → After values, and whether it's Reversible. The first 3 entities show straight away; view all shows the rest. Failed entities show the attempted value struck through, with the platform's error message.

To narrow the history, use the Accounts picker, the date range (the last 30 days by default, up to 6 months back), the All actors / Me toggle, and the Filters menu, which filters by Status (OK / Failed), Action, and Source.

Click a card to open its detail sheet:

  • Provenance — the actor, the account, the Source (a workflow, a chat, or a restore, linked to the chat or workflow when it's yours; a restore also names the action it reverts) and the status (e.g. 3 / 3 succeeded).
  • Impact — the impact summary.
  • Changes — a card per entity showing exactly what changed.

At the bottom, View in chat or View in workflow takes you back to where the change came from (for your own chats and workflows), and Restore this action starts a restore. The same sheet, without the restore button, 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 card (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 entity it can put back, pre‑selected, with the exact effect on each field spelled out: now X → restore to Y. Each entity has one checkbox, and all of its fields are restored together — you can't deselect a single field. Anything that can't be restored is shown greyed out, with the reason.
  3. Deselect any entity 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 card shows Restored, or Restore rest while some of its fields are still unrestored.

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.
  • Fields already restored by an earlier restore of the same action. Restore is tracked per field, so you can restore the rest of an action later without touching what's already been put back.
  • Fields 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 chip 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 Impact in N days or Impact soon until the 7‑day window has passed.
  • 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.