Segment conditions: the complete reference
Every kind of segment condition in CDP — traits, events, recency, pages, sums, location, device, campaign and other segments — with its operators and examples.
This page lists every condition you can add to a segment in CDP and what each option means. How to build a segment: Create a segment.
Operators for values
Traits, event properties, pages, location, device and campaign compare a value with one of these operators:
| Operator | Matches when the value… |
|---|---|
| equals / does not equal | is exactly / is not the text or number you typed. |
| contains / does not contain | includes / does not include your text anywhere. |
| starts with / ends with | begins / ends with your text. |
| greater than, greater than or equal, less than, less than or equal | compared as a number. |
| exists / does not exist | is set at all / is not set. |
| is one of / is not one of | is / is not in your list — type the values separated by commas: val1, val2. |
Timeframes
Many conditions take a Timeframe: All time, Last hour, Last 24 hours, Last 7 days, Last 30 days, Last 90 days or Last year. The window moves with time: "Last 30 days" always means the 30 days before now.
Profile conditions
| Condition | What it checks | Example |
|---|---|---|
| Trait | Something known about the person — choose it from the list or type a Custom field. | Trait language equals bg |
| Computed Trait | Something Monfri works out from the person's data. The list shows the ones your profiles have. | a computed trait greater than 3 |
| Date | First Seen or Last Seen, with before, after, on, between, within last, not within last, exists, does not exist. | Last Seen not within last 60 days — people who drifted away |
Behavior conditions
| Condition | What it checks | Example |
|---|---|---|
| Event | Did an event, how many times, in a timeframe: count equals, count greater than, count at least, count less than, count at most, count between, has occurred, has not occurred. Pick an event from the list or type a Custom event. | Order Completed count at least 2 in Last 90 days |
| Event Property | An event with a detail of it — the Property and a value. | Product Viewed where category equals Shoes |
| Recency | When the First or Last occurrence of an event was. | Last Order Completed not within last 60 days |
| Page | Visited a page — by Path, URL, Title or Referrer. | Path contains /sale/ |
| Aggregate | A Sum, Average, Minimum or Maximum of an event's number property, compared with a value. | Sum of revenue in Order Completed greater than 200 |
Context conditions
| Condition | Attributes | Example |
|---|---|---|
| Location | Country, City, Region, Timezone | Country equals BG |
| Device | Device Type, OS, Browser, Manufacturer | Device Type equals mobile |
| Campaign | Source, Medium, Campaign Name, Term, Content — the UTM tags of the visit | Source equals facebook |
Location and Device look at the person's most recent visit; the country is the two-letter code, such as BG. Campaign looks at all their visits in the timeframe and finds UTM tags in visits from 21 September 2026 on.
Segment condition
Cohort — is member of or is not member of another segment. Use it to build on a segment you already have: bought in the last 90 days and is not member of VIP.
Tips
- Event names are case sensitive:
Order Completed, notorder completed. Copy them from Audience → Events. - Prefer Event and Trait conditions; Page, Location, Device and Event Property look through each person's history and are slower on big sites.
- A segment of people who did not do something — has not occurred — includes everyone who never did it, also people who visited once a year ago. Add a Last Seen condition to keep it to active people.
If something doesn't work
A condition matches nobody
The value differs from what arrives: bg against BG, a different event name, a property that is not sent. Open Audience → Events, find a matching event and copy the exact name and value.
Campaign matches nobody
The visits came before 21 September 2026, or the links carry no UTM tags. Check a recent visit in Audience → Events — its properties show the UTM values.