TR / EN Contact
Success Stories Blog References Services Approach Ad Venture One TR / EN
Data · 30 Jun 2026 · Aydın Kara

Creating Segments in GA4 Explore Reports: Using the Right Segment for the Right Analysis

We will examine creating segments in GA4 Explore reports, the Sequence feature within User/Session segments, its difference from standard conditions, and common mistakes.

Creating Segments in GA4 Explore Reports: Using the Right Segment for the Right Analysis

Google Analytics 4 (GA4) Explore reports let you analyze user behavior in more detail by going beyond standard reports. The basis of these analyzes is Segments.

With segments, you can filter specific user groups, sessions or events, compare different audiences and obtain insights that you cannot see in standard reports.

In this article, we will examine creating segments in GA4 Explore reports, the Sequence feature within User/Session segments, its difference from standard conditions, and common mistakes.

Which Segment Type Should I Choose in GA4?

In Explore reports, the panel first offers you three basic segment types. Before starting your analysis, answering the following question makes it easier to choose the right segment: “Is what I want to analyze a user, a session, or a specific event?”

  • User Segment: Analyses users (along with all their past sessions) who meet the conditions you specify.
  • Session Segment: Analyses sessions with specific characteristics or in which specific actions occur.
  • Event Segment: Used when you want to isolate and analyze only specific events and their parameters.

A Powerful Feature of Segments: What is Sequence?

In some analyzes, the occurrence of a single event is not enough; you also need to know in what order the user performed the events.

Important Note: Sequence is not a separate segment type that you will see in the panel. It is an advanced condition architecture that you activate by clicking the "Add sequence" button in the upper right corner after selecting User Segment (or Session Segment, depending on your scenario).

Using the Sequence feature, you can find answers to critical questions like these:

  • Did the user who read the blog post make a purchase at a later stage?
  • Did users who used internal search view a product after this search?
  • Did the user who started the checkout process follow the steps and reach the payment step?

The Difference Between "Directly Followed By" and "Indirectly Followed By"

When creating a sequence condition, you must specify the chronological relationship between each step you add. GA4 offers you two options here:

1. Directly Followed By

Requires the second step to occur immediately after the first step.

  • Example Flow: view_item → add_to_cart
  • If the user triggers another automatically defined event such as scroll, click, page_view or user_engagement between these two events, they are not included in the segment.
  • This option suits very specific technical scenarios where you want to verify the event order exactly (in millisecond steps).

2. Indirectly Followed By

It is enough for the second step to occur at any time after the first step. Other events can happen in between.

  • Example Flow: view_item → scroll → page_view → add_to_cart
  • Even if the user takes other actions in between, they are included in the segment because they ultimately completed the goal steps in order.

Recommendation: In real user behavior, page views, scrolls or automatically collected engagement events always happen in between. Therefore, including e-commerce checkout flows, the option you should prefer in 90% of your analyzes is "Indirectly Followed By". Otherwise, your segment will turn out unnecessarily narrow.

Segment Scenarios with Practical Examples

Example 1: Do Users Who Read the Blog Post Make a Purchase?

  • Segment Type to Choose: User Segment
  • Condition Type: Sequence Step 1: page_view (Page path contains /blog) Step 2: purchase
  • Sequence Setting: Indirectly Followed By (Because after reading the blog, the user can browse the site, add products to their cart and purchase at the end of the day. This is a natural process.)

💡 Critical Comparison: What Would Happen If We Built This Segment with an "AND" Condition Instead of Sequence?

If you did not use Sequence and opened a standard User Segment with page_view (/blog) AND purchase, GA4 would completely ignore the chronological order.

  • Sequence: First the blog must be read, then the purchase made. (Measures the blog’s effect on sales - the Correct Method.)
  • Standard AND: The user must have both read the blog and made a purchase within the selected date range. (E.g. a user who bought the product on Monday and reads the blog post on Wednesday is included in this segment, even though the blog post made no contribution to that sale.)

Result: while the standard "AND" filter gives you a higher and misleading number of users, the Sequence filter shows the actual conversion journey.

Example 2: Do Users Coming from Organic Traffic Make a Purchase?

  • Segment Type to Choose: User Segment
  • Conditions (Standard Condition): Session source / medium contains organic Event Name = purchase
  • (In this scenario there is no need for the Sequence feature, since we are not looking for a before-and-after order between actions, only whether the two attributes intersect in the same user.)

Example 3: Do Those Who Start Checkout Reach the Payment Info Step?

  • Segment Type to Choose: Session Segment
  • Condition Type: Sequence Step 1: begin_checkout Step 2: add_payment_info
  • Sequence Setting: Indirectly Followed By (Even within the same session, the user may refresh the page or read the shipping policy, or other automatic events may be triggered between the two steps.)

The Most Common Mistakes When Creating Segments

  1. Choosing the Wrong Segment Type: Selecting Session Segment when you want to analyze a behavior that spans the user’s lifetime leads to data being interpreted incompletely or incorrectly.
  2. Using Standard "AND" Instead of Sequence Analysis: Using standard logical operators when analyzing a behavioral sequence distorts the data by including users in "reverse chronological" order, as in the blog example above.
  3. Choosing "Directly" by Default in Sequence Analysis: Failing to account for the noise events in between when analyzing the user journey leaves the segment with a user count close to zero.
  4. Adding Too Many Conditions: Each new filter narrows the segment further. Avoid shrinking the data set too much with filters of no strategic importance.

GA4 Explore segments are one of the most powerful analysis tools for seeing the real story behind user behavior.

Simply stacking conditions one under another (AND logic) can sometimes lead you to incorrect results. If your goal is to see whether one behavior triggers another, always make sure to use the Sequence feature within User or Session segments and the Indirectly Followed By setting.

Make it a habit to ask yourself this question before starting an analysis: “Exactly what timeline does the question I am trying to answer cover?” The answer will lead you to the right segment type and the right condition architecture.

Let’s talk about this for your brand.

Write to us →