Segments

Define audience groups to target experiences and gate features

Segments are named audience filters. Define conditions based on user properties, events, or other segments, then use them to target experiences, run experiments on specific audiences, and gate features.

What is a segment?

A segment is a saved set of conditions that evaluates to true or false for each user. For example, “Free Users” might match users whose subscription_status equals free. “Power Users” might match users who triggered feature_used more than 10 times in the last 30 days.

Segments are scoped to an app and environment (test or live). You create and manage them from the dashboard. Nuxie evaluates them on the server and delivers only the membership facts needed by an armed Journey.

Where segments are used

Segments appear throughout Nuxie:

Experience triggers – Show a paywall only to users in the “Free Users” segment. See Triggers & Goals.
Experiment scoping – Run an A/B test only for users in a target audience. See Experiments.
Feature gating – Restrict access to features based on segment membership. See Features & Entitlements.
Analytics filtering – Break down metrics by audience group. See Dashboard & Metrics.

How evaluation works

Nuxie evaluates segment definitions on the server against the customer’s properties, event history, feature access, and referenced segment memberships. A segment-entry trigger starts server Journey work there. When later Journey work runs on a device, the profile contains only the opaque membership booleans that its signed releases require.

The SDK never downloads segment definitions and never changes membership from local events or property updates. It synchronizes the current membership facts at app launch and foreground, then uses them only as state gates for already armed Journeys.

Segments and events

Segments can reference event history. For example, you can create a segment for “users who completed onboarding in the last 7 days.” When a user tracks an event via the SDK, Nuxie re-evaluates any segments that depend on that event type.

Segments can also reference other segments. If “Premium Eligible” depends on membership in “Completed Onboarding,” Nuxie evaluates the dependency first, then the dependent segment. See Using Segments for details on dependencies.

Dashboard

The Segments list in the dashboard shows every segment for the current app and environment. For each segment, you can see:

Name and optional description
Member count – How many users currently match the conditions
Experience usage – How many experiences reference this segment

Click a segment to open its detail view with three tabs:

Overview – Edit the segment conditions using the visual builder.
Customers – Browse the list of users currently in the segment.
Usage – See which experiences reference this segment.

Next steps

Segment Builder – Create segments with the visual condition editor.
Using Segments – Reference segments in experiences, experiments, and the SDK.