There are different types of segment conditions available:
- Segments
- Goals
- User actions
- Session attributes
- Integrations
- *Product Analytics (BETA)
- *Page load metrics
- Frustration
*Note that Product Analytics, Page load metrics conditions are dependent on your plan. If you don't have these available, but would like to, please contact your Customer Success Manager for more information.
Overview
When you create a segment you can combine as many segments and groups of conditions as you like, but each segment is limited to a max 72 goals.
You can choose an existing Segment as a condition and combine it with other conditions or segment conditions.
Ex: Users who "match" "Returning visitors" AND Users who "match" "Sessions with transactions"
Default segments
Your Contentsquare project comes equipped with the default segments shown in the image below You cannot edit them but you can combine them with other segments and groups of conditions.
| All users | Includes all users visiting the site |
| New Users | A user is defined as new if it is the first time the user's browser and Contentsquare's cookie is seen on the site. If the cookie expires or is deleted, the next session from that user will be considered as a new user. |
| Returning Users | Users who are returning to the site, who start a session, and who already have a valid Contentsquare cookie. |
| Bots and spiders | Sessions that Contentsquare automatically filter out in the backend as sessions coming from Bot traffic. |
| Sessions with transactions | Sessions where users have completed an e-commerce transaction. If your site is not an e-commerce site, this segment will show 0% traffic. |
| Sessions without transactions | Sessions where users have not completed an e-commerce transaction. If your site is not an e-commerce site, this segment will show 100% traffic, essentially the same as the "All users" segment. |
| Non-bounce sessions | Sessions where users have viewed more than one page of your site. "Bounce" is defined as users leaving your site after viewing only one page of your site. |
| Bounce sessions | Sessions where the user left the site after only a single page view. "Bounce" is defined as users leaving your site after viewing only one page of your site. |
Goals
You can choose a Goal as a segment condition to group users who have achieved/not achieved a navigation behavior.
Ex: Users who “have" achieved the goal “Reached cart”
The Goal conditions correspond to all the goals created in the Goals feature.
User actions
You can choose a User action as a segment condition to group users who viewed, hovered, bounced, clicked, hesitated, and more on specific pages and zones.
Ex: "Page viewed" Users have viewed "My account: Login/Register " page "2" times
|
Bounce on Page |
Users who have bounced on a selected page |
|
Exit page |
Users who ended their session on a specific page. Use the page builder to define the exit page based on an existing mapping or by creating your page on the fly. |
|
Click recurrence on a zone |
Users who clicked a certain number of times on a specific zone |
|
Clicked Element (available based on your plan. Please contact your CSM for activation details) |
A button or a link text that users have or have not clicked on. Use Clicked element when:
|
|
Exit zone (last hovered) |
Users who last hovered a selected zone before leaving the website— the zone where the mouse movement was detected last when the session ended |
|
Hesitation time on a zone (in seconds) |
Users who hesitated a defined amount of time before clicking on a specific zone. Define the hesitation time in seconds. |
|
Hover time on zone (in seconds) |
Users who hovered a specific zone for a certain amount of time. Define the hover time in seconds |
|
Landing page |
Users who have started their navigation on a specific page. Use the page builder to define the landing page based on an existing mapping or by creating your page on the fly. |
|
Number of Pageviews |
Users with a specific number of pages viewed during a session. The condition can be set to a maximum, minimum or exact number of pages. For example, defining the number of pages viewed as 'more than 2' means that the users have seen at least 3 pages during their session. |
|
Viewed Page |
Users who viewed a selected page. Use the page builder to define the page based on an existing mapping or by creating your page on the fly. This condition also allows you to define the position in which the page was viewed. For example, defining the position as “1” means the page is viewed as a landing page. |
|
Scroll rate of a Page |
Users who scrolled exactly/more than/less than/ between a defined % of the selected page |
|
Time before first click on a zone |
Users who clicked on a specific zone exactly/more than/less than/ between a defined number of seconds after loading the page |
|
Time spent on a Page |
Users who spent exactly/ more than/ less than/ between a defined amount of time on the selected page |
|
Zone clicked |
Users who clicked or did not click on the selected zone within a session. Use Zone clicked when:
|
|
Zone hovered |
Users who hovered (mouse movement) on the selected zone within a session. |
|
Page event (available in Experience Monitoring) |
Users who achieved a custom page event, triggered during a session on a specific page. |
|
Same Pageview |
Enables you to create segments based on in-page events that occurred on the same pageview. |
|
Errors (available in Experience Monitoring) |
Users who did/did not experience an error on any page, or a specific page (or page group). |
|
Text seen (available in Experience Monitoring) |
Users have seen a specific text string, such as text based messages or errors. Learn more about Text Search. |
Session attributes
You can choose a Session attribute as a segment condition to group users who share browsing characteristics.
Ex: "Viewed Page" Users have viewed "Account login" page "2" times
| Browser | Users who used a specific browser or browser version. |
| Browser size | Sessions focused on the size of the browser window, by width or height (pixel). |
| Custom variable (Cvar) |
Enables you to create conditions for the values and keys of personalized variables defined for users, pages or sessions. Cvars are case sensitive, Ex: "UX - New Design" ≠ "UX - new design". |
| Dynamic variable (Dvar) |
Enables you to create conditions for the values and keys of personalized variables defined for users, pages or sessions. Useful for A/B test variants. Dvars are case sensitive, Ex: "New Banner" ≠ "new banner". |
| E-commerce transaction |
Users who completed a transaction. You can define a minimum, maximum or exact transaction amount. |
| Geolocation | Users in a specific continent, country or city. |
| Language | Users whose browser language is or is not on a specified list of languages. |
| New/Returning | Shows all sessions from users who have not been tracked by Contentsquare based on cookies in the past 13 months. |
|
Number of sessions |
Users who had a specific number of sessions on your website. The condition can be set to a maximum, minimum or exact number of sessions. |
| Operating system | Users who used a specific operating system and the operating system version. |
|
Referring Page |
Users who landed on the website using a specific referral URL. |
|
Screen resolution |
Users using screens with a specific resolution. |
| Session duration | Users with a specific minimum, maximum or exact session duration expressed in minutes. |
| User ID (Contentsquare) | Session relating to a Contentsquare User ID, a unique identifier that Contentsquare assigns to all users. Only one ID can be provided with the option "is" or "is not" . |
| Bots and Spiders | Enables you to analyze the bot traffic by filtering the sessions that "match" "Bots and spiders" OR "do not match" "Bots and spiders". |
Integrations
You can choose a segment from an integration you have implemented with Contentsquare.
Once you select your Integration condition for your segment, you can select a page key and enter operators. Then, you can add more conditions to your segment.
Ex:
Product Analytics (BETA)
Note, Product Analytics conditions are only available if you use Product Analytics.
You can leverage Product Analytics segments to:
- See how the behavior compares between one off purchasers vs. users who purchased again later.
- Analyze how Zoning Analysis compares between users who left and never came back vs. those who did come back later and transacted.
| Returned later in a session | Sessions of users who returned in a subsequent session* |
| Did not return later in a session | Sessions of users who didn't return in a subsequent session* |
|
Returned in a later session but did not transact |
Sessions of users who returned and transacted in subsequent sessions* |
|
Returned in a later session and transacted |
Sessions of users who returned and transacted in subsequent sessions* |
|
Returned in a later session but did not transact |
Sessions of users who returned in a subsequent session* but without completing any transaction |
|
Transacted, and transacted again in a later session |
Sessions of users with a transaction who transacted again in a subsequent session* |
|
Transacted, but did not transact again in a later session |
Sessions of users with a transaction who haven't transacted again since |
* subsequent sessions are sessions that have happened after the initial session.
Page load metrics
Note, Page load metrics are only available with Experience Monitoring enabled on your plan.
You can choose Page load metrics as a segment condition to group sessions where the page experience meets (or does not meet) the below page load metrics, to further analyze the impact on user experience and/or your site's performance. See all the Page load metric descriptions here.
| LCP (Largest Contentful Paint) | Sessions of users who experienced a LCP of more of less than a number of seconds on any, or selected, page or page group. |
| CLS (Cumulative Layout Shift) | Sessions of users who experienced a CLS of more, less or between a total sum of layout shifts on any, or selected, page or page group. |
| INP (Interaction Next Pain) | Sessions of users who experienced an INP of more, less or between a number of milliseconds on any, or selected, page or page group. |
| FID (First Input Delay) | Sessions of users who experienced a FID of more, less or between a number of milliseconds on any, or selected, page or page group. |
| FCP (First Contentful Paint) | Sessions of users who experienced a FCP of more, less or between a number of seconds on any, or selected, page or page group. |
| TTFB (Time to First Byte) | Sessions of users who experienced a TTFB of more, less or between a number of milliseconds on any, or selected, page or page group. |
Frustration
You can choose Frustration conditions to further analyze the impact of individual friction indicators on your site's experience, conversion and revenue. Learn more about Frustration score and each of the friction indicators.
| Frustration Score | Sessions where the Frustration score met a high, medium, or low level (or your own custom score). |
| Rage click | Sessions where Rage click was/wasn't experienced on any page, or a specific page/page group or zone. |
| Element - multiple clicks | Sessions where multiple element clicks were/weren't experienced on any page, or a specific page/page group or zone. |
| Button - multiple clicks | Sessions where multiple button clicks were/weren't experienced on any page, or a specific page/page group or zone. |
| Field - multiple clicks | Sessions where multiple field clicks were/weren't experienced on any page, or a specific page/page group or zone. |
| Excessive hover | Sessions where excessive hover was/wasn't experienced on any page, or a specific page/page group or zone. |
| Page looping | Sessions where page looping was/wasn't experienced on any page. |
| Page not consumed | Sessions where Page not consumed was/wasn't experienced on any page. |
| Low activity | Sessions where Low activity was/wasn't experienced on any, or a specific page/page group. |
How segments define New vs. Returning users
After installing the Contentsquare Tag, the ratio between New vs. Returning users will be heavily skewed towards "New users" until the cookie has more time to capture "Returning users".
"New users" are users who have not been tracked by Contentsquare based on cookies in the past 13 months.
"Returning users" are those that start a session and already have a valid Contentsquare cookie.
Here are some examples:
- If a user browses with Safari, cookies will auto delete after 7 days, contributing to a higher percentage of "New users" than is real.
- If a user deletes their own cookies on any browser this will also contribute to a higher percentage of "New users" than is real.
- If a user browses with Chrome but doesn’t clear their cookies and doesn’t return within 13 months, they will be counted as a new user if they return in month 14.
How to define your segments using Cvars
Using Custom variables enables you to create conditions for the values and keys of personalized variables defined for users, pages or sessions.
- Page: If a custom variable is defined on a page, Contentsquare checks the variable's value across all pageviews in the session. If a visitor's status changes, they will be included in multiple segments.
Example: If a visitor logs in during the session, they will belong to both the "not subscribed" and "subscribed" segments.
- Session: When a custom variable is defined on a visit, Contentsquare retains the value from the last pageview.
Example: If the visitor is logged in on the last page viewed, they will exclusively be part of the "subscribed visitors" segment, even if they were not logged in at the session's start.
- User: If the custom variable is defined on a visit, Contentsquare keeps the value from the last pageview of the visitor's last session.
Example: If the visitor is logged in on the last page viewed, they will be included in the "subscribed visitors" segment.
Note! The definition of the "last session" relies on one's cookies.
Segmentation limits
| Maximum number of conditions | 225 |
| Maximum number of integration segments | 100 |
| Maximum number of conditions in a page* | 100 |
Maximum number of matches regex or not regex operators in a page
|
32 |
|
Maximum number of |
50 |
| Maximum number of goals | 72 |
| Maximum number of matches_regex (regex operator used in a browser, operating system or error condition) | 5 |
Maximum number of | symbols (regex alterations a|b used in a browser, operating system or error condition) |
15 |
| Maximum number of Text seen conditions (text seen conditions are part of the Text search feature included in Experience Monitoring) |
4 |
* Number of page conditions refers to the number of page conditions defined from the mapping module and use in a segment as total, which is limited to 100.
For example:
Segment A:
Page viewed= PageGroup1 (path = "/home', prefix="contentsquare.com", cvar regex = "hello.*")
Number of page conditions = 3
Segment B: Page viewed=PageGroup1 (path = "/home", prefix="contentsquare.com", cvar regex = "hello.*") OR Landing Page=PageGroup2 (path = "/", prefix="contentsquare.com", cvar startsWith= "product")
Number of page condition = 6
Segment C: Segment A and Segment B
Number of page conditions = 6