# Condition operator

> 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.

Source: https://adops.id/glossary/condition-operator/
Last updated: 2026-08-20
Publisher: AdOps (https://adops.id) — an independent product, not affiliated with Meta Platforms, Inc.

---

**Also known as:** Comparison operator, Rule operator

**In 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.

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.