> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/journey-basics/viewing-a-journey.md).

# View a journey

Open **Content → Journeys**, find the journey, and choose **View** from its row menu (**⋯**) to open its overview page.

<figure><img src="/files/MemrrpUTVU6dx99bJulf" alt="A journey&#x27;s overview page: its name, status, and public link; a live conversion funnel showing sessions started, completed, active, and abandoned with a completion rate; and the step-by-step flow with the commerce actions each step runs"><figcaption><p>A journey's overview — its identity and public link, a live conversion funnel, then the step-by-step flow with the commerce actions each step runs.</p></figcaption></figure>

## What the overview shows

* **Public URL** — the live link customers use to run the journey (`/journey?journeyId=…`). Copy it, or open it in a new tab to test.
* **Cart prefill URL parameters** *(optional)* — append parameters to the public URL to pre-select a plan or pre-fill the cart when the journey opens.
* **Session stats** — **Completed**, **Active**, and **Abandoned** counts for the journey.
* **Journey details** — name, type, status, created date, and description.

## Actions

From the top of the page you can:

* **Edit** — open the step builder and settings. See [Edit a journey](/product/journeys-and-pages/journey-basics/editing-a-journey.md).
* **Preview** — run the journey yourself without affecting its session stats.
* **Publish** — make the current version live and snapshot it to version history.
* **Embed** — get a snippet to embed the journey in another site.
* **Flow diagram** — open the journey's flow graph on its own page. See [Flow Diagram](#flow-diagram) below.
* **Heatmap viewer** — see where users click and where they drop off.

## Tabs

* **Steps** — the ordered steps a customer moves through.
* **Related Lists** — records associated with the journey.
* **History** — the journey's published versions. See [Journey version history](/product/journeys-and-pages/journey-basics/journey-history.md).

## Flow Diagram

The **Flow diagram** action opens a full-page view (`/journeys/<id>/flow`) that draws the journey as a graph: steps sit in order on a vertical spine from **Start** to **End**, and every transition is drawn as a real connector.

* **Routes** (branching rules) travel labeled lanes to the right of the steps, each labeled with its condition (for example `cancellationReason = too_expensive`). Failure routes are labeled **on failure**.
* **Back** transitions loop up the left side, so a step that can return to an earlier step is visible as a literal loop.
* **Broken** routes — rules that point at a step number that no longer exists — dead-end into a red *step n — missing* marker.
* **Disabled** steps are dimmed, and transitions through them are shown dotted and struck through (**skipped**), matching how the live journey skips them.

The header shows a health strip: step and route counts, plus **broken**, **unreachable**, and **cycle** indicators when the graph has problems (or **✓ healthy** when it doesn't). Click an indicator — or any row in the **Diagnostics** panel below the graph — to jump to the affected step. Hover a step to spotlight its direct connections, click it to highlight everything reachable downstream from it, and click the legend chips to show or hide each kind of transition.

Each step that runs commerce actions shows a **⚡ runs on advance** panel: the actions in execution order, each with its integration, plus markers for **commit** (a billing write that locks the step once it runs — committing steps also get a green edge accent), **async** (doesn't block the step), `if …` conditions, 🔒 (required by the step's role), **paused** (the step advances without it), and **fail → step n** (on failure, routing continues to the step's on-failure target). Indented **↳ on fail** rows are compensating actions that run only when their parent action fails. Use the **⚡ commerce actions** legend chip to hide the panels for pure-flow reading.

Use **Back to journey** at the top of the page to return to the journey overview.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/journeys-and-pages/journey-basics/viewing-a-journey.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.