Experience Analytics Mobile - Segment Conditions

In this article, you will find definitions for every condition available in the Segments module. 

There are different types of conditions available in the segment creation panel: existing goals, existing segments, session attributes, and user actions. 

Note: You can combine all types of conditions when creating a new segment.

Segments  

In the segment creation panel, you can select an existing segment and combine it with other conditions to create a new segment.

Choose if you want the new segment’s visitors to “match” or “do not match” the condition in the existing segment.

Goals 

You can choose a goal as your new segment’s condition. Goals correspond to users who performed a specific action on your app. For example, users who “have achieved” the goal “Reached cart”.  

Note: Goals in the segment creation panel correspond to all the goals created in the Goals module. 

Choose a goal in the drop-down list. Decide whether your visitors “have achieved” or “have not achieved” the selected goal. 

User actions

You can combine user actions with other available conditions.

Note: you can combine up to nine (9) user actions within one segment. 

A visitor action can be: 

Bounce on screen: users who have bounced on a selected screen. 

Exit screen (by goal): users who ended/didn't end their session on a specific screen. 

Number of screens viewed: users with a specific number of screen viewed during a session. The condition can be set to a maximum, minimum or exact number of pages.

Viewed screen: visitors who viewed a selected screen. This condition allows you to define the position in which the screen was viewed. For example, defining the position as “1” means the screen is viewed as a landing screen.

Time before first tap on a zone: Users who interact with a specific zone within a defined number of seconds after loading the page. 

Time spent on screen: users who spent a defined amount of time on the selected screen.

Zone tapped/not tapped: visitors who tapped or not tapped on the selected zone within a session. 

Session attributes

App version: Select the version of your app and an expression between "exactly", "more/less than" or "equals".(Available for CS Growth and Enterprise plans only)

Custom Variables: Enables you to customize your segmentation further based on certain attributes. WIth Custom variables (CVARs), you can create conditions for the values and keys defined for personalized variables. For example, logged in vs logged out attributes.

Device manufacturer & model: choose the device model (Samsung, Google, Xiaomi, etc.) and an expression between "any model" or "any of."(Available for CS Growth and Enterprise plans only)

Dynamic variable: Enables you to create conditions for the values and keys of personalized variables defined for users, screens or sessions. Dynamic variables are sent at the session level (not with each screenview) and are useful for AB test variants.

E-commerce transaction: users with transaction. You can define a minimum, maximum or exact transaction amount.

Language: users whose browser language is or is not on a specified list of languages.

New/Returning users: select users who either visited your app for the first time (new users) or who came back at least for the second time (returning users).

Network connection type: choose the network type (2G, 3G, 4G, WIFI, etc.)(Available for CS Growth and Enterprise plans only)

Number of sessions: users who had a specific number of sessions on your app. The condition can be set to a maximum, minimum or exact number of visits.

OS version: users who used a specific operating system version.(Available for CS Growth and Enterprise plans only)

Session duration: users with a specific minimum, maximum or exact session duration expressed in minutes.

Product Analytics (beta)

(These segments are only available if you use Product Analytics (Heap powered by Contentsquare)

You can choose Product Analytics segments.

* subsequent sessions are sessions that have happened after the initial session.

New vs. returning users

After installing the Contentsquare SDK, the ratio between New vs. Returning users will be heavily skewed towards "New users" until enough time goes by to capture "Returning users".

A user is defined as new if it is the first time the user uses the App with the SDK included on their device. If the user uninstall and reinstalls the app or opts-out and opts-in again, the next session from that user will be considered as a new user. "Returning users" are those that start a session and are already included in tracking (and opted-in).

Here are some examples:

• When the SDK is added to the App for the first time, all users using this App version will be considered as new users for their first tracked session.
• If a user updates the app and the Contentsquare SDK is included in the app only from this app version, this user will be considered as a "New users".
• If a user deletes the app from the device and installs it again, the user will be considered as a new user.
• If a user opts-out from tracking in the app then opts-in again in a later session, the user will be considered as a new user.