Segments
Choose who receives a Notification with built-in and custom Segments.
A Segment is a saved rule that picks which Contacts receive a Notification, for example "Premium users in India". You choose a Segment as the Audience in the composer, and your server can use the same Segments through the API.
Admins and Operators can both create and edit Segments.
Built-in Segments
Every Project comes with these. You can't edit or archive them.
| Segment | Who's in it |
|---|---|
| Everyone | Every Contact who can receive push: at least one active device and not opted out. |
| New contacts | Contacts in Everyone first seen in the last 7 days. Imported Contacts keep their original first-seen date. |
| Recently active | Contacts with an active device seen in the last 7 days. |
| Engaged | Recently active Contacts with 3 or more app sessions. |
| Dormant | Contacts that still have active devices, but none seen in the last 7 days. |
| Android contacts | Contacts with an active Android device. The Notification also goes only to their Android devices. |
| iOS contacts | Contacts with an active iOS device. The Notification also goes only to their iOS devices. |
Create a Segment
- Open Segments and click Create segment.
- Enter a Segment name, for example "Premium learners".
- Under Rules, choose Match:
- All rules: a Contact must match every rule.
- Any rule: a Contact must match at least one.
- Add one or more rules. Each rule has a Field, an Operator, and a Value.
- Save. The Segments list shows how many Contacts match.
Rule fields
| Field | Matches on | Example |
|---|---|---|
| Contact attribute | Data your server sends with the Contact. Pick the Attribute key. Only keys your server has already sent appear. | plan is premium |
| Locale | The Contact's language and region, as reported by the SDK. | en-IN |
| Timezone | The Contact's timezone. | Asia/Kolkata |
| Last active | Whether the Contact was active within, or not within, the last N days. | within the last 30 days |
| Endpoint platform | Contacts with an active Android and/or iOS device. | Android only |
| Has Active Endpoint | True: at least one active device. False: none. | True |
| Communication preference | Whether a category is turned on or off for the Contact. | promotions enabled |
Match: All rules is not Everyone
All rules only describes how your rules combine. It doesn't mean "all Contacts". To send to everyone who can receive push, choose the built-in Everyone Segment instead of making a Segment with no useful rules.
Edit, archive, and restore
- Edit a custom Segment at any time. Notifications that were already scheduled keep the rules the Segment had when you scheduled them. The Segment's page warns you how many scheduled Notifications use it.
- Archive a Segment to hide it from the composer. Scheduled Notifications that use it still go out.
- Restore an archived Segment to use it again. Find archived Segments with the Status filter.
Open a Segment to see how many Contacts match, its rules, and the Notifications sent to it.
Segments created through the API can use rules the Dashboard editor can't show. Those Segments say These rules are read-only here — edit with the API.
Who actually receives it
ComRaid works out which Contacts match a Segment when the Notification is sent, not when you create it. A Contact who joins the Segment after you schedule a Notification still gets it. Contacts who opted out, or turned off the Notification's category, are skipped.
From the API
Create Segments, use them in sends, and see every rule field and operator in the Segments guide.