Skip to main content
A journey represents the full path a real user takes through your application — from the first page they land on to the moment they convert, sign up, or complete a critical action. Rather than testing a single interaction in isolation, a journey links multiple flows in sequence (for example, landing page → lead capture form → confirmation email) so you can verify that the entire path holds together, not just its individual parts.

​
Why Journeys Matter

Passing individual flows does not guarantee your full user path works. A user might successfully reach your signup page (flow 1) and your confirmation page might render correctly (flow 3), but a broken handoff in between — a failed redirect, a missing session token, a dropped form submission — means no one can actually complete the journey. Journeys catch exactly these integration failures by verifying that the output of one flow feeds correctly into the next.

​
Journey Structure

A journey is an ordered list of flows that share state across steps. This shared state is what makes journeys more than a playlist of independent tests:
  • Ordered execution — Flows run in the sequence you define. If an earlier flow fails, subsequent flows are skipped and the journey is marked as failing at that step.
  • Shared context — Data produced in one flow (such as a lead ID, a session cookie, or a confirmation code) is available as input to the next flow. You define which outputs to pass forward when you build the journey.
  • Single health signal — The journey surfaces one overall status so you can see at a glance whether the complete path is working, without inspecting each flow individually.

​
Example Journey: Prospect Pipeline

The following journey verifies that a prospect can move from first contact to confirmed lead without any broken steps:
  1. Visit landing page — Navigate to the campaign landing page and assert the primary call-to-action button is visible.
  2. Fill lead form — Click the CTA, fill in the prospect’s name, email, and company, and submit the form.
  3. Verify confirmation — Assert the thank-you page is displayed and confirm a confirmation email is received at the test inbox.
If step 2 fails because the form submission returns an error, step 3 never runs — and your dashboard immediately shows you which step broke the pipeline.

​
Journey Health

A journey’s overall health status gives you a fast read on whether your end-to-end path is working:
  • All Passing — Every flow in the journey completed successfully on its last run. Your full user path is operational.
  • Partially Failing — One or more flows in the journey failed, but others passed. The dashboard highlights exactly which step broke and where the path is interrupted.
  • Fully Failing — The first flow in the journey failed, which prevented all subsequent flows from running. Your entry point is broken and no users can begin the path.
Start by mapping your top three conversion paths as journeys — for example, your main signup funnel, your primary sales lead capture, and your core in-app action. These three journeys cover the flows that directly impact revenue and are the highest-value paths to monitor continuously.

Flows

Build the individual step sequences that make up each stage of a journey.

Monitors

Attach a journey to a monitor to verify your end-to-end path on a continuous schedule.