Node Stats
Track user flow across journey nodes with version-specific stats to evaluate performance, drop-offs, and conversion impact
Overview
The Node Stats tab helps you track users' progress through each step of a journey. For every node on the canvas, you can view performance metrics such as the number of users who entered, where they dropped off, or whether they completed a goal.
Each node is labeled with a unique ID visible on the top-right corner of the node block. This makes it easier to reference and interpret stats in context.
You can select a specific date range from the calendar and view granular stats for each node type – Entry, Segment, Engage, or Force Exit.
If your journey has multiple versions, use the version dropdown on the Node Stats tab to analyze each version independently. The stats shown reflect only those users who entered and moved through the selected version's structure, logic, and timing. This ensures the insights remain accurate, especially when versions differ in entry criteria, delays, goals, or node sequences. Viewing stats version-wise, you can meaningfully compare user movement, drop-offs, and conversion outcomes for each version.
Node Stats
Entry Node
The Entry node is the starting point of every journey and defines which users are eligible to enter. Each journey version can have only one Entry node, which must always be a Segment node.
Entry criteria, such as segment conditions or trigger logic, may differ depending on the version, resulting in different sets of qualified users across versions.
When analyzing the Node Stats, the Entry node provides insight into the number of users who met the entry criteria, the number who actually entered, and the number who were included in the control group. These stats also help compare the effectiveness of entry criteria across versions and identify if changes in qualification logic impacted journey inflow.
Entry Node Stats
| Metric | Description |
|---|---|
| Qualified | The total number of users who qualified for the journey based on entry conditions. This is shown only on the Entry node and may vary by version.. |
| Entered Journey | The number of users who entered the journey flow after qualifying. These users progress through node connectors, such as Yes or No. |
| Control Group | The number of users randomly held back as part of a control group. These users do not receive journey campaigns, which allow you to measure uplift by comparing them against the treated cohort. |
Segment Node
The Segment node evaluates users based on behavioral or profile conditions. It acts as a decision point that branches the journey based on whether users match defined segment criteria. Segment nodes can be used at any point in the journey, including as the entry node.
In the case of multiple journey versions, the Node Stats tab reflects segment-level performance only for the currently selected version. Segment definitions may evolve across versions, affecting the number of users who qualify at that node or proceed forward. This allows you to assess how changes in segmentation (for example, segment criteria or order in the flow) impact the user movement, conversion, and drop-offs.
Segment node
| Metric | Description |
|---|---|
| Entered Node | The total number of users who entered the node. It includes all users from Moved Forward, Waiting, Goal Met, and Journey Timeout. |
| Moved forward | Users who have progressed via node connectors, such as Yes, No, or Node Timeout. |
| Waiting users | The users waiting at a node to qualify. The users may wait for either of two reasons:
|
| Goal Met | These users have performed the intended goal, such as viewing a movie or purchasing a product.
|
| Journey timeout exits | These are the users who exited the Journey after the time duration set for the Journey, that is, Journey Timeout is complete. |
Engagement Node
The Engage node represents the campaign delivery points within a journey, where users receive messages via channels such as Push, SMS, Email, or WhatsApp. These nodes are critical for driving user actions, and the stats captured here help you assess how effectively your messages are reaching and engaging users.
In the case of multiple journey versions, the Engage nodes may vary in their content, timing, or conditions across versions.
Engage Node
| Stat | Description |
|---|---|
| Entered Node | The total number of users who entered the node. It includes the sum of all the users from Moved Forward, Waiting Users, Goal Met, and Journey Timeout. |
| Moved Forward | Users who moved forward via node connectors, such as Sent, Viewed, Clicked, Failed, and Unreachable. Unreachable refers to profiles that lack identity (for example, email, phone, or device token is unavailable). |
| Waiting Users | Users who are delayed in progressing. Two possible reasons:
|
| Goal Met | Users who fulfilled the journey goal condition.
|
| Journey Timeout Exits | Users who exited the journey due to reaching the overall journey timeout duration. In the case of multiple journey versions, users can exit an Engage node for the following reasons:
|
You can view the campaign-level stats for every node. Click the Engage node to open the campaign-level stats.
Unique Users Converted
If a user enters the journey and performs the conversation event twice, only one conversation event for that unique user is counted.
Force Exit Node
The Force Exit node is used to remove users from the journey at a specific point manually. This node tracks only the number of users who were explicitly exited at that point in the journey flow.
Force Exit Node
Updated 1 day ago