> 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/journeys-overview.md).

# Journeys Overview

A **journey** is a guided, multi-step flow that PeakCommerce hosts as a public page (or an embed) and runs a person through to complete a specific commerce outcome — buying a plan, changing or cancelling a subscription, or any guided self-service task — with no custom front-end code. You define the steps, the data each one collects, and the order they run in; PeakCommerce renders the flow, enforces your rules, creates the resulting order or subscription in your billing system, and records every session.

Journeys are how most customer-facing commerce happens in PeakCommerce. Rather than building bespoke checkout or self-service screens, you compose a journey from reusable pages and publish it.

## What you can do with journeys

* **Sell** — stand up a self-service checkout (offer/plan selection → signup → billing → confirmation → thank-you) that creates a real subscription in your billing system at the end.
* **Let customers self-serve** — change plan, add or remove add-ons, upgrade or downgrade, or cancel — including **branching retention paths** such as presenting a save offer before a cancellation completes.
* **Equip CSRs** — run the same flows on a customer's behalf from the CSR workspace.
* **Enable partners** — give resellers guided flows to transact for the customers they manage.
* **Publish and measure** — every journey gets a public URL and can be embedded; preview before launch, then review completed / active / abandoned sessions and heatmaps.

Those are the headline uses, but journeys are really a general workflow engine — see [What you can build with journeys](/product/journeys-and-pages/journey-basics/journey-use-cases.md) for the full range, from dunning recovery and onboarding wizards to surveys, returns, and agent-driven flows.

## Journey types

A journey's **Type** sets its default behavior, who it is for, and where it fits in the platform:

| Type                      | Use it for                                                    |
| ------------------------- | ------------------------------------------------------------- |
| **E-Commerce**            | Public, unauthenticated self-service checkout and signup      |
| **Customer Self-Service** | Signed-in customers managing their own subscription           |
| **Partner Self-Service**  | Partners / resellers transacting on behalf of their customers |
| **CSR Self-Service**      | Customer service reps acting on a customer's behalf           |

## Key concepts

* **Step** — one page in the flow. Each step renders a page, reads and writes values to the journey's shared **context** (so data collected early is available to later steps), and can trigger **actions** such as creating the order.
* **Flow** — the order steps run in, including branching that sends people down different paths based on their choices.
* **Settings** — journey-wide configuration: the **subscription term** the journey creates, the **profile assignments** that control who may enter it, and **SEO & metadata** for its public page.
* **Runner** — the hosted experience customers actually move through at the journey's public URL.
* **Session** — one person's run through a journey, tracked as completed, active, or abandoned.

## How a journey is built

Open **Content → Journeys** and open a journey to edit it: add and order **Steps** (each bound to a page) on the Steps tab, wire branching on the **Flow** tab, and configure **Settings**. **Preview** to test, then **Publish** to make it live and get its public URL.

## Managing journeys

The **Content → Journeys** list shows each journey's type, status, step count, and session totals. Search by name, filter by status or tag, and use the row menu (**⋯**) for **View, Edit, View Sessions, Archive,** or **Delete**.

## Learn more

* [Create a journey](/product/journeys-and-pages/journey-basics/adding-a-journey.md)
* [View a journey](/product/journeys-and-pages/journey-basics/viewing-a-journey.md)
* [Edit a journey](/product/journeys-and-pages/journey-basics/editing-a-journey.md)
* [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/journeys-overview.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.