When to choose this
Older forms may label this operator Is not — behavior is identical to Not equals.
Exact behavior
- Requires a non-blank answer on the source field — null,
"", and[]never match (fail-closed, same as Equals). - Uses the same flexible matching as Equals: string normalization, yes/no aliases, multi-select set comparison.
- If your comparison value is blank or missing, the clause never matches.
- Multi-select: matches when the selected set is not exactly the expected set (order ignored).
Which field types
Blank / unanswered answers
Never matches. This surprises many builders: Not equals Free does not fire when the Plan field is blank — the engine treats unanswered fields as “no comparison yet”, not “anything except Free”. Always pair exclusion logic with a separate Is empty rule if you need a third path for skipped fields.Configure in Studio
1
Open a rule
Open Logic → Rules, or Branch / Add condition on a field — expand When.
2
Pick the source field
Select the field to test (e.g. Plan, Country).
3
Choose Not equals
Select Not equals (or Is not) from the operator list.
4
Enter the excluded value
Type or pick the one value that should not trigger this branch.
5
Add Then actions
Common pairings: Hide blocks for irrelevant sections, Jump to page for alternate flows.
6
Preview on Fill
Test with the excluded value, a different value, and a blank field.
Worked examples
Hide enterprise-only section
When Plan is notFires for Starter and Pro — but not when Plan is still blank on first load.Enterprise→ Then Hide blocksSSO details, Audit log
International shipping path
When Country is notCombine with When Country is empty → Hide international shipping if you want three distinct paths.US→ Then Show blocksInternational shipping
“Other” follow-up cleanup
When Industry is notHides the free-text follow-up whenever they pick a preset industry.Other→ Then Hide blocksPlease specify industry
Toggle off path
When “Subscribe to newsletter” is notYes/no fields work well with Not equals for the unchecked state.Yes→ Then Make optionalEmail preferences
Test on fill
1
Pick the excluded value
Select exactly the value in your rule — Then should not run.
2
Pick any other valid value
Then should activate.
3
Leave the field blank
Confirm Then does not run — add Is empty if you need blank handling.
4
Change answers back and forth
Visibility and requirements should update live without stale state.
Common mistakes
- Expecting Not equals X to mean “empty or anything but X” — blank never matches; add Is empty.
- Using Not equals for a list of forbidden values — use Is none of with multiple chips.
- Hiding a follow-up with Not equals Other but forgetting to Show it when they do pick Other (use paired rules in Rules or Branch).
- Comparing against the wrong option value (label vs stored value).
Troubleshooting
Rule never fires on blank — I wanted it to
Rule never fires on blank — I wanted it to
By design. Add When field is empty → Then … as a sibling rule or use Any match mode across two clauses.
Rule fires on blank in Fill
Rule fires on blank in Fill
Unlikely with Not equals — check you did not mean Is not empty or another operator. Inspect whether a default value pre-fills the field.
Multi-select not behaving
Multi-select not behaving
Not equals compares full sets. For “does not include option X”, use Does not contain on choice fields.
Two rules fight (Show vs Hide)
Two rules fight (Show vs Hide)
Last matching rule wins. Reorder Logic Board rules or narrow When clauses so only one applies per answer state.