Skip to main content

Overview

MoEngage Flows provides an intuitive way to analyze user interactions and understand the performance of the flow built. We represent the performance using Trips and a Trip basically represents a unique user journey, beginning with their entry into a flow after fulfilling certain conditions and including their interactions with campaigns and possible conversions along the way. The analytics of user trip data is crucial for effective user engagement and flow performance optimization. The explained metrics, including Active Trips, Engaged Trips, Converted Trips, Drop-offs, and Revenue among others, offer granular insights into user behaviour and interactions. You can also visualize and filter trip data using the Canvas and Detailed Stats views. Additionally, it sheds light on the performance analysis of individual channels and campaigns, helping you to fine-tune your customer engagement strategies.
  • This is an Early Access feature. To enable it for your account, please contact your MoEngage Customer Success Manager (CSM) or the Support team.
  • All metrics are calculated and displayed in the App Timezone. To find your current app timezone value, refer to the Workspace Settings.
  • This feature applies only to flows created after it is enabled; flows created prior to enablement will continue to show stats in GMT.

Why Trips?

While tracking the total user entries is an alternative, we identify that auxiliary metrics such as unique user entries and unique conversions are to be tracked and reported every time to remove the ambiguity among the metrics. As a Trip uniquely identifies each instance a user might enter a flow over the lifetime of a user, it provides an unambiguous concept that can be extended to every metric you would want to track to analyze the performance of your flow.

Definition of Metrics

In every flow, you can see the following top-level metrics:

Example

For a flow with action campaigns C1 and C2, User U1 enters the flow and receives both campaigns and converts with the configured conversion goal 2 times. Now, after the user exits the flow, the stats will be:
  • Total Trips: 1
  • Active Trips: 0
  • Engaged Trips: 1 (although the user received both campaigns, it will be treated as one trip)
  • Converted Trips: 1
  • Total Conversions:2
Now if User U2 enters the flow but because of some reason (such as personalization failure or not having an active device token) does not receive any of the campaigns but does perform the conversion event once. Now after the user exits the flow, the stats will be:
  • Total Trips: 2
  • Active Trips: 0
  • Engaged Trips: 1
  • Converted Trips: 1
  • Total Conversions:2
The engaged trip, converted trip, and total conversion do not change because the User U2 was not engaged from either of the flow action campaigns.

Canvas View

In addition to the overall stats at the top, you can also see the performance of each stage configured in the flow. By filtering for a defined time period, you can understand the behavior or stats of users who have entered the flow within that time. Flow canvas showing the entry rules, each stage's entered, current, drops and exits counts, and the branch and exit counts below the conditional split You can also view the stage level stats to know the number of users that have passed through, or are currently at, or have exited the flow from that stage.
Entered = Current + Drop off + Exits for any given stage.
When users move into a version from an earlier one, a badge appears in the top-right corner of each stage they entered directly. Hover over the badge to see how many users arrived there and which versions they came from. The stage’s Entered count also carries a second line showing the split, such as 0 + 2 (from V10, V6). The first number counts the users who reached the stage from the stage above it, and the second counts those who arrived from an earlier version. This explains a rise in a stage’s numbers that the entry stage does not account for. The versions named in the split are the ones the users came from, and they are not always the version immediately before the current one. Each time you publish and choose to move active users forward, the users in the version before that publish come with it, so a user can travel forward over several publishes. A stage can therefore show arrivals from more than one earlier version, as in the example above. Hovering the badge on a stage to see how many users entered it directly from an earlier version The following image shows that 2 users have exited the flow from the Has done event stage. When you hover the mouse over the stage, you will see a pop-up that shows the reason for each exit. 8.png
Users can exit from any stage in the flow due to reasons such as:
  • Passing through an exit stage in the flow path
  • Fulfilling the conditions in the exit criteria (for more information on adding exit criteria, refer to Global Exit Criteria)
  • Achieving the conversion goal defined in the flow
  • Moving to a new version of the flow, when you publish a new version and choose to move the active users into it
  • Dropping off due to reasons mentioned in the Definition of Metrics section.
In addition to analyzing the canvas view for all the user trips, you can analyze and compare the stats/behavior of users who have entered the flow within a defined time period. As shown in the previous image, You can filter the canvas view for the user trips that started within the selected date range.
In canvas view, when you filter for a time period, it shows data for all users who have entered the flow in the specified time period. The detailed stats show data of what has happened during that time period regardless of when the user entered the flow. For more information, refer here.
If you want to see the updated stats for the active trips, click the Refresh icon next to the date range filter to update both the overall and stage-level stats.

Conversion Uplift

Uplift is only shown in overall stats if the control group was enabled for at least a day during the filtered period. To know more about how uplift is calculated, click here.

Legends

The colors in the canvas represent the flow path and the decisions made to send campaigns to your customers. The following table describes the legends on the canvas:

Detailed Stats

You can open the detailed stats page for your flow by clicking the “Stats” tab adjacent to the “Flows” tab.
The detailed stats are shown for the last 90 days by default or since the current version’s published time, whichever is shorter. You can see the stats from the time the flow was published using the date range filter.

Flow Performance

The stats of the currently active version of the Flow are loaded in this section. You can see the stats of any specific version by selecting the version from the version selector as shown in the following image. You can choose the following in the version selector:
  • Specific Version: This section shows you the trends of User trips, Engaged Trips, and Converted trips over time for the selected Version. If the control group is enabled during the filtered time, the conversion uplift is also shown. Flow Performance.png
  • All Versions: The All Versions option loads the cumulative stats for all versions put together. The Flow Performance for All Versions has information about User Trips, Engaged Trips, and Converted Trips and Conversions over time. If the control group is enabled during the filtered time, the conversion uplift is also shown. Revenue performance is not available in the All Versions option, because each version might have a different revenue attribute or currency. The chart also shows when each version was published. Flow Performance.gif
While the default view is the overall period of the flow and the defined primary goal at the time when the flow is published, you can filter out the stats:
  • For a particular time period based on the dates.
  • Based on the conversion goals.
Are your control group trips more than the defined percentage, or is there a negative uplift? Refer to the uplift calculation and CG Allotment for more information.

Drop-Offs and Exits

This section has the following tabs:
  • Drops - This tab lists reasons for all drop-offs, an explanation for each drop-off reason, the total drop-offs due to this reason, and the percentage of all drop-offs. When you expand a drop-off reason, you will see the stage type and stage name from which users were dropped off. When you move active users to a new version, this tab also lists a Version migration failed reason, which counts the trips dropped because the cross-version migration did not complete, such as when no defined path existed for the user in the new version. Drops tab of the Drops and Exits Breakdown showing the Version migration failed reason expanded to the stage users dropped from
  • Exits - This tab lists reasons for all exits, an explanation for each exit reason, the total exits due to this reason, and the percentage of all exits. When you expand an exit reason, you will see the stage type and stage name from which users exited.
    This tab also shows Exit on conversion. You can see stats of users who exited the flow on achieving the conversion goal defined in the flow. When you move active users to a new version, this tab also lists a Version migration reason, which counts the trips that exited because of cross-version migration. Expand it to see the stage type and stage name each user left from. 9.png
Exits tab showing the Version migration reason expanded to the stage users left from
Version migration and Version migration failed are the same events that appear elsewhere as User Exited Flow reasons. Version migration is shown as Move to new version, and Version migration failed as Dropped off as the path was no longer defined. For more information, refer to Debug Flows.

Cross-Version Movement

When you select a specific version, a Cross-version movement table appears below the flow performance chart. Moved from names the version each group of users came from, and No. of users moved counts them. The table has its own date range, separate from the one on Flow performance, so changing the dates there does not change this table. Cross-version movement table showing the version users moved from and how many moved

Business Events

This section helps you analyze the flow performance for each Business Event instance. When you expand the Business Event, you can see the impact of each instance separately on a day level. For more information, refer to the Definition of Metrics. 2025-01-08_14-24-44 (1).gif

Channel & Campaign Performance

This section helps you analyze the aggregate performance of every channel used in the flow, together with the performance of each action campaign within it. MoEngage previously showed this as two separate sections, Engagement Trends and Campaign Stats.

Channel Performance

Select a channel from the tabs to see how it performed, or select All Channels to compare every channel used in the flow. You can view the data as a table, a line chart, or a bar chart, and switch the chart between CVR, CTR, and Delivery rate. Use Date Range and Tracking Goal to scope the view, and Compare With to set a second period to compare against. When you select a single channel, CVR and CTR for the tracking goal appear above the chart, and the chart plots that channel’s own metrics, such as attempts, messages sent successfully, conversions, and conversion events. When you select All Channels, the chart compares every channel in the flow on the metric you selected. In the table view, each row is a date, with columns for user entries, successful sends, delivered, opened, adjusted open, clicked, CTR, and conversions. Channel and Campaign Performance section showing the channel tabs, the Channel Performance chart with CVR, CTR and Delivery rate options, and the Campaign Performance table below it This section is also available when you select All Versions, which sums each metric across every version of the flow. Use it to judge the total cost and return of the flow without exporting each version and adding the numbers yourself. The All Versions view adds a Converted trips, Converted users, and Conversions column for each channel.
Changing the conversion goal is one of the reasons to create a new version, and MoEngage still sums the converted and revenue figures across versions when that happens. Where the event on the primary conversion goal differs between versions, MoEngage shows a callout on the All Versions view so that you know the total covers more than one definition.

Campaign Performance

This section lists the performance of all action campaigns configured in the flow. This can help you compare the individual campaigns across channels. If required, you can choose to filter the action campaigns of one particular channel to understand and compare the performance of similar campaigns.
You cannot add the metrics in each row of the Campaign Performance table and compare it with flow-level metrics because this table shows each campaign’s performance and thus will have overlapped attribution across campaigns. For example, the sum of unique conversions can be different from converted trips and conversions at the overall flow level. For more information, refer here.
The current flow version’s channel and campaign performance is shown by default. Use the version selector to view the performance of other versions of the flow.