> 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/adding-a-journey.md).

# Create a journey

1. Go to **Content → Journeys** and click **+ New Journey**.
2. Fill in **Journey Details**:
   * **Name** — an internal name for the journey.
   * **Type** — **E-Commerce**, **Customer Self-Service**, **Partner Self-Service**, or **CSR Self-Service** (sets the journey's default behavior and audience).
   * **Status** — starts as **draft**; set it to active when you're ready to publish.
   * **Order Structure** — how products are grouped when this journey creates orders.
   * **Description** — an optional internal note.
   * **Hide runner Next/Back/Complete buttons** — turn this on only if your pages supply their own navigation controls; otherwise leave it off so customers can advance.
3. *(Optional)* Set **SEO & Metadata** — Browser Tab Title, Meta Description, and Open Graph title/description/image. These control how the journey's public page appears in browser tabs, search results, and social link previews.
4. Click **Create Journey**. You land in the journey builder.
5. On the **Steps** tab, click **Add step** for each page the customer passes through and put them in order (for example Signup → Billing → Confirm → Complete). Use the **Flow** tab to connect steps and add branching. See [Managing journey steps](/product/journeys-and-pages/journey-steps/managing-journey-steps.md).
6. On the **Settings** tab, set the **subscription term** and the **profile assignments** that control who can enter the journey. See [Journey Settings](/product/journeys-and-pages/journey-settings.md).
7. **Preview** the journey to test it, then **Publish**. Publishing makes the journey live and gives you a public URL you can share or embed.


---

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