Custom automations
Beyond the five recommended automations, you can compose your own from a metric-based detection condition and a supported action. Custom automations run through the same execution pipeline as the recommended ones — the same guard chain, cooldowns, caps, brand protection, audit log, and revert flow.
Where to build one
Settings → Automations → scroll to the Custom automations section at the bottom of the page. Click "Create custom automation". A composer dialog opens.
What you can build
Each custom automation pairs a detection condition with an action.
Supported actions:
- Add a search term as a negative keyword on the triggering campaign.
- Pause a keyword.
- Raise a campaign's daily budget.
- Lower a campaign's daily budget.
- Raise a campaign's Target CPA.
- Lower a campaign's Target ROAS.
Detection. The condition defines what triggers the action — which metric to watch, the threshold, and the window. The available conditions cover keyword and campaign spend versus conversions, CPA relative to a historical baseline, and ROAS relative to a historical baseline.
The same guards apply
Custom automations go through the same guard chain as recommended ones. A budget or bid action on a Target CPA or Target ROAS campaign is still blocked by the smart bidding exclusion. Brand protection still applies for negative keyword and keyword pause actions. Cooldowns and daily caps still apply for every action verb.
The hardcoded caps per action verb — the floor below configurable settings:
| Action | Daily cap | Cooldown | Weekly cumulative cap |
|---|---|---|---|
| Add negative keyword | 3 | 14 days | — |
| Pause keyword | 3 | 14 days | — |
| Raise or lower campaign budget | 3 | 7 days | 50% |
| Raise Target CPA | 2 | 14 days | 20% |
| Lower Target ROAS | 2 | 14 days | 20% |
These caps cannot be overridden, even on custom automations.
The dry-run preview
The first-enable dry-run gate applies to custom automations. When you turn one on for the first time, the preview modal shows candidates and guard-blocked executions for the last 30 days under your detection condition and action.
Managing custom automations
Each custom automation appears as a card in the Custom automations section of the settings page. The toggle enables or disables it. The delete button removes the automation permanently, after a confirmation step.
Deleting a custom automation does not delete its history. Past executions remain in the automation history log.
Shared caps across automations
The per-verb daily caps are shared across all automations of the same type — recommended and custom. Two automations that both pause keywords share the 3-per-day keyword-pause cap. If you build a custom automation that overlaps heavily with a recommended one, they compete for the same daily allowance.
Next
- Automation history. Custom automation executions appear in the same shared log.
- Recommended automations. The built-in automations to compare when composing your own.
- Turn on an automation. The first-enable dry-run flow applies to custom automations the same way.