Isolate and examine subsets of your data.
A Segment is a subset of your Analytics data. For example, of your entire set of users, one Segment might be users from a particular country or city. Another Segment might be users who purchase a particular line of products or who visit a specific part of your site.
Segments let you isolate and analyze those subsets of data so you can examine and respond to the component trends in your business. For example, if you find that users from a particular geographic region are no longer purchasing a line of products in the same volume as they normally have, you can see whether a competing business is offering the same types of products at lower prices. If that turned out to be the case, you could respond by offering a loyalty discount to those users that undercuts your competitor's prices.
You can also use Segments as the basis for Remarketing Audiences. For example, you might create a Segment of users who visit your menswear pages, and then target just those users (your Remarketing Audience) with a remarketing campaign that is focused on the new items that you are adding to those pages.In this article:
Segments represent either subsets of sessions or subsets of users:
- Subsets of sessions: for example, all sessions originating from Campaign A; all sessions during which a purchase occurred
- Subsets of users: for example, users who have previously purchased; users who added items to their shopping carts, but didn’t complete a purchase
Segments are non-destructive filters that do not change your underlying data. Once you apply a Segment, it remains active as you navigate throughout the reports, until you remove it. You can apply up to four Segments at a time, and compare results from each Segment side by side in your reports.
In addition to analyzing data with Segments, you can use them to build audiences for remarketing.
Google Analytics includes predefined segments (System Segments) that you can use as provided, or that you can copy and edit to create new custom Segments. You can also build your own Segments from scratch. In addition, you can import Segments from the Analytics Solutions Gallery, a free marketplace where Analytics users share Segments and other solutions they’ve developed.
Segment definition and scope
You define Segments by creating filters based on the dimensions and metrics in your Analytics reports; for example:
- User Type exactly matches “Returning User”
- Country/Territory exactly matches “United States”
- Ecommerce Conversion Rate > "0.2%"
In addition to the dimensions and metrics you use in filters, you also have to set the scope of the data for a filter. There are three different scopes you can use:
- Hit: Behavior confined to a single action, for example, viewing a page or starting a video.
- Session: Behavior within a single session; for example, the goals that users completed during a session, or the amount of revenue they generated during a session.
- User: Behavior across all sessions within the date range you’re using, up to 90 days; for example all the goals users completed or all the revenue they generated (across all sessions) during the date range.
You use the Segment builder to define the component filters of a Segment.
Limits on Segments
Segments are subject to the following limits:
- 1000 Segments per account
- 100 Segments per user, per view
- 100 Segments shared across users, per view
These limits include system Segments and any Segments you create or import. You cannot create or import additional Segments once you reach these limits.
Segments applied to reports
You can have up to 4 segments applied to your reports at any one time.
With user-based Segments, you can apply a maximum date range of 90 days to your reports. If your date range is already set to more than 90 days, then when you create a user-based Segment, Analytics resets the date range to 90 days from the start date.
Segments based on the Date of First Session option are limited to maximum range of 31 days.
Do not use Segments with Multi-Channel Funnel reports. Use Conversion Segments instead.