--- title: About segments description: "Segments in Amplitude are reusable filters that narrow a chart to users, sessions, or events based on properties or behavior. Learn how segment scope works." product: analytics lang: en last_updated: 2026-10-29 token_estimate: 1475 --- # About segments > For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`. Segments in Amplitude are durable, reusable, and shareable filters that identify a subset of users, sessions, or events based on characteristics (properties) or behaviors (events). Use segments to narrow a chart to the group you care about and to compare groups side by side. > **Note:** > > Amplitude is gradually rolling out the updated segments experience through mid-November 2026. If your organization doesn't have the features on this page yet, check back after mid-November. You can build segments directly in a chart's Segmentation Module, or in the [advanced segment builder](https://amplitude.com/docs/analytics/segments/advanced-segment-builder), which adds hierarchical containers, sequential operators, and nested conditions. ## Segment scopes Every segment filter has a scope. The scope determines which events Amplitude returns when a user, session, or event matches the condition. - **User scope**: Includes every session and event for the users who match the condition. When the condition is `Complete Purchase`, Amplitude returns all other events those users triggered in the chart's time range, before and after the purchase. - **Session scope**: Includes every event in the sessions that match the condition. When the condition is `Complete Purchase`, Amplitude returns all other events in the session, before and after the purchase. - **Event scope**: Includes only the events that match the condition. When the condition is `Complete Purchase`, Amplitude returns only the purchase event. The following illustration shows which events each scope includes when you apply the same filter. #### User scope ![Events included by user scope for a Complete Purchase filter](https://amplitude.com/docs/images/diagrams/segments-scope-user.svg) ![Events included by user scope for a Complete Purchase filter](https://amplitude.com/docs/images/diagrams/segments-scope-user.dark.svg) #### Session scope ![Events included by session scope for a Complete Purchase filter](https://amplitude.com/docs/images/diagrams/segments-scope-session.svg) ![Events included by session scope for a Complete Purchase filter](https://amplitude.com/docs/images/diagrams/segments-scope-session.dark.svg) #### Event scope ![Events included by event scope for a Complete Purchase filter](https://amplitude.com/docs/images/diagrams/segments-scope-event.svg) ![Events included by event scope for a Complete Purchase filter](https://amplitude.com/docs/images/diagrams/segments-scope-event.dark.svg) ### Example: how scope changes results User A and User B each had two sessions. Only User B completed a purchase, in their second session. ![User A and User B each have two sessions, and User B completes a purchase in the second session](https://amplitude.com/docs/images/analytics/segments-scope-example-users.png) When you count `Product View` events with a `Complete Purchase` filter, each scope returns a different result: - **Event scope**: 0 product views. Amplitude returns only the `Complete Purchase` event. - **Session scope**: 1 product view. The session that included the purchase had one product view. - **User scope**: 2 product views. The user who completed the purchase viewed two products across both sessions. ![Breakdown of Product View and Complete Purchase counts for user-, session-, and event-scoped segments](https://amplitude.com/docs/images/analytics/segments-scope-example-results.png) ## Amplitude-provided segments Some charts include three default segments: - **Any Users**: Includes all users. - **Active Users**: Includes users who logged at least one [active event](https://amplitude.com/docs/data/change-event-activity-status) during the selected time range. - **New Users**: Includes users in the interval in which they first logged an event. The Active Users and New Users segments are available in [Event Segmentation](https://amplitude.com/docs/analytics/charts/event-segmentation/event-segmentation-build), [Funnel](https://amplitude.com/docs/analytics/charts/funnel-analysis/funnel-analysis-build), [Retention](https://amplitude.com/docs/analytics/charts/retention-analysis/retention-analysis-build), and [Sessions](https://amplitude.com/docs/analytics/charts/user-sessions/user-sessions-track-engagement-frequency) charts. Other chart types support only Any Users. ## Classic Segments and Advanced Segments Amplitude stores saved segments in one of two formats: - **Classic Segments**: Support filters based on user properties, events, and cohort membership. Classic Segments match what you can build directly in the chart's Segmentation Module. - **Advanced Segments**: Extend Classic Segments with session filtering, nested conditions, and ordered event sequences. > **Note:** > > Segments created before October 20, 2026, are Classic Segments. Amplitude plans to migrate Classic Segments to Advanced Segments in 2027. These limitations apply to Advanced Segments: - You can't save a segment that includes an interval cohort in Advanced Segments. - You can save only one segment at a time. ## Work with segments - [Create segments](https://amplitude.com/docs/analytics/segments/create-segments): Add filters in a chart, compare segments, and save a segment for reuse. - [Segment operators](https://amplitude.com/docs/analytics/segments/segment-operators): Look up how property, behavioral, and session operators evaluate. - [Advanced segment builder](https://amplitude.com/docs/analytics/segments/advanced-segment-builder): Combine scopes, nest containers, and filter on event sequences. - [Segments and cohorts](https://amplitude.com/docs/analytics/segments/segments-and-cohorts): Decide when to use a segment or a cohort, and convert a segment to a cohort.