Stop-loss rule: pause ad sets that spend without results
Short answer: pause an ad set when today's spend reaches a fixed amount and it still has zero results. Set the amount relative to your target cost per result, usually one to two targets, so every ad set gets a fair chance and no ad set burns a whole budget on nothing. Check it continuously, in the ad account's time zone, and treat "no data yet" differently from "zero results".
The template
| Setting | Value |
|---|---|
| Apply to | Ad sets (in a 1-1-1 structure the ad set is the test unit) |
| Condition 1 | Spend today ≥ your stop amount |
| Condition 2 | Results today = 0 |
| Join | Both conditions (AND) |
| Action | Pause the ad set |
| Check | Continuously during the day |
| Notify | Every time the rule pauses something |
Choosing the stop amount
Start from the cost you can pay for one result. With a target of $20 per result, a stop at $25–35 of spend gives each ad set between one and two targets to produce its first result. A stop below one target kills ad sets that were about to convert; a stop at three or more targets lets losers spend for too long.
| Target cost per result | Aggressive stop | Balanced stop | Patient stop |
|---|---|---|---|
| $5 | $5 | $7.5 | $10 |
| $20 | $20 | $30 | $40 |
| $50 | $50 | $75 | $100 |
These are worked examples of the 1×, 1.5× and 2× logic, not advice for a particular offer.
Edge cases that make this rule misfire
- Delayed conversions. Meta can report a result hours after the click. A strict rule pauses an ad set that already converted but has not shown it yet. Leave a margin, or allow the rule to switch the ad set back on when the result appears.
- Time zones. "Today" is the ad account's day, not yours. Accounts in different time zones reach their stop amounts at different local hours.
- Missing data is not zero. If the latest numbers have not loaded, a rule that reads them as zero results pauses everything. Rules should skip objects whose data is not fresh.
- Paused by someone else. If a person paused or resumed the ad set by hand, the rule should not fight them.
Setting it up in Meta Ads Manager
- Open Rules in Ads Manager and choose to create a new rule.
- Apply the rule to ad sets and choose the action to turn them off.
- Add the conditions: amount spent greater than your stop amount, and results less than 1.
- Choose today as the time range and a continuous schedule.
- Add yourself as the person who gets notifications, and save.
The rule lives inside one ad account. With many accounts you create and maintain it in each of them.
Setting it up once for all ad accounts in Multitool ADS
In Multitool ADS a rule covers every ad account in the workspace:
- Conditions joined by AND or OR, on the ad set level (or campaign, ad or account level).
- Time windows: today, yesterday or the last N complete days, each in the ad account's own time zone.
- Scope by country and by name, for example only ad sets targeting one country.
- Objects whose data is not fresh are not judged as zero.
- An ad set paused by the rule is switched back on automatically within an hour if the condition no longer holds, for example when a delayed result arrives.
- A Telegram notification for every pause.
The live demo shows the cross-account table these rules work on, with demo ad accounts, no account needed.