> 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-steps/step-confirmation-page-step.md).

# Confirmation and Thank-You Steps

A journey's closing steps are ordinary steps bound to **confirmation** and **thank-you** pages — for example a **Confirm** step (a `Checkout - Confirmation` page showing the order summary) and a **Complete** step (a `Checkout - Thank You` page).

To customize what customers see at the end of a journey:

1. Build or edit the confirmation / thank-you page in [Content → Pages](/product/journeys-and-pages/pages.md) — see [Customizable confirmation page](/product/journeys-and-pages/pages/customizable-confirmation-page.md).
2. In the journey builder (**Steps** tab), add a step and bind it to that page.
3. Order it as the final step (or steps) of the journey.

Because the page is built from components, you control its layout and content directly — there is no separate "confirmation step type" to configure.


---

# 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-steps/step-confirmation-page-step.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.