Skip to content
English
Customer portal
Go to goodunited.io
  • There are no suggestions because the search field is empty.

Metrics at Node Level in Journey Builder

Journey Builder now shows message-level metrics in BUILD mode—sent, delivered, opened, and permission issues. This helps teams optimize messages and spot drop-offs. Metrics apply only to journeys published after the update and are hidden in EDIT mode

What’s New


  • Message nodes now display metrics at the card (node) level in Journey Builder’s BUILD mode.

    Screenshot 2025-04-24 at 12.16.24 AM


  • Metrics shown per node:
      • Sent – Number of messages sent from this node
      • Delivered – Successfully delivered messages
      • No Permission – Messages undelivered due to permission issues
      • Opened – Messages considered opened based on the watermark logic
    • Percentage-based metrics are displayed alongside raw counts.
    • Metrics are visible only in BUILD mode and hidden in EDIT mode.
    • Metrics are only available for journeys published after this enhancement (older journeys will not show metrics).
    • If a node is deleted, its associated metrics are removed.
    • If a node is edited, historical metrics are preserved.
    • Messages are counted as “Opened” if a later message is opened in the same session (watermark logic).

Why It Matters


      • Previously, journey-level metrics only provided high-level performance, without visibility into how individual messages/nodes were performing. This limited the ability to test and iterate effectively.
      • By adding node-level metrics, teams gain insight into:
        • Which messages supporters engage with (or ignore)
        • Where drop-off is occurring in journeys
        • Whether messages are being blocked due to permission issues
        • This improvement supports smarter message optimization, A/B testing, and a stronger overall engagement strategy. It also lays the groundwork for future enhancements like click-through tracking and node-level performance versioning — all critical as the platform scales to support larger supporter journeys and more granular personalization.

Known Limitations


    • Watermark logic marks earlier messages as "Opened" if a later one is opened — which may overstate engagement with individual nodes.
    • Multiple journeys may influence “Opened” metrics if unread messages exist across sessions — data is session-aware, not journey-isolated.
    • Metrics only apply to journeys published after this release; retroactive data is not shown, because the watermark logic starts taking into effect in this release.
    • If a node is deleted, all its metric data is lost and cannot be recovered.
    • CTR (click-through rate) tracking is not included in this release.