Rule templates
A template is a ready-made rule for a typical traffic arbitrage task: stop-loss, turning off ads, scaling, cutting, signals about creative burnout and CPM spikes. You set a few parameters (target CPD, thresholds, object age), and the template fills in the objects, conditions, actions, schedule and guards itself. There are eight templates.
How to apply a template
Open Meta / TikTok → Autorules, click “From template” and select a template. The builder opens with a new rule assembled with default parameters. The second way is the “Templates” button in the new rule builder: in the “Start from a template” dialog, select a card, set the parameters and click “Apply template”.
A banner “Built from the template “…”” with the parameter values appears above the steps. To change them, click “Change parameters”. Values are validated immediately: “Allowed from … to …”, “Enter a whole number”.
On the “Name and ad accounts” step, select the ad accounts — the template does not set them. If you did not enter a name, the rule gets the template name. Names are unique within a team: a second rule from the same template needs a different name.
Check the “Objects in the rule now” counter on the “Which objects” step and the “Preview” for each ad account.
Click “Create in dry-run”. The rule is created disabled and in test mode: enable it, watch the log for a day or two, and only then switch it to Live.
What all templates have in common
Active objects only. The “Which objects” step has the “Status: Active” filter — the rule does not touch what you turned off yourself.
No CBO/ABO filter. Budget templates do not narrow objects by budget type: if an action does not apply to an object, the preview and the log show the reason (“Budget is set on the campaign (CBO)”, etc.).
Noise protection. Each template has a volume threshold — by spend, impressions or number of installs — so that the rule does not fire on objects with negligible stats.
Revenue by cohort and full days. ROI and deposits are counted by click date (cohort) and, as a rule, for “yesterday” and “3 full days”: this way today's deposits that have not arrived yet do not look like a loss. The exception is the stop-loss, which deliberately looks at “today”.
Only new objects. Stop-loss, turning off ads, scaling and cutting work by default only on objects younger than 7 days since first spend (the “Only objects younger than N days since first spend” parameter). Objects that have ramped up leave the rule on their own.
Other settings are default: priority 50, pause after a manual change 24 hours, allowed data lag 90 minutes, notifications about actions and errors, ad account budget cap not set.
Budgets are in the ad account currency. The values 500 and 20 are designed for USD and similar currencies. For JPY, IDR, KRW, VND and the like, they need to be changed. Spend and cost thresholds (CPD, CPI) are always in USD.
Important. The “zero deposits” and “zero installs” templates (stop-loss, turning off ads, new campaign watch) are reliable only if the ad account's tracker sources pass the campaign, ad set and ad IDs. If none of them does, live mode in the ad account is blocked; if only some do, objects of uncovered sources will look like “no deposits”. Check the attribution warnings in the preview.
Templates overview
Template | Level | Action | Schedule | Cooldown / actions per day |
|---|---|---|---|---|
Stop-loss: no deposits today | Ad sets | Pause until end of day | Every 30 minutes | 0 h / 2 |
Kill ads without installs | Ads | Pause | Every hour | 24 h / 1 |
Scale profitable | ABO ad sets or CBO campaigns | Daily budget +20% | Every hour, 06:00–24:00 | 24 h / 1 |
Cut unprofitable | ABO ad sets or CBO campaigns | Daily budget −30% | Every hour, 06:00–24:00 | 24 h / 1 |
Creative burnout alert | Ads | Notify | Every 3 hours | 24 h / 1 |
CPM spike alert | Ad sets | Notify | Every 3 hours | 24 h / 1 |
Expensive installs | Ad sets | Notify or daily budget −20% | Every 3 hours | 24 h / 1 |
New campaign watch | Campaigns | Notify | Every 3 hours | 24 h / 1 |
All schedules and windows follow the time zone of each ad account.
1. Stop-loss: no deposits today
Purpose. Keep a new ad set from burning through its daily budget if it brings no deposits today. A classic for gambling, betting and nutra with pay-per-deposit.
How it works. Level — ad sets. The rule pauses an ad set until the end of the day if, at the same time:
today's spend is more than two target CPDs;
deposits from today's clicks (by click date, cohort) are zero.
At 00:00 in the ad account time zone, the ad set is enabled again and gets a new chance with the new day. Target CPD $30 → stop when today's spend exceeds $60 without a single deposit.
Parameter | Default | Allowed |
|---|---|---|
Target cost per deposit, USD | 30 | 0.01 – 1,000,000 |
Only objects younger than N days since first spend | Yes | Yes / no |
Object age limit, days | 7 | 1 – 90 |
Schedule and guards: every 30 minutes, around the clock; cooldown after an action 0 hours, no more than 2 actions per ad set per day.
Why the cooldown is 0: the cooldown runs across midnight, and 12 hours after a pause at 20:00 would leave the ad set unattended until 08:00, although at 00:00 it is already spending again. There will be no repeated pause anyway: a paused ad set drops out of the rule (it looks only at active ones), and the pause after a manual change (24 hours) protects against a repeated pause after manual enabling.
Tips.
Set the target CPD slightly above the real one: the “two CPDs without a deposit” threshold already accounts for deposits that may arrive with a delay.
Give the stop-loss a high priority (80–100) so that when it coincides with scaling, the pause takes precedence (it already beats a budget increase, but priority matters in disputes with other pauses).
Risks.
Deposits arrive with a delay: today's cohort is still “maturing”, so the rule will sometimes stop a live ad set. The cost of the error is limited — the pause lasts only until midnight.
Without configured attribution (the ad set ID is not passed to the tracker), everyone has “zero” deposits — see the preview warnings.
If you enabled an ad set manually, the rule will not touch its status for 24 hours — remember that the stop-loss is “silent” on this ad set during that time.
2. Kill ads without installs
Purpose. Turn off creatives that have spent budget and produced no installs — for example, when running traffic to PWA or apps.
How it works. Level — ads. The rule pauses an ad (permanently) if:
lifetime spend (since first spend) is above the threshold;
lifetime installs are zero.
Parameter | Default | Allowed |
|---|---|---|
Spend since launch above, USD | 20 | 1 – 1,000,000 |
Only objects younger than N days since first spend | Yes | Yes / no |
Object age limit, days | 7 | 1 – 90 |
Schedule and guards: every hour; cooldown 24 hours, 1 action per day.
Tips. Set the spend threshold based on the install cost in the GEO: in expensive GEOs, $20 may be less than one normal install cost — raise the threshold. Add the “Notify” action to see which creatives were turned off.
Risks.
The pause is permanent: the rule will not enable the ad again.
If installs do not reach the tracker with the ad ID, the rule turns off all ads with spend above the threshold. With no attribution at all, live mode is blocked; with partial attribution, the risk remains.
3. Scale profitable
Purpose. Raise the budget of setups that are consistently profitable, without manual monitoring.
How it works. The rule raises the daily budget by the specified percentage if, at the same time:
ROI yesterday (by click cohort) is above the threshold;
ROI over the 3 full days before today (yesterday and the two days before it, by cohort) is above the threshold;
spend over the same 3 full days is above the threshold.
The budget is not raised above the maximum (and does not go below 1). It is checked from 06:00 until the end of the day in the ad account time zone — by morning, deposits from yesterday's evening clicks have had time to arrive. No more than once a day per object.
Parameter | Default | Allowed |
|---|---|---|
Level | Ad sets (ABO campaigns) | Ad sets (ABO campaigns) / Campaigns (CBO) |
Cohort ROI yesterday above, % | 50 | −99 – 1000 |
Cohort ROI over the last 3 full days above, % | 30 | −99 – 1000 |
Spend over the last 3 full days above, USD | 100 | 1 – 1,000,000 |
Budget increase, % | 20 | 1 – 100 |
Maximum daily budget, account currency | 500 | 1 – 1,000,000,000 |
Only objects younger than N days since first spend | Yes | Yes / no |
Object age limit, days | 7 | 1 – 90 |
Schedule and guards: every hour, activity window every day 06:00–24:00; cooldown 24 hours, 1 action per day.
Example: an ABO ad set with a $100 budget, ROI yesterday 65%, over 3 days 40%, spend over 3 days $280 → on the first run after 06:00 the budget becomes $120, and the next increase is possible no earlier than a day later.
Tips.
Right after applying, set the ad account budget cap on the “Guards and notifications” step — the template does not know it and warns: “Budget action without an ad account budget cap”.
For CBO campaigns, select the “Campaigns (CBO)” level; for a mixed ad account, create two rules.
If you want to be more careful, lower the increase to 10–15% or add “Daily growth limit” to the action.
Risks.
The maximum of 500 is in the ad account currency. In a JPY ad account, that is ¥500: budgets above it will never be raised. Change it.
With a 24-hour cooldown and hourly runs, the moment of the increase gradually shifts to a later time from day to day. If this is a problem, reduce the cooldown (for example, to 18–20 hours): “no more than once a day” still keeps the limit at 1 action.
Ad sets of CBO campaigns and ABO campaigns at an unsuitable level will be skipped with the reason “not applicable” — this is normal.
4. Cut unprofitable
Purpose. Lower the budget of setups that are steadily going into the red, without turning them off completely.
How it works. The rule lowers the daily budget by the specified percentage if:
ROI over the 3 full days before today (by cohort) is below the threshold;
spend over the same 3 full days is above the threshold.
The budget does not go below the minimum; there is no upper bound for the decrease. It is checked from 06:00 until the end of the day in the ad account time, no more than once a day per object. Example: ROI over 3 days −35%, spend $150, budget $80 → $56; with a $25 budget → $20 (minimum).
Parameter | Default | Allowed |
|---|---|---|
Level | Ad sets (ABO campaigns) | Ad sets (ABO campaigns) / Campaigns (CBO) |
Cohort ROI over the last 3 full days below, % | −20 | −99 – 100 |
Spend over the last 3 full days above, USD | 100 | 1 – 1,000,000 |
Budget decrease, % | 30 | 1 – 90 |
Minimum daily budget, account currency | 20 | 1 – 1,000,000,000 |
Only objects younger than N days since first spend | Yes | Yes / no |
Object age limit, days | 7 | 1 – 90 |
Schedule and guards: every hour, window 06:00–24:00 every day; cooldown 24 hours, 1 action per day.
Tips. Do not remove the 06:00 window: in the first hours of the day, yesterday's cohort still lacks some deposits, ROI is understated, and the cut would fire on the least mature data. Set the minimum no lower than the minimum budget at which the ad set still makes sense for you.
Risks. The minimum of 20 is in the ad account currency: in a JPY ad account, the rule can cut the budget down to ¥20. If scaling also runs on the ad account, give the cut a higher priority or separate the ROI thresholds so that the rules do not fight over one budget.
5. Creative burnout alert
Purpose. Find out that a creative is “burning out”: CTR today is noticeably lower than usual.
How it works. Level — ads. A notification is sent if:
CTR today is lower than the CTR of the same ad over N full days before today by the specified percentage;
impressions today are above the threshold.
Example: CTR over 7 full days 1.5%, drop 40% → notification if today's CTR is below 0.9% with 1000+ impressions.
Parameter | Default | Allowed |
|---|---|---|
CTR drop vs. baseline, % | 40 | 5 – 95 |
Baseline, full days before today | 7 | 2 – 30 |
Impressions today above | 1000 | 1 – 100,000,000 |
Schedule and guards: every 3 hours; cooldown 24 hours, 1 action per day — no more than one signal per day per ad.
Tips and risks. In the morning, with a small number of impressions, CTR fluctuates — do not set the impressions threshold too low. If the creative has weekly seasonality (weekends), use a 7- or 14-day baseline. The template does not turn anything off — the decision is yours.
6. CPM spike alert
Purpose. Notice a sharp rise in the cost of impressions: the auction is overheated, the audience is burned out, or the ad set has gone back into learning.
How it works. Level — ad sets. A notification is sent if CPM today is higher than yesterday's by the specified percentage and today's spend is above the threshold. Example: yesterday CPM $8, growth 50% → signal when CPM today is above $12 and spend is more than $20.
Parameter | Default | Allowed |
|---|---|---|
CPM growth vs. yesterday, % | 50 | 5 – 1000 |
Spend today above, USD | 20 | 1 – 1,000,000 |
Schedule and guards: every 3 hours; cooldown 24 hours, 1 action per day.
Tips and risks. At the start of the day, CPM is often above average — that is why there is a spend threshold. If there are too many signals, raise the percentage or the spend threshold.
7. Expensive installs
Purpose. Monitor the install cost (PWA, apps) and, if you wish, automatically cut the budget of ad sets where installs have become more expensive.
How it works. Level — ad sets. It fires if CPI over the last 24 hours is 1.5 times above the target and installs over 24 hours are above the threshold. Ad sets with fewer installs over 24 hours than the threshold are not evaluated at all (“Below the minimum volume”). Target CPI $2 → signal when CPI is above $3.
The action is selected by a parameter: “Notify” (default) or “Lower the daily budget” by the specified percentage, not below the minimum. The decrease works only for ad sets of ABO campaigns; ad sets of CBO campaigns will be skipped with the reason “Budget is set on the campaign (CBO)”.
Parameter | Default | Allowed |
|---|---|---|
Target cost per install, USD | 2 | 0.01 – 1,000,000 |
Installs over the last 24 hours above | 10 | 1 – 1,000,000 |
Action | Notify | Notify / Lower the daily budget |
Budget decrease, % (only when lowering) | 20 | 1 – 90 |
Minimum daily budget, account currency (only when lowering) | 20 | 1 – 1,000,000,000 |
Schedule and guards: every 3 hours; cooldown 24 hours, 1 action per day.
Tips and risks. The “last 24 hours” window is rolling and includes the current hour. Start with notifications and switch to lowering the budget once you are sure the threshold does not catch normal fluctuations. The 1.5 multiplier is fixed in the template; you can set a different threshold in the finished rule on the “Conditions” step.
8. New campaign watch
Purpose. Get a signal if a freshly launched campaign is spending but there are no deposits — before the stop-loss or a manual check notices it.
How it works. Level — campaigns; only active campaigns younger than the specified number of days since first spend get into the rule — a campaign leaves the watch on its own when it becomes older. A notification is sent if lifetime spend is above the threshold and deposits from the campaign's clicks (cohort) are zero. The last 2 hours are counted neither in spend nor in deposits: clicks from the last hours have not yet had time to produce a deposit.
Parameter | Default | Allowed |
|---|---|---|
Campaign age limit, days since first spend | 3 | 1 – 30 |
Spend since launch above, USD | 50 | 1 – 1,000,000 |
Schedule and guards: every 3 hours; cooldown 24 hours, 1 action per day.
Tips and risks. Set the spend threshold at about 1.5–2 target CPDs. The signal is reliable only if the campaign ID is passed to the tracker; campaigns that were spending before the ad account was connected have unknown age and do not get into the rule.
How to change parameters after applying
Before the rule is saved
While the rule has not been created, the “Built from the template” banner has the “Change parameters” button, and the header has “Templates” and “Another template”. Applying again overwrites the objects, conditions, actions, schedule and guards with the template values; the selected ad accounts, name and description are kept. There is no separate confirmation: if you have already edited the steps manually, those edits will be lost. The banner reminds you of this: “The steps were changed after the template was applied: the parameter values above may no longer match the rule”.
After saving
A saved rule is an ordinary rule: it has no link to the template and no “Change parameters” button. Values are changed directly in the builder steps:
Template parameter | Where to change it in a saved rule |
|---|---|
Target cost per deposit (stop-loss) | “Conditions”: today's spend threshold = 2 × new CPD (CPD $40 → “Spend above 80”) |
Target cost per install (expensive installs) | “Conditions”: CPI threshold = 1.5 × new CPI (or any value of your own) |
Spend, impressions, installs thresholds | “Conditions”: values of the corresponding conditions |
ROI thresholds | “Conditions”: ROI value in percent |
CTR drop, baseline in days; CPM growth | “Conditions”: the “Same metric in another window” comparison — percentage and baseline window |
Budget increase / decrease, % | “Actions”: “Change, %” |
Maximum / minimum daily budget | “Actions”: “Not above” / “Not below” |
Action (expensive installs) | “Actions”: remove “Notify” and add “Change budget” (or vice versa) |
Only new objects, age limit | “Which objects”: the “Only new objects” toggle and “younger than N days” |
Level (scale, cut) | “Name and ad accounts”: “Level” — conditions and actions will be rechecked |
Schedule, windows, guards (not parameters in templates) | The “Schedule” and “Guards and notifications” steps |
Tip. After any edit, check the preview again. If the rule is already live, only a role with the Live permission can save the edit.