Skip to main content

Segments Overview

Segments let you group subscribers based on their attributes and behavior. Use segments to send targeted notifications to specific audiences.

Why Use Segments?​

Instead of sending to everyone, segments let you:

  • Target specific user groups
  • Increase relevance and engagement
  • Reduce unsubscribes
  • Personalize messaging

Example segments:

  • "Mobile users in the US"
  • "Users who clicked in the last 7 days"
  • "Premium plan subscribers"

Accessing Segments​

  1. Navigate to your app
  2. Click Segments in the app menu

Segment List​

View all your segments as cards showing:

  • Segment name
  • Description (if provided)
  • Number of matching subscribers
  • Last calculated timestamp

The Segments dashboard showing existing audience segments

Actions​

ActionDescription
CreateAdd a new segment
EditModify segment rules
RecalculateUpdate subscriber count
DeleteRemove the segment

Segment Templates​

For common targeting needs, you can skip manual rule-building entirely. Templates create the segment with one click — you can rename it or adjust the rules afterward before saving.

Ready-made segment templates available above your custom segments list

TemplateRule(s)
Highly EngagedClicked 3+ notifications and seen in the last 14 days (2 rules)
New SubscribersSubscribed in the last 7 days (1 rule)
At RiskSubscribed 30+ days and never clicked a notification (2 rules)
DormantLast seen more than 60 days ago (1 rule)
Mobile OnlySubscribers on mobile devices (1 rule)
Desktop OnlySubscribers on desktop devices (1 rule)
Tablet OnlySubscribers on tablet devices (1 rule)
Recently ClickedClicked a notification in the last 7 days (1 rule)

To use one, click Use Template on the card. The segment is created immediately and appears in Your Segments below — open it any time to rename it or refine the rules.

Creating a Segment​

1. Basic Information​

FieldDescriptionRequired
NameDescriptive segment nameYes
DescriptionExplanation of the segment (max 1000 characters)No

2. Match Type​

Choose how rules are combined:

TypeLogicDescription
AllANDSubscriber must match ALL rules
AnyORSubscriber must match ANY rule

Defining the segment name and match logic in OCM Pulse

Example with "All":

  • Rule 1: Country = US
  • Rule 2: Device = Mobile
  • Result: Only US mobile users

Example with "Any":

  • Rule 1: Country = US
  • Rule 2: Country = UK
  • Result: US OR UK users

3. Rules​

Add one or more rules to define your segment. Each rule consists of:

ComponentDescription
FieldWhat attribute to check
OperatorHow to compare
ValueWhat to compare against

Constructing targeting rules in the OCM Pulse Segment builder

Available Fields​

Device & Browser​

FieldDescriptionExample Operators
Device TypeDesktop, Mobile, or Tabletequals, not equals
BrowserBrowser name (Chrome, Firefox, Safari, Edge, Opera)equals, in, not in

Location​

FieldDescriptionExample Operators
CountryTwo-letter country codeequals, in, not in

Engagement​

FieldDescriptionExample Operators
Last SeenMost recent activity (uses relative dates like "-7 days", "-1 month", "now" with the "between" operator)greater than, less than, between
Last ClickedMost recent notification click (uses relative dates like "-7 days", "-1 month", "now" with the "between" operator)greater than, less than, between
Subscribed AtWhen the subscriber first subscribed (uses relative dates like "-7 days", "-1 month", "now" with the "between" operator)greater than, less than, between
Notifications SentTotal receivedgreater than, less than
Notifications ClickedTotal notifications clickedgreater than, less than
Click RateEngagement percentagegreater than, less than

Custom Tags​

FieldDescriptionExample Operators
TagCustom tag valuehas, has not, has value

Operators​

Comparison Operators​

OperatorSymbolDescription
Equals=Exact match
Not Equals≠Does not match
Greater Than>Value is more than
Less Than<Value is less than
Greater or Equal≥Value is at least
Less or Equal≤Value is at most
Between↔Value is within range

Collection Operators​

OperatorDescription
InValue is one of the listed options
Not InValue is not in the list
ContainsText contains substring

Tag Operators​

OperatorDescription
HasTag key exists
Has NotTag key doesn't exist
Has ValueTag has specific value

Live Preview​

As you build your segment:

  1. Rules are validated in real-time
  2. Matching subscriber count updates
  3. Preview shows estimated audience size

Real-time audience size preview in the OCM Pulse segment builder

This helps you refine rules before saving.

Example Segments​

Engaged Mobile Users​

Match: All
Rules:
- Device Type equals Mobile
- Click Rate greater than 3%

International Audience​

Match: Any
Rules:
- Country equals UK
- Country equals DE
- Country equals FR

Premium Subscribers​

Match: All
Rules:
- Tag "plan" has value "premium"

Subscribers with a Known Lotame / OID Identifier​

Match: Any
Rules:
- Tag "lotame_id" has
- Tag "oid_cookie" has

If your app has the Lotame and/or Reaper integrations enabled, these tags are written automatically to subscriptions by the SDK. See External Identifiers on Subscriptions.

Dormant Users​

Match: All
Rules:
- Last Seen less than 30 days ago
- Notifications Sent greater than 5
- Click Rate less than 1%

New Desktop Users​

Match: All
Rules:
- Device Type equals Desktop
- Notifications Sent less than 3

Using Segments​

In Manual Triggers​

When creating a notification, select a segment to target only matching subscribers.

In RSS Triggers​

Configure RSS triggers to automatically send to a segment.

In A/B Tests​

Run tests against specific segments for focused optimization.

Managing Segments​

Editing a Segment​

  1. Click the segment card
  2. Modify name, description, or rules
  3. Save changes
  4. Audience count recalculates automatically

Recalculating Counts​

Segment counts are cached for performance. To get the current count:

  1. Click Recalculate on the segment card
  2. Wait for the count to update

Deleting a Segment​

  1. Click the delete button on the segment card
  2. Confirm deletion
warning

Deleting a segment doesn't affect:

  • Existing deliveries that used this segment
  • Triggers that reference this segment (they'll target all subscribers instead)

Best Practices​

Keep Segments Focused​

  • One clear purpose per segment
  • Avoid overly complex rules
  • Document with descriptions

Name Clearly​

Good: "US Mobile Users - High Engagement" Bad: "Segment 1"

Test Before Using​

  • Check the audience count
  • Send test notifications to yourself first
  • Monitor performance

Review Regularly​

  • Audience sizes change over time
  • Remove unused segments
  • Update rules as needed

Combine with Categories​

Use segments with delivery categories for powerful targeting:

  • Segment: "Sports fans"
  • Category: "Breaking news"

Segment Limits​

LimitValue
Rules per segmentMaximum 10
Segments per appUnlimited

Next Steps​