Skip to main content
A journey gives you two views of its behavior. Run inspection answers “what happened for this one user?” node by node. Metrics answer “how is this journey performing overall?” across every run. Version history ties them together: a run always shows the version it executed. All three live in the journey editor.

​
How it works

​
Run inspection

Every invoke records a run: the journey’s full execution trace for that user, identified by a runId. A journey’s Logs tab lists its runs. Filter by run ID, status, date, or recipient, then open one to inspect it. Run inspection is a console view. No public API returns a run’s step-by-step trace. The detail view overlays each node’s outcome on the journey graph. It shows which nodes ran, which branch was taken, where a run is paused, and which node failed. Click a node for its step context:
  • the input data at that step
  • the profile as it existed then
  • the conditions evaluated, and whether they passed
  • the node’s output
Use it to answer “why did this branch take the wrong path” or “why did this send fail.” A run has one of these statuses:

​
Metrics

The Metrics tab shows delivery performance across the journey’s send nodes:
  • a send-volume chart over time
  • a table of every template (one per send node) with sent, delivered, opened, and clicked rates
Click a template row for a drawer with per-metric charts and a provider-level breakdown. Filter to a 7-, 30-, or 90-day window, computed in UTC. Templates removed in a later version keep an “Inactive” prefix, so their historical metrics stay visible.

​
Version history

Publishing a journey creates a version. Republish an older version to roll back. Inspection is version-aware: opening a run shows the version active when the run started, not the current draft. You see what that user experienced. Line up version history against the metrics timeline to correlate a metric shift with a publish.

​
Limits & behavior

  • Run inspection is console-only. No public endpoint returns a run’s step-by-step trace. Inspect runs in the journey’s Logs tab.
  • Metrics windows are UTC. A “last 7 days” figure is 7 UTC days.
  • Runs are pinned to their version. A run inspects against the version it executed, even after you publish changes.

​
FAQ

Open the journey’s Logs tab and search by run ID (returned from the invoke call), or filter by recipient, status, or date.
Inspection is version-aware. A run shows the published version active when it started, so you see what the user experienced, not your latest edits.
Not through a public endpoint. Run inspection is a console view. Use the runId from the invoke response to find the run in the Logs tab.