Journeys
Inspect one user's durable run through an Experience
A Journey is one user’s run through an Experience. It connects eligibility, the active Version, screen progress, authored actions, Goal state, responses, and the eventual exit.
Why Journeys matter
Aggregate conversion answers whether an Experience worked. A Journey answers what happened to one user and gives Nuxie the durable state needed to resume, advance, or finish the work correctly.
Each Journey records identifiers for the Experience, Version, user, and run, plus its current state and timestamps.
Lifecycle
A Journey begins when the SDK accepts an eligible trigger and persists the start. It remains active while it can continue through the published Flow. It reaches a terminal state when the goal or exit rules complete it, it expires, it is superseded, it fails, or an operator explicitly ends it.
Visible presentation and Journey state are related but not identical. A Journey may remain active while its screen is not visible, and the runtime can resume an approved checkpoint when app lifecycle and release authority allow it.
Journeys tab
Open an Experience and choose Journeys to inspect its runs. Use the table and Journey detail to answer questions such as:
- Did the trigger start a Journey?
- Which Version and Experiment variant did it use?
- What screen or node was last active?
- Was the Goal met?
- Why did the run exit?
- Were responses submitted, left as drafts, or abandoned?
Pause and active runs
Pausing an Experience stops new Journeys. It does not silently cancel existing runs. The Experience header reports remaining active runs and offers a separate confirmation to end them as cancelled.
Identity and resume
Anonymous users receive a stable local identity. Identified users can reconcile Journey checkpoints across sessions and devices. Resume still depends on the current authenticated release, its state version, and the Experience’s active delivery rules; the SDK does not blindly restore stale screen state.
Responses
For surveys, quizzes, and onboarding forms, response values are tied to the Journey and response schema Version. The Responses tab summarizes submitted, draft, and abandoned rows and exposes field-level distributions for supported types.