Hero doesn't just flag it. It fixes it.

No. Every automation that pauses or negates runs a brand-allowlist guard sourced from your product profile, plus any terms you add. Pausing your own brand keyword is the classic automation disaster, so the guard exists to prevent it, and the dry run preview shows you any brand matches before you ever enable.

Every action is one click to revert, in any order. Google Ads version history only unwinds changes in strict reverse-chronological order, so you would have to undo Saturday before undoing Friday's mistake. Hero's audit log lets you revert any past execution on its own, whenever you want.

Only after you enable it, and only inside the caps you can see. Every automation ships disabled, requires a 30-day dry run preview before its first enable, and runs under a daily cap, a per-entity cooldown, and a conversion-attribution-lag gate so it never acts on a signal that has not had time to report.

Google's rules read a fixed set of metrics over fixed date windows. They cannot reference a rolling baseline, cannot guard against cross-campaign side effects, cannot honor a long B2B conversion lag, and cannot read your product profile to exclude brand terms. Hero's automations are scoped to exactly those gaps, and a budget raise only executes if Google's own budget simulation projects more conversions at the new budget, which Google's rules cannot do.