Analytics Segment
An analytics segment is a subset of your data, isolated by a set of conditions, so you can analyze one group instead of the whole dataset. Segments answer questions that site-wide averages hide, such as whether mobile buyers convert differently from desktop visitors. Google Analytics 4 defines a segment as “a subset of your Analytics data” and keeps segments inside Explorations, where they apply retroactively to data you have already collected.
Why Segments Matter
A property-wide average describes almost nobody. A 2.1% conversion rate across all traffic can hide paid search converting at 6% and social converting at 0.3%, and the average tells you to do nothing about either.
Segments separate those populations so the numbers become actionable. Three questions they answer well:
- Behavioral: what do users who reached checkout do differently from users who did not?
- Acquisition: do sessions from one campaign engage longer than sessions from another?
- Diagnostic: is a drop in conversions site-wide, or confined to one device, country, or landing page?
Types of Segments in GA4
GA4 offers three segment types, and the type sets the scope of what gets returned.
| Segment type | What it returns | Example |
|---|---|---|
| User | Every session and event belonging to users who met the condition | Everyone who has ever purchased |
| Session | Only the sessions that met the condition | Sessions that began from a paid campaign |
| Event | Only the individual events that met the condition | purchase events from Germany |
Universal Analytics offered user and session segments only. Event scope is new to GA4 and is the narrowest of the three, useful when one event property matters and the surrounding session does not.
Scope cannot be changed after a segment is created. Switching from session to user scope means rebuilding the segment.
User Segment vs Session Segment
The same condition returns different numbers depending on scope, and this is the most common source of confusion.
Take one condition: the user viewed /pricing.
- A user segment returns every session those people ever had, including sessions where they never opened the pricing page. It answers “what else do pricing-page visitors do?”
- A session segment returns only the sessions that actually contained a pricing-page view. It answers “what happens in a visit that includes pricing?”
Suppose 1,000 users viewed pricing at some point, and those users produced 4,000 sessions in total, but only 1,200 of those sessions included a pricing view. The user-scoped segment reports 4,000 sessions. The session-scoped one reports 1,200. Neither is wrong. Reporting the first number while describing the second is.
Pick user scope for lifetime and cohort questions. Pick session scope for campaign, channel, and landing-page questions.
Segments vs Audiences in GA4
Segments analyze. Audiences activate. They are built with a nearly identical condition builder, which is why they get treated as interchangeable, but they behave differently in every way that matters.
| Segment | Audience | |
|---|---|---|
| Where it works | Explorations only | Standard reports, Google Ads, remarketing |
| Historical data | Fully retroactive across the date range | 30-day lookback, then forward only |
| Availability | Immediate | 24 to 48 hours to accumulate users |
| Limit | 10 per exploration, 4 applied at once | 100 per property, 400 on Analytics 360 |
| Purpose | Analysis | Targeting and export |
The retroactivity gap is the one that costs people data. Google’s documentation states that when you create an audience, “Analytics adds any users who have met the audience criteria during the last 30 days”. Anything older is gone. Create audiences before you need them; segments can always be built after the fact.
How to Build a Segment in GA4
- Open Explore and choose any technique, such as Free form.
- In the Variables column, click the + next to Segments.
- Pick User, Session, or Event scope. Choose deliberately, since this cannot be changed later.
- Add your conditions. For user segments, set the condition scoping (across all sessions, within the same session, or within the same event) to control how strictly the conditions must co-occur.
- Add a sequence if order matters, for example a category view followed by an add to cart.
- Name the segment and click Apply. The summary panel estimates the share of users it matches before you commit.
Session segments built on campaign conditions are only as reliable as the tagging underneath them. Filtering on Session campaign returns nothing useful if the same campaign was tagged three different ways, which is what building links with a UTM builder prevents.
Segment Limits and Common Mistakes
Google’s documented limits: an exploration holds up to 10 segments, and you can “apply up to four segments to an individual exploration technique at one time”.
Four mistakes worth avoiding:
- Looking for segments in standard reports. They do not exist there. Segments are available only within the Explore module. Standard reports use comparisons instead.
- Ignoring sampling. Explorations may sample when a query covers more than 10 million events, so a broad date range plus a narrow segment can return an estimate rather than a count.
- Choosing scope by habit. Session scope is the right default for acquisition analysis, not user scope.
- Building an audience when a segment would do. Audiences cost you the historical data; use them only when the group needs to leave GA4.
Frequently Asked Questions
What is a segment in analytics?
A segment is a subset of analytics data defined by conditions, used to analyze one group separately from the total. Conditions can be based on demographics, technology, traffic source, behavior, or events. In GA4, segments are built and applied inside Explorations, and they apply to historical data as well as new data.
What is the difference between GA4 segments and audiences?
Segments are for analysis inside Explorations and are fully retroactive. Audiences are for activation, work in standard reports and Google Ads, and only look back 30 days from the day you create them. A property allows 100 audiences on the standard tier and 400 on Analytics 360, while an exploration holds 10 segments.
What is the difference between a user segment and a session segment?
A user segment returns all activity from users who met the condition, including sessions where the condition never occurred. A session segment returns only the sessions in which the condition was met. The user-scoped version almost always reports higher session and event counts, so the two are not interchangeable in a report.
Why can’t I find segments in my GA4 reports?
Segments appear only in the Explore module, not in standard reports. Google’s documentation confirms segments are available only within Explore. For a quick split inside a standard report, use the comparisons feature at the top of the report instead.
To see campaign click data next to the segments you build in GA4, use linkutm’s link analytics.