Combine user attributes, segments, event history, page URLs, and experience state with AND or OR audience rules.
Combine conditions when an in-app experience should appear only for users who match a particular audience and context. The targeting builder supports user attributes, saved segments, event history, the current page, and experience state.
Survey targeting builder with its five condition sources in the Atlas demo workspace.
Open the condition builder
For a survey, open its targeting settings and choose Specific users. Add conditions in the builder below the audience choices.
Product tours and checklists use the same condition builder in their targeting settings. Announcements expose it under Advanced in-app eligibility. Announcement in-app rules are not copied to email delivery.
Choose a condition source
| Source | Use it to check |
|---|---|
| User attribute | A profile value, such as a plan or role, using the comparisons available for its type. |
| Saved segment | Whether the user is in or outside an existing saved segment. |
| Event history | Whether an event occurred, how often it occurred, or when it occurred. |
| Current page | The page URL when the experience is evaluated. |
| Experience state | Whether another experience was shown, completed, or dismissed. |
Select the source, choose the property, event, segment, or experience, and complete the comparison and value fields. Each source has its own operators.
Combine conditions with AND or OR
Choose All (AND) when every condition in a group must match. Choose Any (OR) when any one condition can match.
Use Filter to add a rule. Use Group when part of the audience needs its own AND or OR logic.
For example, a survey for administrators on either of two plans could use:
- An outer All (AND) group.
- A user-attribute condition for the administrator role.
- A nested Any (OR) group containing one condition for each plan.
The property names and values in this example must match the data your application sends.
Keep eligibility separate from launch timing
Conditions determine who qualifies. Launch events, delay, frequency, schedule, and publication still determine whether and when the experience can appear.
An Event history condition evaluates past behavior. It does not make the experience launch immediately when that event occurs. Configure an immediate launch event separately when that is the intended behavior.
Test the audience
- Save a complete set of conditions.
- Test with a user who should match.
- Test with a user who should not match.
- For page conditions, test both a matching and a non-matching URL.
- For event or experience history, use accounts with known histories.
- Preview the experience and verify its launch settings before publishing.
Resolve empty groups, missing values, and deleted references reported by the editor. Advanced conditions require a compatible current Userorbit SDK. If the editor reports an SDK compatibility warning, update the installed SDK before relying on those conditions.