Unified customer profile

Advanced segmentation for precise, reusable audiences

Combine tags, events, and platform data with nested AND, OR, and exclude logic. Save it once as a named segment, then target it from any channel, Condition split, or Journey.

Control Panel segment builder showing nested condition groups joined with AND and OR operators

The audience is rarely one fact

“High spender” is a useful tag, on its own, until the audience you actually need is high spenders who haven’t opened the app in two weeks and have an email on file. That’s three facts, and the segment only works if it can hold all three at once.

Building that logic by hand for every send is how targeting quietly narrows down to “anyone who ever bought something.” Advanced segmentation is what lets you combine what you know once, name it, and point any channel or journey at it.

What it does

A segment is a tree of conditions, tags, events, geo, platform, even other segments, joined with AND, OR, or exclude. Any branch can nest inside another, so the logic isn’t a flat list: it’s “(A and B) or (C and not D)” as deep as the audience needs. A saved segment can sit as a condition inside another one, so segmentation logic built once gets reused instead of rebuilt.

ModeHow size is calculatedUpdate
StandardCached estimateManual, via Refresh Segment Size
High-Speed Delivery (opt-in)Precompiled membership listEvery 10 minutes
Mode
1 / 2
Standard
How size is calculated
Cached estimate
Update
Manual, via Refresh Segment Size
Mode
2 / 2
High-Speed Delivery (opt-in)
How size is calculated
Precompiled membership list
Update
Every 10 minutes

“Hasn’t done X in 14 days” works the same way as “has done X”: it’s an event count condition, just set to zero. And because segments can reference each other, combining an iOS segment with an Android one, or layering a behavioral exclusion on top of an existing win-back segment, takes one condition instead of rebuilding the whole tree.

Segments can reference other segments

A saved segment dropped into another one as a condition means a platform split, a behavioral exclusion, or an RFM tier gets defined once, in one place, and every segment that references it stays in sync.

What ties it back to a unified customer profile

Tags and events only earn their keep once something can combine them into a decision. Advanced segmentation is the layer that turns “spent over $50,” “hasn’t opened the app in two weeks,” and “has an email on file” into one addressable audience instead of three separate facts sitting on a unified customer profile with nobody acting on the combination.

How it works

  1. Open Segments and add conditions

    In Audience → Segments, build conditions from tags, events, geo, platform, or other saved segments.

  2. Combine them

    Join conditions with AND, OR, or exclude, nesting groups as deep as the audience needs.

  3. Save and reuse it

    Point any channel, a Condition split branch, or a Journey's entry condition at the saved segment.

All three steps are no-code, in the Control Panel. What you can build depends on the tags and events already recorded, so those need to exist first.

Built to sit next to tags and events

A segment rarely stands alone. Tags hold what’s true about someone now, events hold what they just did, and a segment is where both get combined: an RFM tier built from three tags, ANDed with an event condition for recent inactivity, feeding straight into a Condition split branch or a Journey’s entry condition. RFM segmentation is the scoring layer that most often supplies the tags a segment like this ANDs together.

Built to feed the rest of the platform

Tags and events supply the facts. A segment combines them into one audience. Condition split and Journey entry read that segment to decide who gets in.

How to tell it is working

Each segment shows an estimated size you refresh on demand. Before you delete one, the product checks which campaigns and Journeys currently reference it and warns you, so cleaning up an old segment doesn’t quietly pause something live.

What to keep in mind

A few things worth checking before you build on a segment.

  • No published cap on condition count or nesting depth. Deep trees work in practice, but there’s no documented guarantee.
  • Segment size is an on-demand estimate, not a live counter while you build. Refresh manually to see the current number.
  • High-Speed Delivery is a separate, opt-in mode with a 10-minute refresh interval, not the default for every segment.
  • Deleting a segment used elsewhere pauses the campaigns and Journeys that reference it.

Turn what you know into exactly who you reach

Tags and events are facts. A segment is what turns several of them into the exact audience you meant.