Skip to main content
In MoEngage, user count can be analyzed on two different pages - The analytics page and the Segmentation page. The Segmentation page provides user count and sample users for a segment and Analytics Pages (Behavior, Funnel, etc) provide, event count, event frequency, revenue, retention & funnel information along with the unique user count.

​
Behavior & Segmentation Users

To analyze users on Behavior Page, select Plot For as Total Users. This option shows unique users for the selected granularity in the line/area chart or overall unique users in the bar chart. Analysis01.gif Whereas the Segmentation page shows the overall unique user count. Analysis02.gif

​
User Merging

A few times these two user counts from the segmentation page and behavior page do not match. This may happen due to user merging. In MoEngage engagement Module, the user who is coming from different devices is merged when the user logs in. User Merging is explained in detail here. The user merging is available in MoEngage Analytics Module as well. However, it is not enabled by default. Hence there are some leftover anonymous users present in the system. A normal person may have 2 kinds of events in analytics when the user was anonymous and when the user was logged in and hence identified as two different users. To overcome this scenario, you can enable user merging. This will help you to merge the anonymous user IDs with registered user IDs and show those uses as One. To enable user merging follow the path: Settings -> General Settings -> Analytics Settings -> Enable User Merging Screenshot

​
Funnel and Segmentation Users

There can be a difference in funnel user count and segmentation user count. This is primarily due to how funnel and segmentation work. The funnel considers the order of the event. For a user funnel of events E1 and E2, the final number is users who have done event E1 and after that E2. Users who have performed E2 before E1 are not considered. Segmentation does not consider the order of the event. For a user segment of events E1 and E2, the final number is users who have done both events, E1 and E2. It doesn’t matter which is the first and which is the second event.

​
First-Time Event Filters

When you filter users with the for the first time operator, Behavior and Segmentation can return different user counts for the same event and date range. This is expected behavior because each page checks a different event history:
  • Segmentation checks whether the user’s first-ever occurrence of the event falls inside the selected date range. Users who performed the event before the start of the range are excluded. The check covers only the events data retention period of your workspace. For more information, refer to Filters in Segmentation.
  • Behavior looks for each user’s first occurrence of the event within the selected date range. Occurrences before the start of the range are not checked.
As a result, Segmentation returns an equal or lower count than Behavior for the same for the first time condition. For example, a user who viewed a product in May and again on June 3 qualifies for “Viewed Product for the first time between June 1 and June 7” in Behavior, but not in Segmentation.