Overview
Learn how to segment your audience and target feedback campaigns in encatch
Segments let you organize users in encatch based on shared attributes or behavior. A segment is a group of users who meet criteria you define. For manual segments, it is a list you curate yourself.
The Segments page in the dashboard shows All Users (every identified user in your project) and any segments you create. Use segments to control who sees your feedback forms, compare responses by audience, and run targeted campaigns.
Segment types
encatch supports three kinds of segments:
| Type | UI label | How it works | When to use |
|---|---|---|---|
| All Users | All Users (no badge) | Contains every identified user in the project. You cannot edit, delete, rename, or change membership of this segment. | Baseline audience, browsing all users in the project |
| Data-driven | Dynamic | Users enter and leave automatically when they match (or stop matching) the conditions you set. Membership updates as encatch receives new user data, feedback activity, or tracked events. | Dynamic groups based on traits, behavior, feedback history, or survey answers |
| Manual | Manual | You add and remove users by username. The list stays fixed until you change it. | Beta testers, VIPs, one-off lists from spreadsheets or external tools |
Docs refer to Data-driven segments. In the dashboard, these appear with a Dynamic badge. When creating a segment, the option is labeled Data Driven Segment.
Data-driven vs Manual
| Data-driven | Manual | |
|---|---|---|
| Membership | Automatic based on conditions | You add and remove users manually |
| Updates | Users enter/leave when data changes | List changes only when you edit it |
| Best for | Traits, events, feedback interaction, survey answers | Hand-picked cohorts, imports from other tools |
What you can do with segments
Segments are used throughout encatch:
- Target feedback forms: Include or exclude segments when configuring Logged-in Users targeting so only matching users see a form.
- Run targeted campaigns: Show forms to specific groups (e.g. enterprise plan users, iOS users, highly engaged users).
- Analyze by audience: Filter feedback results by user segment in reports (for example, Audience Overview).
- Reduce survey fatigue: Combine segment targeting with Past Interaction rules to avoid showing forms to users who already saw or responded to other surveys.
- Reuse across forms: Build a segment once and reference it on multiple feedback forms.
Condition types (data-driven segments)
When you click Add condition, the picker shows four options:
| Condition type | What it filters on |
|---|---|
| User Traits | User properties, including system fields (e.g. device_os, email) and custom traits (e.g. plan). Account traits appear under Account Data in the trait list. |
| Tracked Events | In-app actions sent via trackEvent() (e.g. feature_used, checkout_completed) |
| Feedback Interaction | Form engagement: seen, started, completed, dismissed, and more |
| Feedback Response | What users answered on past surveys (e.g. NPS score, choice selections) |
See Data-driven segments for full details on each condition type and how to configure them.
Traits are configured in User Traits. Events are configured in Tracked Events.
Use case examples
| Use Case | Segment Type | Example |
|---|---|---|
| Beta product feedback | Manual | Add beta testers by username for a dedicated feedback campaign. |
| Highly engaged users | Data-driven | feedback_response_count greater than a threshold for loyalty surveys. |
| Device-specific rollouts | Data-driven | device_os equals iOS or Android for compatibility testing. |
| SDK upgrade campaigns | Data-driven | sdk_version starts with an older version for upgrade prompts. |
| Technical environment | Data-driven | device_os is set AND browser equals Chrome. |
| NPS detractor follow-up | Data-driven | Feedback Response: NPS is 0-6 on a previous survey. |
| Non-responders | Data-driven | Feedback Interaction: form was Seen but not Completed in the last 30 days. |
| Feature power users | Data-driven | Tracked Event: feature_used occurred at least 10 times in the last 7 days. |
| Custom cohorts | Manual | Provide a list of usernames for a one-off survey or special offer. |
Next Steps
- Data-driven segments: Create dynamic segments using traits, events, feedback interaction, and feedback response conditions.
- Manual segments: Build static, hand-picked lists of users by username.
- User Traits: Configure traits used in segment conditions.
- Tracked Events: Configure events used in segment conditions.
- Logged-in Users targeting: Use segments when setting up who sees your feedback forms.
Was this page helpful?