Condition types

Each condition has a type plus fields that depend on it. The examples show each condition in a segment definition's JSON form.

Shared rules

• Values. 1 to 100 per condition, each a non-empty string of up to 256 bytes.
• Operators on text. is and is_not compare exact values. contains is a case-insensitive substring match.
• Windows. See Time windows. A window is {"last_days": N} or {"from": "YYYY-MM-DD", "to": "YYYY-MM-DD"}.
• Negative conditions. Those marked "negative" below must sit in an and group with a positive condition.

Did an event

Matches people who raised an event at least count times in the window.

{ "type": "event", "event_name": "checkout",
  "filters": [{ "field": "properties.plan", "op": "is", "value": "pro" }],
  "count": 3, "window": { "last_days": 30 } }

Give exactly one of event_type, event_name or any.

Filter fields: screen_name, platform, app_version, country, city, device_model, os, os_version, language, tracking_source, tracking_medium, tracking_campaign, ads_platform, or an event property as properties.<key>. In the dashboard, click where on the condition to add one.

Message events, such as push_open and in_app_viewed, do not count toward Any activity or Any custom event, because a message shown is not something the person did. Target a message event by its name instead.

Device

Matches on a device or app field.

{ "type": "device", "field": "platform", "op": "is", "value": ["ios"], "mode": "current" }

The two modes:

• current device (current): the latest value seen in the last 30 days. No window. is_not means "has a known current value that is not this one", so it counts as positive.
• any device used (used): any event with that value in the window. is_not means "not seen with that value in the window", so people with no activity in the window also match. This is_not is negative.

On self-hosted deployments, SEGMENT_DEVICE_CURRENT_DAYS sets the 30-day lookback of current.

Profile property

Matches the current value of a profile property your app set through the SDK, not its value at the time of an event.

{ "type": "profile", "field": "properties.plan", "op": "is", "value": ["pro"] }

is_not and is_not_set are negative. A person with no profile also matches is_not.

A dotted key such as user.plan and the nested path user › plan are the same property.

First seen

Matches the date of the person's earliest built-in event.

{ "type": "first_seen", "op": "gte", "value": "2026-01-01" }

Only built-in events set first seen. A person whose only activity is custom events never matches.

Identifier

Matches the user identifier your app set through the SDK.

{ "type": "identifier", "op": "is", "value": ["member-4471"] }

in_list and not_in_list only work on a saved segment that has an uploaded list. See Identifier lists.

Acquired via

Matches people who had an install or reinstall from a link, campaign, source or medium in the window.

{ "type": "acquisition", "field": "campaign_id", "op": "is", "value": [41], "window": { "last_days": 365 } }

is_not is negative.

Purchase

Matches people with at least count purchases in the window, optionally above a spending total.

{ "type": "purchase", "product_id": ["pro_yearly"], "purchase_type": ["subscription"],
  "count": 1, "min_total_usd_cents": 999, "window": { "last_days": 90 } }

How purchases count:

• One transaction counts once, from its buy. Renewals and repeat purchases are separate transactions.
• A refunded transaction does not count, unless the refund was later reversed.
• quantity raises the spend total. It does not multiply the count.
• Totals use the purchase's US dollar value.

Saving a segment with a purchase condition fails while revenue tracking is off.

Limits

Self-hosted deployments can change the window caps with environment variables. The other limits are fixed.