> 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.

## 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.
* **Heatmap viewer** — see where users click and where they drop off.

## Tabs

* **Steps** — the ordered steps a customer moves through.
* **Flow Diagram** — a visual map of how the steps connect.
* **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).


---

# 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.