
Audience
People & profiles
Segments
A segment is a saved audience definition composed of attribute, event, list, and RFM conditions. Segments are evaluated on-read so membership always reflects the latest data.
Creating a segment
- Go to Segments โ + New segment.
- Give it a name and optional description.
- Add conditions. Groups of conditions can be combined with
AND/OR, and nested. - Click Preview to see the estimated count and a sample of 20 matching customers.
Condition types
| Type | Example |
|---|---|
| Attribute | plan = 'premium', wallet_balance_ngn > 10000, country IN ('NG','KE','GH') |
| Event | Performed purchase_completed at least 2 times in the last 30 days where total > 50. |
| No event | Has not performed app_opened in the last 14 days. |
| List membership | Is on list VIP but not on list Churned. |
| RFM | RFM bucket IN Champions, Loyal. |
| Consent | Consent for channel email is opted_in. |
Live preview
As you edit conditions the preview count updates automatically (400ms debounce) so you can feel your way to the right size of audience without saving.
Using segments
- As a campaign audience (one-shot or scheduled).
- As a journey entry trigger ("whenever a customer enters this segment").
- As a journey exit condition ("stop the flow when they leave this segment").
- As a filter in analytics (funnels, cohorts, revenue attribution).
Performance notes
Segments are cached for 60 seconds inside the segment preview endpoint. For very large workspaces (> 5M customers), use RFM buckets or pre-computed attributes where possible โ they index better than deeply nested event counts.