Segment membership conditions
Target visitors who belong to a segment or chose a multiple-choice answer. You'll find how selections, empty groups, and decisions that are still loading affect a match.
You can show the same offer to several audiences or limit it to one, using the segments a visitor currently belongs to.
What it checks
Under Segments / Questions, choose a segment group or a multiple-choice question. The group's segments, or the question's answer segments, become the values you can select.
This condition checks current membership. It doesn't compare the raw answer again. Membership doesn't always mean someone clicked that answer, either. Automatic rules and synced data can establish it too.
When to use it
Use membership conditions when you've already grouped visitors and want to use those groups in another rule.
For typed answers, such as a number or email address, use input-question answer conditions. For activity during the current page view, use Question Engagement.
Options
A new membership condition starts with include any of and no selected values.
| Choose | Select | When it matches |
|---|---|---|
| include any of | One or more segments or answer segments | The visitor belongs to at least one selected value. |
| don't include any of | One or more segments or answer segments | The visitor belongs to none of the selected values. |
| matches any | No selection required | The visitor has at least one membership in the chosen group. |
| doesn't match any | No selection required | The visitor has no membership in the chosen group. |
Multiple selections are alternatives. include any of with Solo and Team means Solo or Team. To require both, use separate conditions in an All group. The underlying segment group must allow multiple matches.
matches any checks only the chosen group, not every group in the project. It isn't a general check for a known visitor.
The two presence operators, matches any and doesn't match any, hide the selection field. They check the visitor's entire membership list for that group, so you don't need to select a segment.
Examples
WorkForge (opens in a new tab) could use a Business Type group with Agency and Consultancy segments.
- include any of with both segments shows the same offer to either audience.
- don't include any of with
Agencyalso includes visitors with no Business Type membership, unless another condition requires membership.
Things to know
Empty selections and missing groups
An empty membership list, an empty selection, and a missing group behave differently.
| State | include any of | don't include any of | matches any | doesn't match any |
|---|---|---|---|---|
| The group exists, but the visitor has no memberships | False | True | False | True |
| The group exists, but you've selected no comparison values | False | True | Checks actual membership | Checks actual membership |
| The group is missing or unavailable | False | False | False | False |
A deleted group doesn't count as a valid group with an empty membership list. An old condition that still points to it won't match, even with a negative operator.
Which memberships count
RightMessage gives priority to a debugger override, then an explicit answer, then automatic rules.
For a group that allows one winner, that priority and the configured segment order decide which membership applies. Several automatic rules can be true without the visitor belonging to every segment. The condition checks the winning membership, not every segment whose rules pass.
A group that allows multiple matches can give a visitor several memberships. include any of still needs only one of your selected values to match.
If an answer conflicts with an automatic rule, the membership condition follows the resolved answer or override. It doesn't independently prefer the lower-priority automatic rule.
Decisions that are still loading
Membership can remain unresolved while data it needs loads. For example, an automatic segment based on a CRM field can wait for the contact profile.
RightMessage considers both known memberships and memberships that are still possible. It can decide whether a condition matches when both possibilities give the same answer. If a pending membership could change that answer, the condition stays unresolved.
A negative membership comparison isn't automatically true while the group's contact data loads. An unresolved group doesn't immediately count as having no memberships, either.
Groups that depend on each other
The picker leaves out groups where needed to prevent a group from directly referencing itself. Circular dependencies between groups can still leave a decision unresolved. A cycle doesn't count as an empty membership list.
Use source data or an independent group rather than defining two groups only in terms of each other. The condition builder reference covers nested groups, negative conditions, and unresolved combinations.
How long membership lasts
This condition checks the visitor's current membership and has no separate expiration field. How long membership lasts depends on what established it.
A saved answer can remain available in the same browser. A current-page rule changes as the visitor moves between pages. A CRM-based rule follows the loaded contact profile. Clearing browser data or changing the underlying values can change membership.
Matching a segment condition doesn't write a tag to your email platform or permanently assign a contact to that segment. Those are separate sync or flow actions.