What is it?
Journeys reporting tracks overall journey performance, trigger-level events, node-specific interactions, and individual message outcomes. This data allows you to monitor subscriber flow, engagement, conversion revenue, and message delivery status across all stages of a journey. Please note that some Journeys performance metrics may update faster than others. As a result, metrics may appear slightly out of sync.
The reporting suite tracks the following metrics:
- Journey-Level Metrics:
- Total sent: The total number of messages you sent to subscribers using this journey.
- CTR (Click-Through Rate): Total clicks divided by the number of recipients. (Clicks are non-unique; multiple clicks by a single subscriber increase CTR).
- Revenue: The total revenue attributed to the journey.
- CVR (Conversion Rate): Total conversions divided by total clicks. (Conversions are non-unique; multiple purchases by a single subscriber increase CVR).
- Entered journey*: The total number of subscribers who successfully initiated the journey.
- Subscribers who didn’t enter the journey due to entry frequency*: The number of subscribers who triggered the journey but were excluded based on entry frequency configurations.
- Exited journey*: The total number of subscribers who exited due to exit rules configured on the journey
- Some journey types (price drop, low inventory, back in stock) also show the number of subscribers who exited due to products going out of stock. To see this, toggle the enhanced metric to On.
- Node-Specific Metrics:
- Subscribers in each branch arm*: The volume of subscribers routing through individual conditional branches, A/B test, or parallel paths.
- Exited at each “End journey” step*: The number of subscribers who completed and terminated the journey at specific end nodes.
- Per-Message Metrics:
- Messages sent*: The total volume of outbound messages dispatched at an individual message step.
- Messages dropped by reason*: The count of undelivered messages, categorized by the failure type: smart sending, unresolved macros, offer not retrieved, or content/media failure.
- Exited due to exit rules*: The number of subscribers removed from the journey at a specific message step due to predefined exit criteria.
- Exited due to automatic checks*: The number of subscribers removed by automated system validations. This applies to price drop, low inventory, and back in stock journeys.
* Available for all revisions published on or after June 26, 2026.
How do I use it?
- Navigate to the Journeys page and click a journey with the Active label or that was previously active.
- To view baseline performance metrics (such as Total Sent, CTR, Revenue, and CVR) for the current version, view the Version Performance on the left panel.
- To view historical data, select a prior iteration from the version dropdown menu in the upper-right corner. While viewing past versions, you can also restore a previous version, clone a version to create a new journey, or remove subscribers from previous active versions.
- To view expanded metrics, navigate to the left sidebar and select View additional metrics.
- To view node-specific and per-message metrics directly on the interactive journey map:
- Inspect individual branch arms to see the volume of subscribers routing through each path.
- Inspect individual End journey steps to see the volume of subscribers who completed the journey at that specific node.
- Click an A/B test node to view the total number sent, runtime duration, and performance comparison stats for each variant.
- Click a Send message node to view individual performance details and specific delivery drop reasons.
Why should I use it?
- Evaluate Revenue and Engagement: Monitor click-through rates, conversions, and total revenue to evaluate the financial return and subscriber engagement of your customer journeys.
- Identify Entry Barriers: Quantify the exact volume of subscribers blocked from entering journeys due to frequency capping constraints.
- Audit Routing Logic: Track subscriber distribution across complex conditional paths to identify which specific branch arms or "End journey" steps terminate sessions most frequently.
- Troubleshoot Message Delivery Failures: Isolate and debug message drops by reviewing specific system errors, such as payload/media failures, missing offers, or macro resolution issues.
- Monitor Automation Health: Verify the operational integrity of exit rules and product catalog automations by tracking automated real-time inventory exits.