Segments

What it does and when to use it

A segment is a group of contacts described by conditions (“bought twice or more, nothing in the last 60 days”), not a fixed list. Whoever matches the conditions is in it, today and from now on: it keeps itself up to date. Use segments to choose who receives a campaign, who may enter a flow, and who must be left out.

How it works

A segment is a set of conditions, joined by all conditions (everyone who matches every one) or any condition (everyone who matches at least one), up to 20 conditions.

Each condition is a field, a condition on it and a value. Fields are what you know about a contact:

Group	Fields
Details	Email, First name, Last name, Phone, City, Country, Language, Added on
Consent	Has email consent, the topics they receive
Tags	Tags
Orders	Has bought, Orders, Spent, Last order, Last conversion
Engagement	Last email opened, Last link clicked, Last email received
Campaign activity	Received, opened, clicked or bought from a given campaign
Your fields	Every field in Settings › Contact fields
Events	Did an event, or when they last did it

Conditions depend on the field: equals, is not, contains, does not contain, greater or less than, before or after a date, and within or not within the last N days.

Instead of building the conditions by hand you can describe who you want (“bought twice or more, but nothing in the last 60 days”) and let the AI write them; anything it cannot express with your fields is left out and you are told.

What each status means and what to do

A segment has no status of its own. What decides whether its members actually receive an email is each one’s consent: a segment can include people who may not be written to, and the sending gate leaves them out at send time, with the reason recorded. See why an email was not sent.

Events involved

Segments react to the same facts as everything else: a new order changes Orders and Spent, an open changes Last email opened, an event your product sends can be a condition. The list of events is in the events catalog.

Set it up in the dashboard

Contacts, then build the filter: add a condition, choose the field, the condition and the value. The count of matching contacts updates as you go.
Save as segment, give it a name and a description of who is in it and what it is for.
Use it:
- In a campaign: choose it as the audience; optionally leave out another segment, and people who received an email from you in the last N days.
- In a flow: an Audience step lets only the segment’s members continue.
- From a campaign’s results: save the people who opened, clicked or bought as a new segment.

Editing a segment’s conditions changes who is in it from then on. Deleting it removes only the saved filter; the contacts stay.

When a campaign starts, its recipients are fixed. The people in the segment at that moment are the ones who get the email, even if the segment changes while it is being sent; the campaign keeps the segment’s name as it was.

Do it from your code

Your product decides who is in a segment through the data it sends: fields on POST /contacts, events on POST /events. See what you can build today.

Troubleshooting

Symptom	Likely cause	Fix
The count is zero while you build it	A condition is incomplete, or the conditions are joined by all when you meant any.	Fill in every condition; check the join.
A campaign reached fewer people than the segment holds	Some members may not receive marketing (no consent, unsubscribed, a topic turned off) or were excluded.	Check the campaign’s exclusions and why an email was not sent.
Someone left the segment	They no longer match: segments update on their own.	Expected.