Scheduling and pauses
When a rule pauses an ad, it specifies the duration — as the first argument of the pauseAd function (and its counterparts). The duration determines when the ad will return to work. The return happens automatically on the nearest check pass after the term has come.
JavaScript
pauseAd('24h', 'причина'); // на 24 часа
pauseAd('next_day_target_geo'); // до полуночи в стране объявления
pauseAd('while_matches'); // пока выполняется условие
Available durations
| Value | What it does |
|---|---|
6h | A pause for 6 hours. |
12h | A pause for 12 hours. |
24h | A pause for 24 hours. |
next_day_target_geo | Until the start of the next day (midnight) in the time zone of the ad's country. |
next_day_ad_account | Until the start of the next day (midnight) in the time zone of the ad account. |
while_matches | Without a fixed term: the ad is held on pause as long as the rule keeps triggering. As soon as the condition stops being met — the ad returns on its own. |
permanent | No return term. Can only be lifted manually. |
These are the only allowed values. The rule will not accept any other duration value.
How to choose the duration
- Fixed 6h / 12h / 24h — when you need to "cool down" the ad for a specific term and give it another chance.
- Until midnight (in the geo or in the account) — when the logic is tied to the day: a daily budget, daily statistics, delivery by the local day. The difference between the two options — whose time zone to count midnight by: the country where the ad is shown or the ad account's settings.
- While the condition matches — the most "live" mode: the ad automatically goes on pause and automatically returns when the metrics recover. No need to guess the term.
- Permanent — when the ad definitely needs to be stopped and not returned without a manual decision.
Tip
If you don't want to guess the term — start with while_matches. Britva will return the ad itself as soon as the condition stops being met, and pause it again if the metrics worsen again.
The return is not instant
The ad returns to work not exactly at the moment the pause expires, but on the nearest check pass after it. The check runs every 3 minutes, so a delay of up to 3 minutes is normal.