DocumentationAnalyticsComponents Guide

Segment builder

Last update: Mon Jun 23 2025 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Topics:
  • Segmentation

CREATED FOR:

  • User
  • Admin

The Segment builder dialog is used to create new or edit existing segments. The dialog is titled New segment or Edit segment for segments that you create or manage from the Segment manager.

Segment builder
Segment details window showing fields and options described in the next section.
Create or Edit segment
Segment details window showing fields and options described in the next section.
  1. Specify the following details ( Required is required):

    Element
    Description
    Report suite
    You can select the report suite for the segment.
    Project-only segment
    An info box to explain that the segment is only visible in the project where it is created and that the segment will not be added to your component list. Enable Make this segment available to all your projects and add it to your component list to change that setting. This info box is only visible when you create a quick segment and turn the quick segment info a regular segment using Open builder from the Quick segment interface.
    Title Required
    Name the segment, for example, Last month mobile visitors.
    Description
    Provide a description for the segment, for example, Segment to define the mobile customers for the last month.
    Tags
    Organize the segment by creating or applying one or more tags. Start typing to find existing tags you can select. Or press ENTER to add a new tag. Select CrossSize75 to remove a tag.
    Definition Required
    Define your segment using the Definition builder.
  2. To verify whether your segment definition is correct, use the constantly updated preview of the results of the segment at the top right.

  3. To publish your segment to the Experience Cloud, select Publish this segment to the Experience Cloud (for report suite). See Publish segments to Experience Cloud for more information.

  4. Select:

    • Save to save the segment.
    • Save As to save a copy of the segment.
    • Delete to delete the segment.
    • Cancel to cancel any changes you made to the segment or cancel the creation of a new segment.

Definition builder

You use the Definition builder to construct your segment definition. In that construction, you use components, containers, operators and logic.

You can configure the type and scope of your definition:

  1. To specify the type of your definition, specify whether you want the build an include or exclude definition. Select Setting Options and from the drop-down menu Include or Exclude.
  2. To specify the scope of your definition, select from the Include or Exclude drop-down menu whether you want the scope of the definition to be Hits, Visits, or Visitors.

You can always change these settings later.

Components

A vital part of the construction of your segment definition is using dimensions, metrics, existing segments and date ranges. All these components are available from the component panel in the Segment builder.

Start building a definition

To add a component:

  1. Drag and drop a component from the components panel onto Drag and drop Metric(s), Segment(s), and/or Dimensions here. You can use the Search in the components bar to search for specific components.
  2. Specify details for the component. For example, select a value from Select value. Or enter a value. What and how you can specify one or more values depends on the component and the operator.
  3. Optionally modify the default operator. For example, from equals to equals any of. See Operators for a detailed overview of the available operators.

To edit a component:

  • Select a new operator for the component from the operator drop-down menu.
  • Select or specify a different value for the operator if appropriate.
  • If the component type is a dimension, you can define the attribution model. See Attribution model for more information.

To delete a component:

  • Select CrossSize75 in a component.

Containers

You can group multiple components in one or more containers and define logic within and between containers. Containers allow you to build complex definitions for your segment.

Add a container

  • To add a container, select Add container from Setting Options.
  • To add an existing component to the container, drag and drop the component into the container.
  • To add another component to the container, drag and drop a component from the component panel into the container. Use the blue insertion line as a guide.
  • To add another component outside of the container, drag and drop a component from the component panel outside of the container, but inside the main definition container. User the blue insertion line as a guide.
  • To modify the logic between components in a container, between containers or between a container and a component, select the appropriate And, Or, Then. When you select Then, you turn the segment into a sequential segment. See Create sequential segment for more information.
  • To switch the container level, select WebPage Hits, Visit Visits or User Visitors.

You can use Setting in a container for the following actions:

Container action
Description
Add container
Add a nested container to the container.
Exclude
Exclude the result from the container in the segment definition. A thin red left bar identifies an exclude container.
Include
Include the result from the container in the segment definition. Include is the default. A thin gray left bar identifies an include container.
Name container
Rename the container from its default description. Type a name in the text field. If you provide no input, the default description is used.
Delete container
Delete the container from the definition.

Date ranges

You can build segments that contain rolling date ranges. This way, you are able to answer questions about ongoing campaigns or events. For example, you can build a segment that includes everyone who has made an online purchase over the last 60 days.

Segment using rolling date range

recommendation-more-help

See VideoCheckedOut Rolling date ranges in segments for a demo video.

Stack segments

You can build a segment using segments. When you use segments in a segment, you can optimize your segment and reduce the complexity.

Imagine you want to segment on the combination of interaction channel (5) and US states (50). You could either build 250 segments, each for the unique combination of device type (mobile phone versus tablet) and US state. To get the tablet users in California, you would use one of the 250 segments:

Simple segment for California and tablet

Or, you could define 55 segments: 50 segments for the US states, and 5 for the possible interaction channels. And then stack the segments to obtain the same results. To get the California mobile app users, you would stack two segments:

Stacked segment for CA and tablet

Attribution

When you use a dimension in the Segment builder, you have the options to specify the attribution model for that dimension. The attribution model you select determines whether data qualifies for the condition you have specified for the dimension component.

Select Setting within the dimension component and select one of the Attribution models from the popup:

Models
Description
Repeating model (default)
Include instance and persisted values for the dimension to determine qualification.
Instance
Include only instance values for the dimension to determine qualification.
Non-repeating instance
Include unique instance (non-repeating) values for the dimension to determine qualification.

Attribution model on dimension when building a segment

Example

As part of a segment definition you have specified the following condition: Page Name equals Women. Similar to the example above. You repeat this segment definition using the two other attribution models. So you have three segments each with their own attribution model:

  • Women Page - Attribution - Repeating (default)
  • Women Page - Attribution - Instance
  • Women Page - Attribution - Non-repeating instance

The table below explains, for each attribution model, which incoming events are qualified CheckmarkCircle for that condition.

Women Page - Attribution -
attribution model
Event 1:
Page Name equals
Women
Event 2:
Page Name equals
Men
Event 3:
Page Name equals
Women
Event 4:
Page Name equals
Women
(persisted)
Event 5:
Page Name equals
Checkout
Event 6:
Page Name equals
Women
Event 7:
Page Name equals
Home
Repeating (default)
CheckmarkCircle
Remove
CheckmarkCircle
CheckmarkCircle
Remove
CheckmarkCircle
Remove
Instance
CheckmarkCircle
Remove
CheckmarkCircle
Remove
Remove
CheckmarkCircle
Remove
Non-repeating instance
CheckmarkCircle
Remove
CheckmarkCircle
Remove
Remove
CheckmarkCircle
Remove

An example report on events using the three segments looks like:

Segment attribution model results

Segment templates

Segment templates are provided for common segmentation use cases, such as “First-time Visits” or “Vists from Mobile Devices”. They are available in Workspace projects and in the segment builder as building blocks for new segments.

Templates are denoted by the Adobe “A” logo. A sample of the templates are listed below:

Template Name
Definition
Abandon Cart

View data for visitors that added items to their carts but did not order anything. In the Segment Definition, the container is Visit. The rule for this sequential segment is

Cart Additions is not null

Then

Orders equals 0.

First Time Visits

View data for visitors that have visited a maximum of one [1] times. In the Segment Definition, the container is Visit. The rule is

Visit Number equals 1.

Non-Purchasers

View data for visitors that have not participated in an order event. In the Segment Definition, the container is Visitor. This segment uses the Exclude logic. The rule is

Orders is not null.

Non-Single Page Visit (Non-Bounces)

View data for visitors that visited more than once. In the Segment Definition, the container is Visitor. This segment uses the Exclude logic. The rule is

Single Access is not null.

Paid Search

View data from visitors originating from a paid search. In the Segment Definition, the container is Visit. The rule is

Paid Search equals 1.

Purchasers

View data for visitors that have participated in an order event. In the Segment Definition, the container is Visitor. The rule is

Orders is not null.

Return Visits

View data from visitors that have visited at least once. In the Segment Definition, the container is Visit. The rule is

Visit Number is greater than 1.

Single Page Visits

View data from visits in which you see a single page value, even though you may submit multiple page views during that visit. Single-page visits with exit link events are included in the segment. In the Segment Definition, the container is Visit. The rule is

Single Page Visits equals 1.

Viewed Product Didn't Add to Cart

View data for visitors that viewed products but had no cart additions. In the Segment Definition, the container is Visit. The rule for this sequential segment is

Product Views is not null

Then

Cart Additions equals 0.

Visits from Campaign

View data from visitors referred by campaigns. In the Segment Definition, the container is Visit. The rule is

Tracking Code is not null.

Visits from Mobile Devices

View data from visitors using mobile devices. In the Segment Definition, the container is Visit. The rule is

Mobile Device is not null.

Visits from Natural Search

View data from visitors not originating from a paid search. In the Segment Definition, the container is Visit. The rule is

Paid Search equals 0.

Visits from Non-Mobile Device

View data from visitors not using mobile devices. In the Segment Definition, the container is Visit. This segment uses the Exclude logic. The rule is

Mobile Device Type equals Mobile Phone

Or

Mobile Device Type equals Tablet.

Visits from Phones

View data from visitors using phones. In the Segment Definition, the container is Visit. The rule is

Device Type equals Mobile Phone.

Visits from Search Engines

View data from visitors referred by search engines. In the Segment Definition, the container is Visit. The rule is

Referrer Type equals Search Engines.

Visits from Social Sites

View data from visitors referred by social sites. In the Segment Definition, the container is Visit. The rule is

Referrer Type equals Social Networks.

Visits from Tablets

View data from visitors using tablets. In the Segment Definition, the container is Visit. The rule is

Device Type equals Tablet.

Visits with Visitor ID Cookie

View data from visitors to your site, where a persistent cookie is required. In the Segment Definition, the container is Visit. The rule is

Persistent Cookie equals 1.

46b8682c-fda6-4669-9355-1a44923e549e