Overview
A segment is a group of users defined by specific properties or values. Segments are used to send campaigns or to analyze specific information or behavioral traits of users.
MoEngage dashboard enables growth teams to create multiple kinds of segments. MoEngage has the following types of segments:
- Static Segments
- Dynamic Segments
- Custom Segments
- Live Segments
Static Segment
Static segments are fixed groups of users and used as a list of users.
Dynamic Segment
Dynamic segments are groups of users created using rules and criteria based on user attributes or properties, events or event properties, or a combination of attributes and events. The rules or criteria are executed on the existing data to provide a group of users.
Custom Segment
Custom segment are lists or rules or definitions. Custom segment is primarily a segment having a name that is used easily anywhere.
A custom segment is static or dynamic or a combination of the two. You can:
- Add and remove users in a static custom segment.
- Modify the rules or criteria of a dynamic custom segment.
Live Segments
Live segments are segments available all the time and are calculated very frequently. Live segments are primarily used in Event-triggered, In-App, Web Personalization, and On-Site Messaging campaigns.
In Event-triggered, In-App, Web Personalization, and On-Site Messaging campaigns, individual users receive the campaign based on a trigger event or qualifying action. The uncertainity of a user executing the trigger action or visiting the app or website, the following statements are valid:
- The segments are executed frequently and the results stored or updated. These can be called precomputed segments.
- When the user performs the trigger action or qualifying action, the subscription of a user for the segment is verified in the precomputed segmen, and the campaigns are sent accordingly.
Live Segment SLA
The following table describes the Service Level Agreement (SLA) for Live Segments:
| SLA Type | SLA Time | Description |
|---|---|---|
| Data Availability | 45 Mins |
Live segments processes the data available in the MoEngage data warehouse. Data processing SLA is 45 Mins and the actions or events, action properties, or user property has not reached the data warehouse is not considered for the live segment. |
| Processing | 10 Million users per hour |
Live segments creation and availablity takes time. The SLA for Live Segment creation is 10 million users per hour. Meaning that it takes one hour to process 10 million users and make them available as a live segment. |
| Refresh Frequency | 3 Hour / 6 Hour |
Live Segments for event-triggered campaigns are re-calculated and updated every 3 hours. |
User Attribute SLA
If you are using only user attributes for your segment definition in event-triggered campaigns or user attribute condition evaluation in the Flows campaign. The following table describes the Service Level Agreements:
| SLA Type | SLA Time | Description |
|---|---|---|
| Data Availability | 15 Mins | User properties are available for event-triggered and Flows campaigns within 15 minutes of property set or change. |
| Processing | Real-time |
A few milliseconds is required to process segments that are only defined using user properties. |
| Refresh Frequency | Not Required |
For user property only live segments, there is no need for segment storage as the segment execution is performed on live data. |
INFORMATION
|
Analysis of Segments
The analysis of segments is performed based on server time for all of the time-bound analyses.
For example, a user who has executed App Open in the last 3 days. For this example, the last 3 days are calculated using server time.
For more information about server time, refer to Event Time and Server Time.
Examples
Dynamic Segments using User Properties
User properties are attributes of the user in the MoEngage system such as email, name, last location, etc. The value of user properties gets updated almost in real-time and the latest values are available for calculation.
Dynamic Segments using Events
Events are activities done by users such as App Open, Product Purchase, etc. These events also have event attributes such as app version, platform name, product category, product price, etc. Event attributes are tracked with events and are specific to the selected event.