Skip to main content
Greater than or equal checks whether a numeric answer is at or above your threshold — including an exact match at the boundary. Use it for “18+”, minimum order quantities, passing scores (≥ 70), and tier unlocks. Number fields only — date fields do not offer this operator in Studio.

When to choose this


Exact behavior

  • Numbers only — integer, stepper, currency, sliders, rating, year, duration, calculated numbers.
  • Both sides must be present and valid — blank answers never match.
  • Compared as floating-point (>=).
  • String numerics like "18" compare correctly against 18.
  • Blank comparison value → clause never matches (fail-closed).
  • Pick another field in Value for dynamic floors (e.g. Spend ≥ Minimum).

Which field types


Blank / unanswered answers

Never matches. Pair with Is empty if skipped fields need their own branch.

Configure in Studio

1

Open a rule

Logic → Rules, or Branch / Add condition on a field.
2

Select a number field

Pick integer, currency, rating, calculated total, etc.
3

Choose Greater than or equal

Appears only for number family fields.
4

Enter the minimum threshold

Literal (e.g. 18, 100.00) or pick another numeric field in Value.
5

Add Then actions

e.g. Show blocks, Jump to page, Hide submit for ineligible users.
6

Test boundary on Fill

Values at, below, and above threshold.

Worked examples

Age 18+ gate

When Age greater than or equal 18 → Then Show blocks Adult section
Age 18 matches; age 17 does not.

Minimum order quantity

When Quantity greater than or equal 10 → Then Show blocks Bulk discount applied
Exactly 10 units qualifies.

Passing quiz score

When Score greater than or equal 70 → Then Jump to page Pass certificate
Use ≥ so a score of exactly 70 passes.

Spend meets minimum

When Cart total greater than or equal (pick) Free shipping minimum → Then show free shipping banner
Both totals must be entered and numeric.

Test on fill

1

Enter one below threshold

Rule off.
2

Enter exactly at threshold

Rule on — this is the key difference from Greater than.
3

Enter well above threshold

Rule stays on.
4

Clear the field

Rule off immediately.

Common mistakes

  • Looking for ≥ on date fields — not available; use After or a calculated day count.
  • Using Greater than when boundary should qualify — switch to ≥.
  • Comparing non-numeric text — operator unavailable by design.

Troubleshooting

Field is not in the number family. Convert to integer/currency or use a calculated numeric field.
Float compare should treat them equal — if not, check for hidden characters in text masquerading as numbers.
Dynamic minimum unset → comparison value blank → fail-closed until filled.
Use After with (boundary − 1 day) or store epoch/day-count in a number field with ≥.
Last modified on September 7, 2026