Segments

A segment is a saved filter expression that identifies a set of actors based on event behavior — for example, “users who triggered report_exported at least 5 times in the last 30 days but never dashboard_shared.” Save a segment, rerun whenever you want a current count and actor list.

Prerequisites

• Plan: Segments are available on Trial, Pro, Business, and Enterprise. Starter accounts see an upgrade prompt instead of the Segments page.
• Permissions: view_segments to see and evaluate segments; manage_segments additionally to create, edit, duplicate, or delete.

Create a segment

In the sidebar, click Segments, then New Segment in the top-right.

Fill in:

Then build the filter — at least one group with at least one condition. Within a group, conditions combine via the group’s logic setting (AND or OR). Multiple groups are always intersected — an actor must satisfy every group. Maximum 10 conditions total.

Condition types

• Did event — actor performed a specific event a given number of times (at least, at most, or exactly N).
• Did NOT do event — actor did not perform the event the threshold number of times.
• Last event before — actor’s most recent occurrence of the event is before a date.
• Last event after — actor’s most recent occurrence is after a date.
• Actor identified — actor has been linked from anonymous to a real ID via Identify at any point.
• Actor anonymous — actor has only ever been seen anonymous (never identified).

Each event-based condition can carry its own time range that overrides the outer range. Options:

• All time — no time bound.
• Relative preset — Last 7 / 30 / 90 / 180 / 365 days, Last quarter, This quarter, Last month, Last year.
• Relative range — custom relative window.
• Absolute — specific start and end dates.

Click Create segment to save. You’re navigated to the segment’s detail page.

Evaluate a segment

The detail page shows the saved definition plus a results panel. Click Evaluate to compute the current actor list against live event data. Optional Source App filter narrows the run to one product (defaults to the segment’s saved default product if set).

Results render as a paginated table (50 actors per page) with: actor_id, first seen, last seen, total events, and per-condition event counts (one column per event_performed / event_not_performed condition in the segment). Click Load more to fetch the next page.

Computation is live — events ingested moments ago count immediately. A 30-second timeout applies; if a segment is too broad to evaluate inside the budget, the API returns a 504 and the UI surfaces the message. Tighten the time range, drop a condition, or filter to a single source app.

Templates

The create page includes a small set of starter templates — common shapes like “Active users (last 30 days)” or “Churned users (no activity in 60 days)” — that pre-fill the form. Use them as a base and adjust.

Edit, duplicate, delete

From a segment’s detail page (requires manage_segments):

• Edit — change the filter, name, or description. Your changes save together; re-evaluating uses the new definition.
• Duplicate — copies the segment with a new name. Useful when you want a small variation.
• Delete — permanently removes the segment. The actor data isn’t deleted — only the saved definition.

Common questions

My segment returns zero actors. Check that the events you reference (by name and optional category) actually exist in your data — use Event Explorer to confirm. Also verify the time range — a tight window plus a high threshold can drop the count to zero on smaller products.

Group logic is confusing. Multiple groups always intersect — actors must satisfy every group. The and / or setting on each group only controls how that group’s own conditions combine. For a union, use a single group with or logic.

Can I use a segment as a funnel filter? Not today. Funnels and segments are independent; segment IDs are not accepted as a funnel filter. A future feature may bridge them.

Can I export the actor list? Not from the Segments page UI today. The list is available via the POST /v1/segments/{id}/evaluate API; iterate over the paginated cursor to fetch all actors.

Next

→ Anomalies