Segment Filters
Segment filters are used to define the type of sessions to include in a segment.
Adding segment filters
-
When creating a segment, click Add filters.
The available segment filters appear in a series of tabs. Depending on the segment filter selected, the options available differ. For example, in the image below, you can select whether you want the filter to apply if DXA doesn't detect "Bird's nest" behavior in a session or if DXA does detect "Bird's nest" behavior.Note: For details on available segment filters, see Segment filter types. For details on the options available for each filter, see Segment filter options. -
Select the filter and option to apply.
-
Click Apply this filter.
The selected filter and option appear under Segment filters.
-
(Optional) Repeat steps 1 to 3 for any other filters you want to apply.
In the image below, the segment will capture sessions where DXA detects "Bird's nest" behavior and a focus time of up to 5 seconds.
-
Click Save Segment.
The segment is saved and appears on the list in Segment Definition. Allow some time for the segment data to process before it can be used.
You can now use the segment in sessions, heatmaps, forms, alerts, and technical reports using the Segment dropdown menu.
Segment filter types
Behavior
Use Behavior filters for segments where DXA doesn't detect or does detect specific visitor Behaviors, such as Bird Nesting and Rapid Scrolling.
The following options are available for each Behavior filter:
-
No — The segment captures sessions where DXA doesn't detect the selected Behavior.
-
Yes — The segment captures sessions where DXA does detect the selected Behavior.
Engagement
Filter | Description |
---|---|
Attribute | Display any element with a DXA ID or a custom ID. |
Bounced | Refers to whether the visitor just viewed one page and then left. |
Domain | What domain the user visited during their session (i.e if you have multiple domains or subdomains on an account, you can specify which domains you want to segment by). |
Entry page | The page that the visitor entered the property on. |
Entry Page Group | The page group that the visitor entered the website on. |
Exit page | The page that the visitor exited the website from. |
Exit Page Group | The page group that the visitor exited the website from. |
Focus time |
Length of time the page or screen was the main focus on the visitor's device. If the visitor goes to a different browser tab or opens a different program while DXA is running, this would count towards the total duration and not the focus time. |
Goal count | The number of goals achieved in the session. |
Opened tabs | The number of opened tabs that the visitor was viewing the property on during their session. |
Page count | The number of pages visited in a session. |
Page Group | Sessions from any point in a page group. |
Page title | The title of pages that the user viewed in their session. |
Pages viewed | The pages that the user viewed or didn't view in their session. |
Tag | Tags included in a session. |
Time on site | The amount of time the user spent on the property. |
Form
Filter | Description |
---|---|
Element abandoned | If a visitor has engaged with a field but not entered a value. |
Element completed | If a visitor has completed a specific element or field of a form. |
Element engaged | If a visitor has engaged with a specific element or field on a form. |
Element errored | If a visitor has encountered any validation errors on a specific element or field. |
Form abandoned | If a visitor abandoned a form. |
Form completed | If a visitor completed a form. |
Form engaged | If a visitor engages with any element within a form. |
Form errored | If a visitor encounters a validation error on a form. |
Form validation error | If a user encounters a form validation error. |
Integrations
Integrations filters allow you to add segments already created in supported data connectors, such as Medallia Digital and Google Analytics.
Technical
Filter | Description |
---|---|
Application error | If the visitor experienced an application error during their session. Application errors need to be configured using the sendApplicationError call.Note: This filter requires application error tracking to be enabled during DXA implementation. |
HTTP error | If the visitor received a specific HTTP error (such as 404 Not Found). This will need to be configured using the sendHTTPerror call. For more information, see Configuring Application Error Messages. Note: This filter requires HTTP error tracking to be enabled during DXA implementation. |
HTTP error occurred | If any HTTP error occurred during the visitor's session. As mentioned above, these need to be configured using the sendHTTPError call. |
JavaScript error | If the visitor received a JavaScript error at any time in their session. |
URL fragment | If fragmenting is set up then you can segment by these fragments. For example, if you had a URL such as the following: www.decibel.com/cart#!checkout/billingSection and had fragmenting set up, you could segment by checkout/billingSection. |
URL query | If a property uses query strings, you can segment by them here. For example, in www.decibel.com/blog?post=17, you could segment by post=17. |
Wait time |
Average time taken before visitors are able to interact with the page before fully rendering |
Traffic
Filter | Description |
---|---|
Channel | The channel the visitor came to the property from, such as Google or Facebook. |
IP Address | The IP address from which the visitor came to the property. |
Referer | The website the visitor arrived from, such as a Google search result or a Medium article. |
UTM campaign | The UTM campaign code from which a visitor arrived on the property. |
UTM medium | The UTM medium code from which a visitor arrived on the property. |
UTM source | The UTM source from which a visitor arrived on the property. |
Visitor
Filter | Description |
---|---|
Browser | The visitor's browser, such as Google Chrome or Mozilla Firefox. |
Country | The country that the visitor browsed to the property from. |
Device type | The device used by the visitor, such as desktop, tablet, or mobile phone. |
Language | The language that the visitor's browser is set to. |
Operating system | The operating system of the visitor's device, such as iOS 15, macOS Catalina, or Windows 10. |
Screen resolution | The screen resolution of the visitor's device screen. Both the screen width and height can be configured. |
Status | The lead status of a visitor. Note: This can be configured using tracked events. |
Time of visit | The day and time the visitor came to the property. |
Viewport size | The size of the visitor's viewport when viewing the site (i.e. how large the part of the browser that shows the page is). Both the screen width and height can be configured. |
Visitor count | The number of times a visitor has visited the site. |
Visitor type | The type of visitor. |
Custom
You can use custom dimensions as segment filters and search for sessions matching custom dimension data, such as order IDs.
The names of all custom dimensions used as segment filters are listed on the left. The options available for each filter depend on the Type chosen when creating your custom dimension.
Segment filter options
Option | Description |
---|---|
one of | Refers to one of the following selected. The Please select ... box below this will allow you to search for specific pages or browsers, and you can select one or multiple of these. By selecting one of and a number of pages, this would mean that the visitor only had to reach one of the pages selected to meet this criteria. |
all of | Similar to above, but all of the selected. If you were to add two pages into the Please select ... box, then the visitor will have had to view all of the pages that you have selected to meet this criteria. |
not any of | Not any of the selected. Again, if you add two pages into this text box, then the visitor will have had to not view either of these pages to meet the criteria. |
matches regex | Here you can use a regular expression (regex) to define the criteria, and if the visitor matches, they will be part of the segment. For example, you could use a wildcard statement (.*) when using custom dimensions to search for any session with that custom dimension present. |
does not match regex | Similar to above. The visitor can create a regex statement and if the session doesn't match it (for example, by not having the custom dimension present), they will not meet the criteria. |
contains | A simple contain criteria. For example, if you wanted to see visitors who have viewed your company's blog, you could simply enter "blog" into the text box and all users who viewed a URL containing "blog" will match this criteria. |
does not contain | Similar to above, but must not contain what is input into the text box. For example, if you were to enter "blog" in the text box, any sessions where the user visited a URL containing "blog" means they would not meet the criteria, whereas if they did not visit a URL containing "blog", they would meet the criteria. |
any | Removes the text/search option and simply references "any" of the criteria. For example, in the Form abandoned filter in the Form tab, selecting any will mean any form abandoned. |
none | Similar to above. Removes the text/search option and simply references "none". Using Form abandoned as an example again, selecting none will mean no forms were abandoned. |