Language
Contact us

Automation

Condition operator

Updated 20 August 2026

A condition operator is the comparison inside an automation condition that decides whether a metric's value passes, such as greater than, less than, or equal to a stated threshold.

Key facts about Condition operator

Also known as
Comparison operator, Rule operator
Category
Automation
Last updated
20 August 2026

In AdOps

How does Condition operator work inside AdOps?

AdOps offers six comparison operators — greater than, less than, greater than equal, less than equal, equal and not equal — and 43 of its 45 metrics expose all six. Conditions inside one task are joined by a single AND or OR group operator.

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. Sample data
Metric, period, operator, value — joined with AND or OR, and nestable, so a rule can say something a dropdown cannot. Read the details

A condition operator is the comparison that turns a metric and a threshold into a pass or a fail. AdOps offers six of them: greater than, less than, greater than equal, less than equal, equal and not equal, shown in the rule builder as the symbols greater-than, less-than, greater-or-equal, less-or-equal, equals and not-equals.

Which operators does each metric accept?

43 of the 45 AdOps metrics expose all six. The two exceptions are the time-of-day metrics: Time greater than accepts only greater than, and Time less than accepts only less than, because each one already states its direction in its name.

How are several conditions combined?

With a single group operator per task, either AND or OR. A task that requires Spend over Today above Rp 500,000 AND Purchase ROAS over Last 7 days below 1.5 fires only when both are true. Group operators apply at one level, so a rule expresses one AND group or one OR group rather than a nested tree.

Can a condition compare two metrics instead of a number?

Yes. A condition can be set to compare against another metric rather than a fixed value, and the compared metric carries its own reporting period. That allows a rule to test Spend over Today against a revenue figure over Last 7 days, or against a custom metric resolved from a Google Sheet.

Glossary

The terms an advertiser usually reads in the same sitting.

Automated rule
An automated rule is a saved instruction that checks advertising metrics on a schedule and performs an action when its conditions are true, such as pausing a campaign or raising a budget, without a person present.
Lookback period
A lookback period is the range of past days a reported metric is calculated over, such as the last 7 days or the current month; it decides which data forms the number, not which conversions are credited to the ad.
Action frequency
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.
All glossary terms

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