Skip to main content
Greater than (numbers) or After (dates) checks whether the answer is strictly above your threshold — higher quantity, later deadline, score above a cutoff. Use it for eligibility gates, quiz routing, age checks, and “late registration” fees. Equal values do not match — use Greater than or equal on numbers when the boundary counts.

​
When to choose this

​
Exact behavior

  • Both sides must be present and valid — blank answers never match.
  • Numbers: compared as floating-point values (10 > 9.5, "10" > "9").
  • Dates and times: parsed as real timestamps when possible (strtotime); otherwise compared as strings lexicographically.
  • Strictly greater — equal values do not match.
  • If your comparison value is blank, the clause never matches (fail-closed).
  • Pick another field in Value — e.g. End date after Start date.
Date fields support After and Before only — not “greater than or equal”. To include the boundary date, pick the day before as your comparison value, or store dates as numbers.

​
Which field types

Supported number blocks include integer, stepper, currency, sliders, rating, year, duration, and calculated numeric results.

​
Blank / unanswered answers

Never matches. Use Is empty to react to skipped number or date fields. If you reference a later-page date via Value, the comparison stays false until that field is answered.

​
Configure in Studio

1

Open a rule

Logic → Rules, or Branch / Add condition — open When.
2

Pick a number or date field

Only numeric and date/time families show Greater than / After.
3

Select the operator

Choose Greater than (numbers) or After (dates).
4

Set the threshold

Enter a literal number, pick a date, or pick another field in Value for dynamic comparisons.
5

Add Then actions

Popular: Jump to page, Show blocks, Calculate.
6

Test boundary values

On Fill, try exactly at threshold (should fail) and one step above (should pass).

​
Worked examples

​
Quiz winner routing

When Score greater than 80 → Then Jump to page Winner
Score of exactly 80 does not jump — use ≥ 80 if ties should win.

​
Late registration fee

When Event date after 2026-06-01 → Then Show blocks Late fee notice
June 1 itself does not match — use May 31 as boundary or switch to a numeric “days until event” calculated field with ≥.

​
Budget exceeds minimum

When Budget greater than (pick) Minimum budget → Then show upsell options
Both fields must be filled with valid numbers.

​
Age gate (numeric)

When Age greater than 17 → Then Show blocks Adult consent
Age exactly 17 does not match — use Greater than or equal 18 for “18+”.

​
Test on fill

1

Enter a value below the threshold

Rule should stay off.
2

Enter exactly the threshold

Greater than / After should not match.
3

Enter one step above

Then actions should fire.
4

Clear the field

Rule turns off — blank never matches.
5

Test date parsing

Use realistic date formats your block emits; invalid strings may fall back to string compare.

​
Common mistakes

  • Using After when you mean “on or after” — adjust the date or use a number field with ≥.
  • Comparing text fields — use Starts with or Contains instead.
  • Reading a field on a page the respondent has not reached — stays false until answered.
  • Mixing date formats — keep Studio defaults consistent across compared fields.

​
Troubleshooting

After excludes equality. Pick the previous calendar day or use a calculated numeric offset.
Referenced field may still be blank or non-numeric. Fill both fields in order on Fill.
Both sides must be numeric for float compare. Non-numeric strings use lexicographic order — usually not what you want for quantities.
Field may be text or choice family — Greater than is numbers and dates only.
Last modified on September 7, 2026