Journey performance evaluation
The journey data report includes overall journey data and node data.
Overall journey data
| Metric | Metric definition | Description |
|---|---|---|
| Unique Arrivals | Users who meet the trigger or selection conditions and arrive at the journey | |
| Entry Users | Users who successfully enter the journey | Entry Users = Unique Arrivals - eliminated by entry limits - eliminated by arrival control (behavior-triggered entry) |
| Exit Users | Users who have exited the journey | You can view the specific exit reasons and the number of users who exited. Exit reasons include:
|
| Planned | Users who flow into an action node and aren't filtered out by do-not-disturb control, an empty send ID, or a journey pause | |
| Attempted Push | Planned users, excluding users filtered out by channel delivery caps | Planned - Delivery Caps |
| Push Succeeded | Users for whom the push channel's send API was called and the message was sent successfully | When you filter to view version data, you can view the specific delivery of each node. |
| Push Failed | Users for whom the push channel's send API was called and returned an error | |
| Target Completion & conversion rate | Users who complete the conversion behavior within the specified window after entering the journey, and their proportion |
Node data
Click Node Data & Details to view nodes and their data performance. If your journey has multiple journey versions, you can switch versions in the upper-right corner.
The metrics of each node type are described below.
Entry Node
| Metric | Metric definition | Description |
|---|---|---|
| Unique Arrivals | Users who meet the trigger or selection conditions and arrive at the journey | |
| Entry Control | Users who meet the entry conditions but are filtered out by entry limits | Shown only when entry control is enabled |
| Timeout Control | Users who meet the entry conditions but arrive after the timeout | Shown only for behavior-triggered entry with timeout control enabled |
| Entry Users | Users who successfully enter the journey | Entry Users = Unique Arrivals - eliminated by entry limits - eliminated by arrival control (behavior-triggered entry) |
Decision Node
| Metric | Metric definition | Description |
|---|---|---|
| Node Inflow | Users who flow into the node | |
| Moved Forward | Users who meet the decision conditions and flow out of the node |
Action Node
Version 5.0 includes Webhook delivery, Push Notification, and WeChat - Subscription Message delivery.
| Metric | Metric definition | Description |
|---|---|---|
| Node Inflow | Users who flow into the node | |
| Planned | Users who flow into the node and aren't filtered out by do-not-disturb control, an empty send ID, or a journey pause | |
| Attempted Push | Planned users, excluding users filtered out by channel delivery caps | Planned - Delivery Caps |
| Push Succeeded | Users for whom the push channel's send API was called and the message was sent successfully | |
| Delivered | Users for whom the push channel returns a Delivered receipt | Shown only when the channel has the touch funnel setting enabled |
| Clicked | Users for whom the push channel returns a Clicked receipt | Shown only when the channel has the touch funnel setting enabled |
| Moved Forward | Users who flow out of the node |
Switch to the Details view at the top to view the detailed data funnel of the action node.
| Metric | Metric definition | Description |
|---|---|---|
| Node Inflow | Users who flow into the node | |
| Do not disturb | Users filtered out by the do-not-disturb skip condition | |
| Push ID is Null | Users whose channel send ID is empty | |
| Pushing ID Duplicated | Users who arrive at the journey in the same batch and are filtered out because of duplicate send IDs | Counted only for scheduled entry |
| Planned | Users who flow into the node and aren't filtered out by do-not-disturb control, an empty send ID, or a journey pause | |
| Timeout handling | The number of users who exit the journey because system processing timed out | By default, processing is considered timed out if the node transition isn't completed within 12 hours |
| Delivery Caps | Users filtered out by the push channel's delivery caps | |
| Attempted Push | Planned users, excluding users filtered out by channel delivery caps | Planned - Delivery Caps |
| Push Succeeded | Users for whom the push channel's send API was called and the message was sent successfully | |
| Push Failed | The number of calls to the push channel's send API that returned an error | |
| Moved Forward | Users who flow out of the node |
Control Node
- Profile Split/Behavior Control/time control components
| Metric | Metric definition | Description |
|---|---|---|
| Node Inflow | Users who flow into the node | |
| Moved Forward | Users who meet the flow conditions and flow out of the node |
- A/B Test component
| Metric | Metric definition | Description |
|---|---|---|
| Node Inflow | Users who flow into the node | |
| Entry Users | The number of users who enter each group | |
| Activated Users | Users who enter each group and complete the activation event within the experiment metric window | Counted only when an activation event is added |
| Achieved Users | Users who achieve the experiment metric within the specified window (after completing the activation event) | |
| Metric Achieve Rate | Achieved Users / users in the group (activated) | |
| Lifted by | (Experiment Group achieve rate - Control Group achieve rate) / Control Group achieve rate | |
| Confidence Interval of Improvement Rate | The range that the true value of the metric lift may fall into, based on a two-sided test with a 5% significance level | |
| Moved Forward | Users who flow out of the node |
- End Node
| Metric | Metric definition | Description |
|---|---|---|
| Moved Forward | Users who flow out of the node |
Node-level effect metrics
In a journey, operators often need to evaluate how well different node configurations actually perform, for example:
- The reach conversion of a push action node
- Differences in user behavior between split strategies
To help operators evaluate journey strategies more intuitively, we provide the node effect metrics capability. With it, users can configure key metrics for journey nodes and, after the journey runs, view metric performance for different nodes or split strategies. The feature supports:
- Configuring effect metrics for an Action Node
- Configuring experiment metrics for an A/B Test Node
With node effect metrics, operators can quickly answer questions such as:
- Which delivery strategy brings higher conversion?
- Does user behavior differ across split paths?
- Does a journey node really improve the target behavior?
Add metrics
You can add node-level effect metrics while viewing a journey: click the button in the toolbar on the right of the Node Data & Details canvas, or click Action Node in the empty state of the Custom Analysis tab, to open the Custom Node Metrics drawer. The drawer has two tabs: Action Node and A/B Test Node.
Effect metrics are a journey-level setting. After you add them, you can view the post-delivery metric performance under every action node in the journey.
View the report
After you click a node, switch to the Custom Analysis tab on the right to view the effect metrics of each node.