> 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/pages/customizable-confirmation-page.md).

# Customizable Confirmation Page

A journey's confirmation and thank-you screens are ordinary **pages** you build in **Content → Pages**, so you can customize them fully — order summary, messaging, terms, and branding — using the Component Library. There are no HTML templates or merge tags to edit.

## Build it

1. In **Content → Pages**, create or edit a **Storefront** page for the screen — for example a `Checkout - Confirmation` page (the order summary) and a `Checkout - Thank You` page (the closing message).
2. Lay the page out with components — order summary, text, images, terms — and publish it.
3. In the journey builder (**Content → Journeys → Edit → Steps**), add a step bound to that page and order it at the end of the flow. See [Confirmation and thank-you steps](https://docs.peakcommerce.com/product/journeys-and-pages/journey-steps/step-confirmation-page-step.md).

What used to require editing confirmation-page HTML templates and `${…}` merge tags is now done visually in the page editor.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peakcommerce.com/product/journeys-and-pages/pages/customizable-confirmation-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
