Before we deep dive into segment creation, please ensure that you have read through, Users, User Attributes and User Profiles and have a robust understanding of related concepts.
Now that we understand the benefits and basic principles of segmenting your user base, let’s delve into how you can create segments in WebEngage, starting with a few core concepts.
The term rolling segments implies that the user base of any event (action) based segment is constantly updated to match the real-time actions of a user with the rules of segmentation set by you.
Simply put, the word rolling here implies that users roll in and out of segments as an when the rules of segmentation fall in line with their actions or current status.
Another way to look at this is that the time window is rolling in nature. As the days progress, the time window rolls over to the subsequent day maintaining the time frame defined by you.
Use-case: How rolling segments facilitate intuitive segmentation
Let’s say that you create a segment on December 1 which includes users who have not viewed items added to their cart over the last 30 days. Then, at the time of creation, the segment will include all those users who have not viewed their cart since November 1.
But as the month progresses, the set of users included within the segment will change. Hence, on December 20, the segment will include only those users who have not viewed their cart since November 20, and so on.
This plays an important role when setting up recurring campaigns to send messages based on the stages of your user lifecycle. This could include messages like reminders, offers to drive repeat purchases and so on.
Segments in WebEngage are never static. They are dynamic in the sense that WebEngage tracks your users’ actions in real-time. Users will get added/removed from the segments as and when their actions match/ don't match the rules of a particular segment.
Use-case: How dynamic segments facilitate contextual segmentation
Let's say that you have created a segment of premium users who have an RFM score of above 100. Then WebEngage will constantly track and update the set of users within this segment in real-time, depending on their RFM score.
So, if the RFM score of any of the users included in this segment falls below 100, then they will be excluded from the segment and vice versa.
Now that you have a good understanding of how all segments created in WebEngage are dynamic and rolling - let’s walk you through the creation experience.
How to access
Click the Plus icon at the top left of the List of Segments section to access the creation interface.
Segment creation is broken up into the following sections:
- A live preview of the segment to-be-created, placed on the right, as shown below.
- A field for naming your segment on the top
- The following sections help you define the rules of segmentation:
- User (details like last seen, location, acquisition source, etc.)
- Behavioural (events or actions performed or not performed by users)
- Technology (technological preferences like OS, Browser, Devices etc.)
Let's demonstrate a use-case to help you get acquainted with the workings of this section.
Use-case: Segmenting users to increase conversion rate
Let’s say that you run an online grocery store and want to engage all users based in Mumbai, India who have added products to their cart but have not made a purchase over the last 7 days.
Broadly, here’s what you’ll need to:
It’s as simple as that!
Creating segments in WebEngage is like building a house of Legos - all you need to do is select the right blocks and place them. After building the structure, if you don’t like the way it has turned out, you can always hit the reset button (at each step) to start afresh.
Now let’s deep dive into all the steps of segment creation.
The first step is to give your segment a unique name which will help you identify its purpose or properties. This can be edited anytime you like.
Let's walk you through the features and parameters nested under each section here, starting with User.
Before you proceed, we recommend that you browse through, Users for a clear understanding of these concepts and their application across your dashboard.
Coming back to User, the following parameters can be defined here:
- Visitor Type
- Last Seen
- Location (Geo Filtering)
- User Attribute Value
- First Acquisition Source
- User ID
- Channel Reachability
Let's walk you through each one:
Using this field you can filter users based on how frequently they interact with your mobile app/website.
The dropdown includes the following options:
No. of Sessions (can be defined by any of the following conditions; equal to, not equal to, one of, none of, less than, greater than, less than or equal to, greater than or equal to)
Here you can include users in your segment by the frequency of their interaction with your app and website. This can be done by specifying a date or time frame, in the past or future.
The following options are included here:
Last seen is after a specified period which could be;
last (enter value) minutes/hours/days/weeks/months/years
next (enter value) minutes/hours/days/weeks/months/years
Last seen is before a specified period which could be;
- any one of the fields specified above
Last seen is within a specified period which could be;
any one of the fields specified above
last (enter value) minutes/hours/days/weeks/months/years to last (enter value) minutes/hours/days/weeks/months/years
next (enter value) minutes/hours/days/weeks/months/years to next (enter value) minutes/hours/days/weeks/months/years
Last seen is present (will include users who have visited your app and/or website at least once in their lifetime)
Last seen is not present (will include users who exist in your database but have never interacted with your app and/or website. This means that the users were acquired offline and were added manually through a CSV upload to your WebEngage account.)
Using this field you can choose to include or exclude users in a segment by their location, making it possible for you to communicate contextually.
- A maximum of three locations can be added here.
- Multiple locations can be clubbed by the Inclusion/ Exclusion logic.
- This can be added by selecting Any (inclusion) or None (exclusion), from the drop-down placed on the top right.
So, if we were to club the locations with Any then it would lead to the creation of a segment which specifically includes users residing in the defined locations.
On the contrary, clubbing the locations with None would lead to the creation of a segment which does not include users residing in the specified locations.
The following parameters can be defined for each location:
Country < filtered by Region < further filtered by City
Here you can add one or multiple system attributes and custom attributes to the rules of segmentation.
- Each attribute can be defined by adding a value against it.
- Multiple attributes can be added by clicking the Plus icon on the left.
- All attributes can be clubbed using the AND logic or the OR logic.
Let's solve a short use-case to understand the workings of this section, better:
Use-case: Clubbing multiple user attributes to create a segment
Let's say that you run an international fashion e-commerce app and would like to segment users specifically based in Singapore to engage them with the latest fashion trends and collections of the region. You decide to extend your premium collection to loyal customers first, before making it available to your entire user base.
We'll use the following attributes to create the segment:
Country is equal to Singapore
Loyalty Reward Points is equal to or greater than 5000
Solution: Club attributes by the AND logic to create the segment
Since we would like to create a very niche segment of users to engage with our premium collection, we'll create a segment of users who are located in Singapore AND have 5000 or more Loyalty Reward Points.
On the contrary, if we club the user attributes by the OR logic, then it would broaden the segment's userbase by including users who are either located in Singapore OR have 5000 or more Loyalty Reward Points. While doing so is not useful for the use-case at hand, you can apply the OR logic to club attributes for several other cases which require you to include users based on any one of the related parameters.
The following system attributes are included in the dropdown here:
Hashed Phone (Number): At WebEngage, we extend the option of encrypting all critical user details to avoid any privacy breaches. Hence, using this attribute you can include the encrypted phone numbers to add specific users to your segment.
Hashed Email (Address): Similarly, using this attribute you can include encrypted email addresses to add specific users to your segment.
Last Seen (as discussed under Last Seen, above.)
(Please note that custom user attributes vary for each WebEngage account, making it impossible to list here)
Using this field you can choose to include only those users who have been acquired through a specific channel, landing page, referral source or a combination of these, as shown below.
Here too, you can choose to club the channels by the AND/OR logic - its implications have been explained under User Attribute.
Any Channel: Includes users acquired via any one of the channels listed henceforth. The scope of inclusion can further be refined by defining:
- Referral URL
- Landing Page URL
- You can choose to define multiple referral and landing page URLs as per your segmentation needs.
Direct: Includes users who directly entered your webpage's URL in the browser to visit it. All users for whom,
document.referrer is empty are considered to be acquired directly.
Email: Includes all users for whom the landing page URL contains the UTM parameter,
utm_medium where the value is
Organic Search: Includes all users for whom the referral URL contains one of the search engine's URL but does not contain paid campaign UTM parameters like
utm_medium equal to
GCLID query parameters (used for Adwords).
The following search engines are taken into consideration:
The scope of inclusion can further be refined by defining a Search Phrase or a keyword that the user must have typed into the search engine's search bar.
Display: Includes users for whom the landing page URL contains the UTM parameter,
utm_medium where the value is equal to
Social: Includes users for whom the referrer URL contains the domain of a social media platform like Facebook, Twitter, Google+, Pinterest, LinkedIn, Me2Day. OR The landing page URL contains the UTM parameter,
utm_medium where the value is equal to
social media and so on.
- The scope of inclusion can further be refined by defining a Social Network.
Referral: Includes users who visit your webpage from another domain. All users for whom,
document.referrer is not empty and does not match the landing page's domain are considered to acquired through referral.
- The scope of inclusion can further be refined by defining a Referral URL.
Campaign: Includes users for whom the landing page URL contains the any or a mix of the value specified against the following UTM parameters:
Campaign Name: Add the value that the UTM parameter,
utm_campaignmust contain in the landing page URL for a user.
Campaign Source: Add the value that the UTM parameter,
utm_sourcemust contain in the landing page URL for a user.
Campaign Medium: Add the value that the UTM parameter,
utm_mediummust contain in the landing page URL for a user.
Campaign Term: Add the value that the UTM parameter,
utm_termmust contain in the landing page URL for a user.
Campaign GCLID: Add the unique Google Ads tracking ID that the landing page URL must contain for a user.
Paid Search: Includes users for whom the landing page URL contains the UTM parameter,
utm_medium where the value is equal to
GCLID query parameters (used for Adwords). The scope of inclusion can further be refined by defining:
- Query value
Any parameters added against the fields, AppsFlyer, Adjust, Branch, Tune and Metrix are not applicable to web users as these are mobile specific attribution tools.
Since all mobile apps are downloaded through Google's Playstore or Apple's App Store, acquisition source attribution works differently than it does for websites.
All you need to do is integrate your mobile apps with any of the aforementioned platforms and connect your WebEngage account with it. In doing so, we will start gleaning acquisition source information for all users that download your app.
You can specify the following parameters to segement users (based on the info gleaned through the third-party attribution platform):
Campaign Name: Add the value that the UTM parameter,
utm_campaignmust contain in the page URL for a user prior to downloading your app.
Campaign Source: Add the value that the UTM parameter,
utm_sourcemust contain in the page URL for a user prior to downloading your app.
Here you can enter specific user IDs, prefixed by a condition, to create a very niche segment.
User IDs can be prefixed by any one of the following conditions:
- Equal to
- Not equal to
- One of
- None of
- Starts with
- Does not start with
- Ends with
- Does not end with
- Matches regex (regex is a sequence of characters that define a search pattern - used in several coding languages. Detailed read)
- Does not match regex
- Does not contain
Or, you could simply include users in your segment by specifying a condition wherein the User ID is empty or is not empty.
Please ensure that you have a broad understanding of Channel Reachability before proceeding. Doing so will help you understand this aspect of segmentation, better.
Using this feature, you can choose to include users is your segment based on channels they can (or cannot) be reached on.
As shown in the visual above, this section has two dropdowns - Reachability Criteria and Channel.
Dropdown 1: Reachability Criteria
The following options can be selected here:
Reachable on: By selecting this option, you can include users that can be reached on one or a combination of multiple channels listed in the second dropdown.
Not reachable on: By selecting this option, you can choose to include only those users that are not reachable on certain channels.
Let's help you understand the value proposition of creating a segment of users that are Not reachable on a particular channel with a use-case.
Use-case: App only business with a significant share of users that have disabled Push
Let's say that you are an app only business and rely heavily on push notifications to engage your users. But how do you communicate with users that have disabled push notifications on their devices?
Your next best options are Email and SMS.
But how do you identify the users that can be reached through either or both these channels? And identify which, amongst the two channels would be most effective?
Solution: Create a segment for users that are Not reachable on Push
Once this segment is created, you will be able to get a clear idea of the other channels that you can leverage to engage these users! Such details can be found under the segment's analysis section.
Now, let's solve a quick use-case to demonstrate how you can use this feature to create micro-segments for users that are Reachable on a particular channel.
Use-case: Creating a long-term engagement plan for app users
Let's assume that you are an online travel agency and operate through both, a website and an app. More than 40% of your bookings are made through your mobile app, making app engagement a top priority for your marketing/growth team. So, they come up with a two-step plan to engage all app users.
Step 1: Engage them with informational content about the locations they are visiting.
Step 2: Occasionally promote guided tours of popular historical areas and experiential activities offered by your partners, in the vicinity, they are currently in.
We'll use the following criteria to create this segment:
- Is Reachable on Push
Solution: Create a segment of users that are Reachable on Push and trigger contextual campaigns as per their geo-location
Once this segment is created, you will be able to create multiple journey campaigns for the segment that triggers informational content and offers everytime a user enters/exits a geo-fence pre-defined by you!
Dropdown 2: Channel
The following options can be selected here:
You can choose to include users within your segment based on their reachability criteria across several channels. All four channels can be combined by the OR logic in the drop-down itself. By doing so, you will be limiting the scope of inclusion to either of the following cases:
- Users that are Reachable on a channel.
- Users that are Reachable on either one of the selected channels.
- Users that are Not reachable on a channel.
- Users that are Not reachable on either one of the selected channels.
Must read: Events
Please ensure that you have a robust understanding of Events and Event Attributes before proceeding. Doing so will help you understand the workings of behavioral segmentation better.
Here you can include users in your segment by the events performed or not performed by them. Hence, Behavioral is divided into two conditions;
- Users who DID these Events
- Users who DID NOT do these Events
You can combine the conditions by the AND/OR logic. Which means that the rules of segmentation can be any one of the following:
- Users who have performed an event
- Users who have not performed an event
- Users who have performed event A and have not performed event B
- Users who have either performed event A or have not performed event B
Let's go over all the features of Behavioral in detail:
A drop-down including all the custom events, system events and campaign events being tracked for your account has been included under each condition. Select any one.
Event dropdown options
Please refer to this section for a list of all the system events and campaign events included in the dropdowns under both conditions.
(Please note that custom events vary for each WebEngage account, making it impossible to list here)
To add multiple events under a condition, click the Plus icon placed next to the second dropdown (as shown below). A maximum of three events can be added under each condition, clubbed by the AND logic or the OR logic.
Using the AND/OR Logic to combine events and the conditions
Please note, the logic you use to combine the events added under each condition and the conditions - need to be consistent. Which means you can either use the AND logic when combining the two or the OR logic.
Step 2: Defining the frequency/recency of the selected Event, under the condition: Users who DID these events
Using the second dropdown (below Add Filters) you can further define the context of an event by adding a time-bound parameter of how frequently or recently the event has been performed. This feature helps you create highly targeted segments, facilitating in-the-moment interactions.
While the parameters included in the dropdown here vary contextually as per the event, these parameters apply to all:
At least once
No. of occurrences (scope can further be refined by adding a value prefixed by; is equal to, does not equal to, less than, greater than, is less than or equal to, is greater than or equal to, between, not between)
Most recent event time (scope can further be refined by adding a date prefixed by; after, before, within. Or you could simply define the context as present, not present - leaving it up to us to check whether or not the event has been performed by each user recently, adding them to the segment accordingly.)
Least recent event time (scope can further be refined in the same manner as Most recent event time)
Click Add Filters to add an attribute to the event - this will add a dropdown to the screen, including a contextual list of all the attributes which can be added to the selected event.
Each drop-down includes a contextual list of the system attributes and custom attributes which can be added as filters to the selected event.
Event Attribute dropdown options
Please refer to this section for a list of all the system attributes included in the dropdowns under both conditions.
(Please note that custom attributes are exclusively tied to a custom event and will show up in the drop-down options accordingly, making it impossible to list here)
To add multiple attributes, click Add Filters again. Multiple filters can be clubbed by the AND logic or the OR logic - the implications of which have been explained above, under User Attribute.
Let's solve a practical use-case to understand the workings of this section, better.
Use-case: Segmenting users by two events with event attributes (applied to each)
Let's say that you run a grocery delivery app and want to individually engage users who have added products to their shopping cart, but have not made a purchase yet.
You decide to create a different engagement strategy for high-value users, whose cart value is $100 or higher by offering them a 5% discount. Since you're offering a discount, you decide to extend this offer specifically to users located in the vicinity of your warehouse in Sacramento, California.
- Assume the first event, products added to shopping cart to be; Product - Added to Cart
- The event attributes we'll need to add to it will be; Cart Value, Country, City
- And assume the second event, not made a purchase yet to be; Cart - Checkout Completed.
Now let's show you how to combine these events to create a segment:
Step 1: Add the event, Product - Added to Cart under Users who DID these Events
Step 2: Add event attribute 1, Cart Value, defined as; greater than $100
Step 3: Select AND logic for adding the next attribute
Step 4: Add event attribute 2, Country, defined as; equal to United States
Step 5: Select AND logic for adding the next attribute
Step 6: Add event attribute 3, City, defined as; equal to Sacramento
Step 7: Select AND logic to combine both the conditions; Users who DID these Events, Users who DID NOT do these Events
Step 8: Add event, Cart - Checkout Completed under Users who DID NOT do these Events
Step 9: Hit Save!
And there you have it - a segment updated in real-time for engaging users with discount coupons, located in a specific region, motivating them to complete the transaction.
Here you can choose to include only those users who use a particular operating system, making it easier for you to tailor campaigns with elements native to each OS (Android, iOS, and Web).
Use-case: Using OS as a segmentation parameter to create stylised campaigns
For example, rich mobile push notifications can only be seen on devices that use the recent versions of iOS and Android. Thus, when creating a segment for engaging users with rich push notifications, you can you specify the latest versions of iOS and Android devices under the rules of segmentation.
You can even combine multiple Operating Systems to include a broader set of users by adding parameters under each OS. All these parameters will be combined by the OR logic by default.
Here’s a list of the technical details you can add to the rules of segmentation under each OS:
App Installation Date
Total Time Spent (in seconds): Time spent on your mobile app throughout their entire lifetime
App Version Name
App Version Code
SDK Version (Refers to the WebEngage Mobile SDK version added by you to the platform. All user data is collected through it)
- All data points listed under Android (excluding Android ID, Manufacturer, Brand)
- Vendor ID
2.3.3. Web (Website)
Devices (Mobile, Desktop, Tablet)
Web Push Subscribe - Source URL (The page through which the user opted-in)
OS (Mac OS version, Windows, Linux etc.)
Browser (Chrome version, Safari version, Firefox version etc.)
Placed on the right, a real-time preview of the segment you're creating shows a top-level breakup of its users.
The following parameters are included in the preview:
Total Users: It indicates the total number of users included in the segment, further broken down by;
At WebEngage, we believe it’s essential to have a clear sight of the possibilities offered by each segment you create. Thus, this preview has been designed to help you develop segments which are practical in size, substantially differentiated and can be engaged via a channel.
What happens after you have built a segment?
Once you have reviewed details of the segment to-be-created - hit the Save button, placed on the top right.
Doing so will take you back to the List of Segments, showing your newly created segment at the top of the list.
Depending on the volume of data and parameters set by you, it may take us some time to brew the segment. In cases where this happens, you will see; In Progress, against the segment’s title on the homepage.
So, what will be the first segment you create in your account?
Updated 9 months ago