# Automatic reactions to anomalies

Some anomalies call for an immediate, standard response. Automatic reactions turn the daily anomaly check into proposals — or, under the auto policy, into applied changes.

## What it does

The reaction table is fixed and conservative: a spend spike leads to a proposal to pause the campaign that contributed most; a rise in cost per conversion leads to a proposal to reduce its budget by 20% (never more than the client's limit). CTR and conversion drops only notify.

Before any reaction: observe clients get nothing; a campaign a person changed recently is left alone during quiet hours (24 by default); at most 3 automatic reactions per client per day; no duplicate while a previous automatic proposal is open. Preliminary data never triggers reactions.

## Why it helps

- Stop runaway spend overnight.
- Consistent, documented responses to common problems.
- Strict caps prevent automation from overreacting.

## How to set it up

1. Enable the anomaly check automation for the client.
2. Set quiet hours and the daily reaction limit.
3. Choose the client's write policy: propose (approval) or auto (reversible changes within limits).

## Good to know

- Automation can never exceed limits; only a human owner can override them.
- Each reaction is logged with the job's trace ID.

---
*Originally published at [AdAce Ads blog](https://ads.adace.website/en/blog/automation/anomaly-reactions).*
