---
title: "Activity and Journey history"
description: "Follow a customer through an Experience."
search:
  tags: ["Features"]
  keywords: ["user history", "experience run", "exit reason"]
---

Journey history lets you follow one customer through an Experience. You can see which steps ran, where they waited, and how the run ended—useful when a customer took an unexpected path or you want to understand the activity behind a conversion.

Each run is a Journey. Returning to the same Experience can create another Journey when its re-entry settings allow it.

<span id="follow-a-run" />

## Journey activity

Open a customer's **Journeys** tab, or open **Journeys** on the published Experience. Filter or sort the list, then select a run.

The list shows the Experience, status, start time, outcome, and **Plane**. Plane tells you whether the Journey is running on the device or server. A Journey can move between the two: a screen runs on the device, while a wait or connected action can continue on the server after the screen closes.

The detail page brings together the customer's identity, Journey ID, duration, and outcome. Its timeline shows when steps started and completed, including the time between them. You can also see the Experience's delivery configuration and open its details.

## Status and outcome

A Journey's status tells you whether it's still running:

| Status | Meaning |
| --- | --- |
| **Active** | Running or waiting to continue. |
| **Completed** | Reached the end of its execution. |
| **Stopped** | Ended before normal completion. |
| **Coalesced** | A duplicate run was combined with another Journey for the same customer and Experience. |

Completion and conversion answer different questions. A customer can finish onboarding without starting their first workout, or close a paywall and purchase later. **Completed** says the run ended; the configured conversion goal says whether it led to the outcome you wanted.

The conversion window can stay open after dismissal or completion. A matching outcome during that window can still convert the Journey. Presentation and verified purchases also have their own events, so seeing a screen doesn't imply a sale.

<span id="compare-repeated-visits" />

## Repeat visits and versions

When re-entry is allowed, each visit has its own Journey ID, start time, and history. Open the run that matches the visit you're investigating.

An in-progress Journey can keep the published version it started with. Publishing an update changes future delivery without replacing the screens someone is already moving through. Pausing an Experiment or choosing its winner also leaves existing Journey assignments intact.

<span id="match-the-context" />

## App and system events

Your app sends events for actions such as finishing an export or starting a workout. Nuxie adds system events for SDK lifecycle, Journey steps, screen presentation, and Experiment exposure. Those system event names start with `$`. Answers collected during an Experience are available in [Responses](/docs/guides/collected-responses).

Use the [system event reference](/docs/api-reference/system-events) to look up an event. [Eligibility and re-entry](/docs/guides/eligibility-and-reentry) explains why a run could start, and [Analytics and revenue](/docs/guides/measurement) shows the results across customers.