Segments in Push: groups of web push subscribers
Building a segment of web push subscribers from their attributes, properties and events, reading its count, and how Push segments differ from CDP segments.
A segment in Push is a group of one app's web push subscribers, for sending a campaign to some of them. They are in Push → Push → Segments.
Push segments and CDP segments
| Segments in Push | Segments in CDP | |
|---|---|---|
| Who | One app's web push subscribers | Every visitor and customer of your site |
| Based on | The subscriber's attributes, browser, country and the events sent to Push | Everything CDP knows: pages, purchases, profile, consent |
| Used for | Web push campaigns | Automation flows and recipes, Agents |
For audiences built from site behaviour — looked at a product, bought twice — use CDP and a flow in Automation: Create a segment.
Build a segment
- Click Create Segment, choose the App and give it a Name.
- Under Segment Rules, choose Match — AND (all conditions) or OR (any of them).
- + Add Condition, one of three kinds:
- Attribute — your own Key with an operator (=, !=, >, >=, <, <=, contains, starts with, ends with, exists) and a value;
- Property — Platform, Browser, OS, Timezone, Country, State or External ID with =, !=, in, not in or contains;
- Event — an Event name, how many times (=, >=, >, <=, <) in last N days.
- Click Create Segment.
Event conditions count the events sent to Push itself by the Push SDK or the API — not the events CDP collects with the Monfri script.
The count
The list shows each segment's Cached Count and when it was counted (Last Updated). Use the segment in a campaign: Web push campaigns.
If something doesn't work
The segment counts nobody
Check the values against a real subscriber's page: country codes, browser names and attribute keys must match exactly. An Event condition finds nobody when your site sends its events to CDP only.
No segments yet
The list is empty until you create one. All Subscribers in a campaign needs no segment.