Segments

A segment is a reusable definition of a user group based on attribute conditions. Instead of repeating the same targeting rules across multiple flows, define a segment once and reference it wherever you need it.

What segments are

A segment answers the question: "Which users match these conditions?" For example:

Power users -- loginCount greater than 50 AND isPremium equals true
New free users -- plan equals "free" AND signupDate is within the last 7 days
Enterprise accounts -- plan equals "enterprise"

Segments evaluate dynamically. A user who did not match yesterday might match today if their attributes change.

Segments are scoped to an app. You create them for a specific app and they are only available in flows belonging to that app.

Creating a segment

Go to Audience in the sidebar.
Make sure the Segments view is selected.
Click Create Segment.
Give the segment a descriptive name.
Add one or more conditions.

The condition builder

Segment conditions are combined with AND logic -- a user must match every condition in the segment to be included. Segments do not support OR logic or nested groups internally. To express OR logic, create multiple segments and combine them at the flow trigger level, which does support AND/OR grouping.

Each condition consists of three parts:

Attribute -- the user attribute key to evaluate.
Operator -- how to compare the attribute value.
Value -- the target value to compare against.

Available operators

Operator	Description
`equals`	Exact match.
`notEquals`	Does not match.
`contains`	Value contains the substring.
`notContains`	Value does not contain the substring.
`startsWith`	Value starts with the substring.
`endsWith`	Value ends with the substring.
`greaterThan`	Value is greater than the target.
`lessThan`	Value is less than the target.
`greaterThanOrEqual`	Value is greater than or equal to the target.
`lessThanOrEqual`	Value is less than or equal to the target.

Using segments in flow triggers

When configuring a flow's trigger conditions, you can reference a segment instead of building conditions from scratch:

Open your flow in the editor.
Open the trigger editor (via the Publish modal -- see Flow Triggers).
Add a segment reference as a trigger item.
Choose the segment you want to target.

The flow will only display to users who match the segment at evaluation time. You can combine segment references with other trigger conditions and use AND/OR grouping at the flow trigger level.

Editing segments

To edit a segment:

Go to Audience in the sidebar.
Open the Segments view.
Click the segment you want to edit.
Modify the conditions and save.

Editing a segment affects every flow that references it. Review which flows use a segment before making changes.

Deleting segments

You can delete a segment from the segment list. Review which flows reference the segment before deleting it so no flow ends up with a broken targeting rule.

Best practices

Name segments descriptively. "Premium users on iOS" is more useful than "Segment 1."
Keep segments focused. A segment with 10 conditions is hard to reason about. Break complex targeting into multiple simpler segments and combine them at the flow trigger level when needed.
Audit segment usage. Periodically check which flows reference each segment to avoid stale definitions that no longer match any active flow.

Segments

On this page