Automation history
The history page at /automations is the complete audit log of every action an automation took on your Google Ads account. Every applied, failed, reverted, and preview execution appears here, across all five automations and any custom automations you composed. You can revert any applied action in one click.
Read the log
Each row shows:
- Action description. What happened in plain English, for example "Added negative keyword," "Raised campaign budget," "Paused keyword," "Raised CPA target," or "Lowered ROAS target," with the entity and the before and after values.
- When. Relative time since the action ran, for example "2h ago" or "3 days ago."
- Status badge. One of four values.
| Status | What it means |
|---|---|
| Applied | The action ran and is live in Google Ads. |
| Failed | The automation tried to apply the action, but Google Ads returned an error. |
| Reverted | You reverted a previously applied action. |
| Dry run | A preview execution that Hero Marketer never applied. The card shows it as "Skipped." |
Dry run rows record what an automation would have done over the last 30 days. Hero Marketer writes them when you run the preview required before you enable an automation for the first time. A dry run row also captures the candidates a guard blocked. The log then shows what an automation did, what it declined to do, and the blocking guard's reason.
Filters
Two filters sit at the top of the history page.
- Status. Show only Applied, Failed, Reverted, or Dry run rows.
- Automation. Show only one automation's actions, for example raised budgets, paused keywords, or added negative keywords.
The filters combine, so you can view only the Applied rows from a single automation, for example.
Revert an action
Any Applied row has a Revert button. Every automation's action is reversible. When you click Revert, Hero Marketer:
- Rolls the change back in Google Ads.
- Writes a new row in the log with Reverted status, linked to the original.
- Doubles the cooldown for that entity, so the automation will not touch it again for twice the normal cooldown window.
What a revert restores, by automation:
- Block wasting search terms. A revert removes the negative keyword from the ad group.
- Lift the budget on profitable campaigns being capped. A revert resets the daily budget to the value it held before the raise.
- Pause pure waste keywords. A revert re enables the paused keyword.
- Ease CPA targets on overperformers. A revert restores the Target CPA to its prior value.
- Ease ROAS targets on overperformers. A revert restores the Target ROAS to its prior value.
A custom automation reverts the same way as the recommended automation that carries the same action.
You can revert actions in any order. For example, if you revert a raise from three weeks ago, it does not affect anything that happened since. The doubled cooldown is deliberate. If you roll an action back, the automation should not immediately act on the same entity again. The doubled window gives you time to investigate before it can act again.
Failed executions
A Failed row means the automation tried to apply the action but Google Ads returned an error. Two common causes explain a Failed row: the entity was deleted between when the action was queued and when it ran, or Google Ads rejected a budget or target constraint. Hero Marketer stores the error message from Google. The message shows when you put the pointer on the status badge.
Failed executions do not retry on their own schedule. The automation evaluates again on its next monitoring pass. If the underlying condition still holds and the entity is still eligible, it may act again.
The link to alert drawers
An alert triggers each of Block wasting search terms and Lift the budget, so every execution from those two links to the alert that triggered it. When you open the side drawer for an alert that an automation acted on, the drawer shows a banner with the action taken and a Revert button. A revert from the alert drawer is the same operation as a revert from this page. It lands in this same log with Reverted status. The three grammar automations watch their own metric rule, so their executions appear in this log directly, not through an alert drawer.