See
A sequential segment has some basic functionality and additional options that you can configure to add more complexity to the sequential segment:
Basics
The basics of building a sequential segment are no different than building a regular segment using the Segment builder. A regular segment becomes a sequential segment automatically as soon as you select the Then operator in the main definition or in any of the containers you use within the Segmentation builder.
Examples
The examples below illustrate how you use sequential segments in various use cases.
Simple sequence
Identify visitors who viewed a page and then viewed another page. The hit-level data is segmented using this sequence. Irrespective of previous, past, or interim visitor visits, or the time or number of page views occurring between the visits.
Sequence across visits
Identify visitors who viewed a page in one visit, then viewed another page in another visit. To differentiate between visits, use containers to build the sequence and define
Mixed-level sequence
Identify visitors who view two pages across an undetermined number of visits, and then view a third page in a separate visit. Again, use containers to build the sequence and define
Aggregate sequence
Identify visitors who at their first visit visited a specific page and then later visited some other pages. To differentiate between the sequence of hits, use containers to separate the logic on a
Nest a sequence
Identify all visits where a visitor visits one page before another page and then have follow-up visits that involve two other pages. For example, identify all visits where a visitor first visits the home page, then a category 1 page and then has other visits where in each visit the category 2 and category 3 page are visited.
After and Within
You can use
Time constraints
To apply time constraints to the Then operator:
- Select
- Select Within or After from the context menu.
- Specify a time period (Minute, Hour, up until Years).
- Select the
To remove a time constraint, use
The table below explains in more detail the time constraint operators.
Operators | Description |
---|---|
After | The After operator is used to specify a minimum limit on the amount of time between two checkpoints. When setting the After values, the time limit begins when the segment is applied. For example, if the After operator is set on a container to identify visitors who visit page A, but don’t return to visit page B until after one day, then that day will start when the visitor leaves page A. For the visitor to be included in the segment, a minimum of 1440 minutes (one day) must transpire after leaving page A to view page B. |
Within | The Within operator is used to specify a maximum limit on the amount of time between two checkpoints. For example, if the Within operator is set on a container to identify visitors who visit page A, and then return to visit page B within one day, then that day begins when the visitor leaves page A. To be included in the segment, the visitor has a maximum time of one day before opening page B. For the visitor to be included in the segment, opening page B must occur within a maximum of 1440 minutes (one day) after leaving page A to view page B. |
After but Within | When using both the After and Within operators, both operators start and end in parallel, not sequentially. For example, you build a segment with the container set to: After = 1 Week(s) and Within = 2 Week(s) .The conditions to identify visitors in this segment are met only between one and two weeks. Both conditions are enforced from the time of the first page view. |
Examples
Some examples of using the time constraints.
After operator
Identify visitors that visited one page and then another page only after two weeks. For example, visitors that visited the Home page, but the Women | Shoes page only after two weeks.
If a page view for the Home happens on June 1, 2024, at 00:01, then a page view to page Women | Shoes will match as long as that page view occurs after June 15, 2024 00:01.
Within operator
Identify visitors that visited one page and then another page within five minutes. For example, visitors that visited the Home page and then the Women | Shoes page within 5 minutes.
If a page view for the Home happens on June 1, 2024, at 12:01, then a page view to page Women | Shoes will match as long as that page view occurs before June 15, 2024 12:16.
After but Within operator
Identify visitors that visited one page then visited another page after two weeks but within one month. For example, visitors that visited the Home page and then after two weeks and within one month the Women | Shoes page.
Any visitors hitting the Home page on June 1, 2024 and who are returning to visit the Women | Shoes page after June 15, 2019 00:01, but before July 1, 2019 qualify for the segment.
Hit, Visit and Dimension constraints
The
Example
Below is an example of a sequential segment looking for visitors that visited one product category page (Women | Shoes), followed by a checkout page (Checkout | Thank You) within one page.
The following example sequences match or do not match:
Sequence |
|
---|---|
Page Women | Shoes followed by page Checkout | Thank You |
|
Page Women | Shoes followed by page Women | Tops followed by page Checkout | Thank You |
|
Include
You can specify what data to include in your sequential segment or in a sequential container that is part of your sequential segment.
Everyone
To create a sequential segment that includes everyone, select the option
The sequential segment identifies data that match the given pattern as a whole. Below is an example of a basic sequence segment looking for visitors that visited one product category page (Women | Shoes), followed by a checkout page (Checkout | Thank You). The segment is set to
The following example sequences match or do not match:
Sequence |
| |
---|---|---|
1 | Women | Shoes then Checkout | Thank You in the same visit |
|
2 | Women | Shoes then Men | Shoes then Checkout | Thank You (across different visits) |
|
3 | Checkout | Thank You then Women | Shoes |
|
Only Before Sequence and Only After Sequence
The options
Consider a definition specifying a sequence of a component with criteria identified by B, followed (Then) by a component with criteria identified by D. The three options would identify data as follows:
B Then D | A | B | C | D | E | F |
---|---|---|---|---|---|---|
Include Everyone |
|
|
|
|
|
|
Only Before Sequence |
|
| ||||
Only After Sequence |
|
|
|
B Then D (occurs multiple times) | A | B | C | D | B | C | D | E |
---|---|---|---|---|---|---|---|---|
Include Everyone |
|
|
|
|
|
|
|
|
Only Before Sequence |
|
|
|
|
| |||
Only After Sequence |
|
|
|
|
|
Example
You have defined three version of a sequential segment for site sections. One with the option
When reporting on site sections using these three segments, the example output in a freeform table looks like:
Exclude
Segment definitions include all data unless you specifically exclude
Exclude allows you to dismiss common data and create segments with more focus. Exclude also allows you to create segments excluding specific groups of visitors. For example, to define a segment that specifies visitors that placed orders and then excluding that group of visitors to identify non-purchasers. A best practice is to create rules that use a broad definition rather than trying to use Exclude to target specific visitors that match specific include values.
Example of exclude definitions are:
- Exclude pages. Use a segment definition to strip out a specific page (such as Home Page) from a report, create a Hit rule where the page equals
Home Page
, and then exclude the rule. This definition automatically includes all pages except the Home Page. - Exclude referring domains. Use a definition that includes only referring domains from Google.com and excludes all others.
- Identify non-purchasers. Identify when orders are greater than zero and then exclude the Person.
Exclude can be used to identify a sequence where visitors do not be part of specific visits or perform specific hits. Exclude can also be included within a Logic Group (see below).
You can exclude containers, not components.