About Segment Containers

A Segment sets conditions to filter a visitor based on his or her attributes or interactions with your site. To set conditions in a segment, you set rules to filter visitors based on visitor characteristics and/or navigation traits. To further break down visitor data, you can filter based on specific visits and/or page view hits for each visitor. The Segment Builder provides a simple architecture to build these subsets and apply rules as nested, hierarchical Visitor > Visit > Hit containers.

How-To Video

This YouTube Video give a short overview of what segment containers are and how to use them.

Video Name Video Link
Segment Containers Segment Containers in Adobe Analytics

About Containers

The container architecture employed in the Segment Builder defines Visitor as the outermost container, containing overarching data specific for the visitor across visits and page views. A nested Visit container lets you set rules to break down the visitor's data based on visits, and a nested Hit container lets you break down visitor information based on individual page views. Each container lets you report across a visitor's history, interactions broken down by visits, or break down individual hits.

Visitor Container

The Visitor container includes every visit and page view for visitors within a specified time frame. A segment at the Visitor level returns the page that meets the condition plus all other pages viewed by the visitor (and only constrained by defined date ranges). As the most broadly-defined container, reports generated at the Visitor container level will return page views across all visits and lets you generate a multi-visit analysis. Consequently, the Visitor container is the most susceptible to change based on defined date ranges.

Visitor containers can include values based on a visitor's overall history:

  • Days Before First Purchase
  • Original Entry Page
  • Original Referring Domains

Visit Container

The Visit container lets you identify page interactions, campaigns, or conversions for a specific web session. The Visit container is the most commonly used container because it captures behaviors for the entire visit session once the rule is met and lets you define which visits you want to include or exclude in building and applying a segment. It can help you answer the question of how many visitors viewed the News and Sports section in the same visit? Or pages that attributed to a successful conversion to a sale?

Visit containers include values based on occurrence per visit:

  • Visit Number
  • Entry Page
  • Return Frequency
  • Participation Metrics
  • Linearly allocated metrics

Hit Container

The Hit container defines which page hits you would like to include or exclude from a segment. It is the most narrow of the containers available to let you identify specific clicks and page view where a condition is true, letting you view a single tracking code, or isolate behavior within a particular section of your site. You may also want to pinpoint a specific value when an action occurs, such as the marketing channel when an order was placed.

Hit containers include values based single page breakdowns:

  • Products
  • List Props
  • List eVars
  • Merchandising eVars (in context of events)
    Note: If you use this container on a value that persists, such as an evar, it will pull in every hit where that value is persisting. In the case of a tracking code that expires after a week, that value could be persisting across multiple visits.

Logic Group Container

The Logic Group container allows you to provide a separate container within the segment rules to filter entities not based on hierarchy. For example, you may want to provide a container nested within the segment that filters based on Visitor. This type of logic requires you to break the hierarchy (as you are already have a top-level Visitor container) to filter only for selected visitors. This can be accomplished using the Logic Group container. See Logic Group examples for additional information.

Nesting Containers

When creating segment containers within other containers, you are in essence creating a segment within a segment. The following logic is used with nested containers:

  1. Determine what data is included using the outermost container. Any data that does not match this outer rule is discarded in the segmented report.
  2. Apply the nested rule to the remaining data. The nested rule does NOT apply to any hits that the first rule throws out.
  3. Repeat until all nested container rules have been calculated. The remaining data is then included in the resulting report.
You can use nesting between containers as well as between rules within a container. Here is what you can nest in each container:
Container Name What you can nest inside
Hit Events only
Visit Hit container, Events
Visitor Visit container, Hit container, Events
Logic Group Visitor container, Visit container, Hit container

Include multiple containers within a single definition

Including multiple segments in a new compound segment lets you refine data even further. Dragging two existing segments together acts as an "OR" statement when filtering visitors. All containers in the canvas are reviewed against all data, and any data that matches any of the containers is included in the reporting.

For example, dragging a Visit container where Country = United States with a Visit container where Order = True

Country = United States + Order = True

will build a segment that behaves in this order:

  1. This segment would first look at your entire data and identify all visitors within the United States.
  2. The segment would then look at all your data again, searching to see if any visitors made an an order.
  3. Both sets of data would then be applied to the report.

Containers for Sequential Segments

Sequential segmentation employs the same basic containers, including Visitors, Visits, and Hits (including page views or other dimensions) nested hierarchically.

Visitors constitute the highest-order container in sequential segmentation, with Visits contained within the Visitors container, and Hits contained within the Visitors or Visits containers. This container hierarchy must be maintained to build well-ordered sequential segments.

To build sequential segments, containers are nested and sequential logic joined using the THEN operator that requires each container to be true based on the sequence of the visitor.

The only exception to this hierarchy of containers is when using the Logic Group container. The Logic Group container lets you nest a hit within a container without order to capture events and dimensions but outside of a sequential order.