Between (inclusive)
Between (inclusive) passes when a numeric field sits within the range you type, with both end points counted as inside. It replaces a pair of Greater than and Less than rules joined with all.
When to use it
Use it wherever a number decides what happens next: order totals that qualify for a rewards list, lead scores in a mid-tier band, quantities that trigger a wholesale workflow, ages that fall inside an eligibility window.
How to configure it
- Open AFI → Integrations and edit your integration.
- Switch on Conditional Logic.
- Pick the numeric field, choose Between (inclusive), and type the range as two numbers separated by a comma.
A value of 100,500 matches every amount from 100 through 500.
How it behaves
The range accepts a comma or a pipe as the separator, so 100,500 and 100|500 are the same. Spaces around either number are ignored.
Order does not matter. 500,100 is normalised to the same range as 100,500, so a reversed entry still works instead of silently matching nothing.
Both ends are included. With 100,500, a submission of exactly 100 or exactly 500 passes.
Everything must be numeric. If the field value is not a number, or either end of the range is not a number, or you supply only one number, the rule fails and the integration does not run. That is deliberate: a malformed range should not let submissions through unchecked.
Quick reference
| Range | Field value | Result |
|---|---|---|
100,500 |
100 |
Match |
100,500 |
499.99 |
Match |
100,500 |
500.01 |
No match |
500,100 |
250 |
Match |
100,500 |
abc |
No match |
100 |
250 |
No match |
Example
A WooCommerce store adds customers to a “mid-value” segment when an order lands between £100 and £500.
Set the rule to {{order_total}} Between (inclusive) 100,500. Smaller orders and high-value orders are handled by separate integrations with their own ranges.
Notes
Currency symbols and thousands separators are not stripped, so a field that arrives as £1,250.00 will not read as a number. Map the raw numeric field where your form offers one.