Automation

Action frequency

Updated 20 August 2026

Action frequency is the cooldown on an automated action: the minimum time that must pass before the same rule may perform the same action on the same item again, regardless of how often the rule itself is evaluated.

Key facts about Action frequency

Also known as
Action cooldown
Category
Automation
Last updated
20 August 2026

In AdOps

How does Action frequency work inside AdOps?

Action frequency is set per task in AdOps, with 11 values from 15 minutes to Once in a lifetime. Five actions accept it — Notify, Duplicate, Increase budget, Decrease budget and Set budget — and a rule that re-evaluates before the cooldown expires records a skipped result instead of acting again.

The AdOps metric picker open over a condition row: a panel with Meta Ads and Custom metrics tabs, a search box, and a scrolling list of metrics with Spend selected. Sample data
Forty-five Meta metrics and your own sheet columns in the same list, each carrying a reporting period and any of six operators. Read the details

Action frequency is the cooldown between repeats of the same automated action. In AdOps it is set on the task, not the rule, so a rule can be evaluated every 15 minutes while a given campaign’s budget is only ever raised once every 2 hours. Eleven values are available, from 15 minutes to Once in a lifetime.

What are the 11 options?

15 minutes, 30 minutes, 1 hour, 2 hours, 3 hours, 6 hours, 12 hours, Once a day, Once in 2 days, Once in 3 days and Once in a lifetime. Five actions accept a frequency: Notify, Duplicate, Increase budget, Decrease budget and Set budget. The remaining six actions run whenever their conditions pass.

What happens when the cooldown blocks an action?

The run is recorded, not silently dropped. When an action fires, the engine stores the next permitted time for that task and campaign; Once in a lifetime pins it to 1 January 2100. If the rule re-evaluates before then, the log records a skipped result with the reason, so the rule log shows why nothing changed.

Why does the cooldown matter for budget rules?

Because a percentage increase compounds. A campaign at Rp 2,000,000 a day raised by 20% every 15 minutes would pass Rp 4,000,000 within an hour. Capping the same task at once every 2 hours is what the shipped Tiered Budget Scaling template does for each of its three ROAS tiers.

Glossary

The terms an advertiser usually reads in the same sitting.

Turn this metric into a rule that watches it.

Pick the metric, pick one of the 11 reporting periods, set the threshold, and choose what happens when it is crossed. Nothing runs on your campaigns until you set the rule live.

Contact us See pricing

14-day trial · no card

Inside the product

What the screens actually look like

Nine screens from the working dashboard — the rule builder, the metric picker, the dayparting grid and the log that records what happened. Scroll the strip.

  • The AdOps Performance Dashboard showing a Purchase ROAS card at 2.380x and an Aggregated ROAS card at 2.088x, both badged Profitable, a Monthly Budget card at Rp 155jt, and a Spend Breakdown ranking the top five ad accounts against a budget utilisation bar at 45.5 per cent.
    Performance Dashboard. Two ROAS figures to three decimals, a budget meter, and spend ranked by ad account — over Today, Last 7 days, Last 30 days or This month.
  • The AdOps rule list showing twelve automation rules, each with an on/off toggle, the ad accounts it manages, and when it last triggered — some minutes ago, others on a dated timestamp.
    Rule List. Every rule, what it manages and when it last fired. The toggle is the only thing between draft and live.
  • The AdOps condition builder showing a task with time-of-day conditions across seven day tags, a nested AND group holding a lifetime spend condition under 400,000, and a second task with four stacked metric conditions.
    Conditions. Metric, period, operator, value — joined with AND or OR, and nestable, so a rule can say something a dropdown cannot.
  • The AdOps metric picker open over a condition row: a panel with Meta Ads and Custom metrics tabs, a search box, and a scrolling list of metrics with Spend selected.
    Metric picker. Forty-five Meta metrics and your own sheet columns in the same list, each carrying a reporting period and any of six operators.
  • The AdOps dayparting timetable: a grid of hours against the seven days of the week, with the daytime hours filled navy for every day and the night hours and weekend evenings left empty.
    Dayparting grid. Or draw the hours instead. Anything outside the shape you fill in simply does not run.
  • An AdOps execution log detail: one campaign, two action panels badged Not Executed, each listing the action parameters and every condition evaluated with its actual value, its expected value and a Pass or Fail badge.
    Rule Log detail. Why a rule did nothing is recorded as carefully as why it did something — actual against expected, condition by condition.
  • The AdOps activity log listing budget increases and campaign renames, each row naming the affected campaign by id, the rule that caused it and how long ago it happened.
    Activity Log. One row per change AdOps made in your account, naming the campaign and the rule responsible.
  • The AdOps ad account list: eighteen Meta ad accounts with on/off toggles, account ids, Active or Inactive badges and this month’s spend in rupiah.
    Ad Accounts. Accounts discovered from Meta arrive switched off. Nothing is read, and nothing is changed, until you turn one on.
  • The AdOps custom metric editor mapping a Google Spreadsheet: a spreadsheet id, a sheet name, a column to match campaigns on and a column holding the values.
    Custom metric. Point AdOps at a sheet, name the matching column and the value column, and your own number joins the metric list.

Every figure is rebuilt from the product’s own interface and filled with invented data — no customer name, ad account or spend figure appears anywhere on this site. See how a run works