Appearance
Targeting and segments
Targeting decides who sees a tour, announcement or survey. The backend applies it before content reaches the browser, so hidden content is never sent.
Modes
| Mode | Tours | Announcements |
|---|---|---|
| Everyone | Yes | Yes |
| Page (URL rules) | Yes | No |
| Lifecycle (new or returning) | Yes | No |
| Attribute | Yes | No |
| Segment | Yes | Yes |
Page rules are checked in the browser, because the backend does not know the current page.
Where the data comes from
An anonymous visitor who never calls these still matches Everyone, Page and Lifecycle rules. Attribute and segment rules need trait data. An account-level segment never matches a visitor who has not called group().
Create a segment
- Open Segments in the dashboard.
- Define conditions on the traits you send with
identifyandgroup. - Use the segment in a tour, announcement or survey.
Keep traits fresh
Traits merge, so call identify and group on every page load. If you need targeted content to show right after a trait changes, await identify(...) and then call init() again.