Segments

What Segments Are in GA4

A segment is a subset of your analytics data isolated by conditions you define — organic-search sessions, users from a specific country, people who triggered a purchase event. In GA4, segments live inside Explorations and come in three types (user, session, event), which is a real shift from Universal Analytics, where segments applied across nearly every standard report.

The stakes: aggregate numbers lie by averaging. Segmenting is how you separate the traffic that converts from the traffic that bounces, and it's the difference between "engagement went up" and "engagement went up for organic mobile users on the pricing page."

The Big UA-to-GA4 Change

In Universal Analytics you built a segment once and it followed you into almost every report, and you could stack several at a time to compare. GA4 splits that behavior in two. Full, condition-based segments now exist only inside Explorations. In standard reports you instead use comparisons — lighter, dimension-based filters (e.g. Session medium = organic) applied at the top of the report. Don't go looking for the old segment builder on the Reports snapshot; it isn't there.

The three GA4 segment types

• User segment — everyone who ever met the condition, across all their sessions. "Users who purchased in the last 30 days."
• Session segment — the sessions that met the condition, not the whole user. "Sessions that started from organic search."
• Event segment — individual events matching the condition. "All page_view events on the checkout page."

Choosing wrong distorts everything. A user segment for "sessions from organic" will pull in that user's paid and direct sessions too, because the whole user qualifies once any of their behavior matches.

A real example

You want to compare organic-search visitors against paid visitors on engagement. In an Exploration, build a session segment with condition Session default channel group = Organic Search, and a second session segment for = Paid Search. Drop both into a free-form table with average engagement time and key events. Now you can see organic sessions engage 40 seconds longer but paid converts at a higher rate — a story the blended average completely hid.

How to Build a Segment

1. Open Explore and start a blank or template Exploration.
2. In the Variables panel, click the + next to Segments.
3. Choose the type — User, Session, or Event — based on the unit your question is about. Get this right before adding conditions.
4. Add conditions (e.g. Session default channel group exactly matches Organic Search). Stack AND/OR groups as needed; use the sequence option if order matters.
5. Watch the summary — GA4 estimates the % of users/sessions the segment captures so you can sanity-check it before saving.
6. Save and drag the segment onto the canvas. Add a second segment to compare side by side (up to four).
7. To reuse it for marketing, tick "Build an audience" when creating the segment so it also becomes a GA4 Audience.

For standard reports where you just need a quick cut, skip segments entirely: click Add comparison at the top of the report and filter by a dimension like Session medium.

Common Mistakes and How to Fix Them

• Hunting for segments in standard reports. They don't exist there. Fix: use comparisons in Reports, segments in Explorations.
• Using user scope when you mean sessions. A user segment sweeps in all of that person's sessions, not just the qualifying ones. Fix: use a session segment for channel/campaign questions.
• Confusing a comparison with a segment. Comparisons are simple dimension filters; they can't do sequences or multi-condition logic. Fix: move complex conditions into an Exploration segment.
• Ignoring the sampling/estimate note. A segment that captures 0.2% of sessions will give you noisy, unreliable numbers. Fix: widen conditions or lengthen the date range.
• Not saving segments as audiences. Rebuilding the same segment for ads is wasted effort. Fix: check "Build an audience" so it's reusable for remarketing.

FAQ

Why can't I apply a segment to my standard GA4 report?

Because GA4 restricts full segments to Explorations. In standard reports, use the Add comparison control at the top instead — it's the dimension-based equivalent.

What's the difference between a segment and a comparison?

A comparison is a lightweight dimension filter available in standard reports (e.g. Device = mobile). A segment is a richer, condition-based subset — supporting sequences, multiple scopes, and AND/OR logic — that only works in Explorations.

How many segments can I compare at once?

Up to four per Exploration. If you need more angles, split them across multiple Explorations or use a breakdown dimension alongside your segments.

Can a segment become a remarketing audience?

Yes. When you create the segment, tick "Build an audience" and GA4 also saves it as an Audience you can use for ads and personalization.

Did my Universal Analytics segments carry over to GA4?

No. Segment definitions didn't migrate. You rebuild them in GA4's Exploration segment builder, keeping the new user/session/event scoping in mind.

Related Terms

• Google Analytics
• Custom Dimensions
• Landing Page Report
• GA4 for SEO: Organic-Only Reports