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.

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.

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.

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	Users who are delayed in progressing. Two possible reasons: Before Node: Delay from a previous node. At Node: Users who have reached the node but cannot proceed further due to the node configuration or execution conditions. This can occur in the following cases: Path not defined: The user does not qualify for any configured path from the node. For example, if the Failed path is not connected, such users remain in the At Node state as no next step is defined. Waiting for node execution: A valid path exists, but the node has not yet processed or routed the user. This can happen due to scheduling or node behavior. For example, if a campaign is configured to send at a specific time (for example, 2:47 PM) and the user reaches the node earlier (for example, 2:00 PM), the user remains at the node until execution. Valid path exists and is waiting for execution. In such cases, users may also appear at the node in journeys with PBS nodes due to evaluation timing. For example, if the first PBS node is the entry node, users who enter the journey before midnight (when the PBS segment is evaluated) may remain at the node temporarily until the next evaluation.
Goal Met	Users who fulfilled the journey goal condition. Before Node: Goal achieved while waiting. At Node: Users currently at the node who have already met the journey goal condition.
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.

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: Before Node: Delay from a previous node or users marked as Unreachable (if Unreachable path is not connected). At Node: Users at this node without a defined outcome. For example, if the Failed connector is not connected, users who do not qualify for any path from the node are retained in the At Node state, as the next step is not defined for them..
Goal Met	Users who fulfilled the journey goal condition. Before Node: Goal achieved while waiting, but did not receive the following message. At Node: Users currently at the node who have met the goal. If the Failed connector is not connected, users who do not qualify for any path from the node are retained in the At Node state, as the next step is not defined for them.
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: Journey Timeout: The user did not take the expected action within the defined node delay window. Version Change: In the case of multiple journey versions, users may be forced to exit from older versions when a new version is published and the older version is stopped. The older journey version was stopped while the user was still in progress. These users are automatically exited when a new version is published and takes over.

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.