> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/receipts-and-confirmation-page.md).

# Receipts and Confirmation Page

Customize the receipt email and confirmation page for your Action Page: sender, subject, message, logo, variable tokens, and an optional callback URL.

The **Receipt** panel sets what donors see and receive after they submit your form: the confirmation page and, on Donation Pages and Event Pages, the email receipt. You'll find it in the Page Builder under **Setup > Receipt**. This article covers each section of the panel.

{% hint style="info" %}
Lead Pages don't send an email receipt. They show the confirmation page after a submission.
{% endhint %}

## Open the Receipt Panel

To open the Receipt panel:

1. Go to **Action Pages > Pages**.
2. Hover over the page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Setup > Receipt**.

## Receipt Preset

Choose a saved receipt preset, or edit the fields below for this page only. Applying a preset replaces the fields below. See Presets in the [Page Builder Overview](/action-pages/page-builder.md).

## Sender

* **From name:** The name the receipt email comes from.
* **Reply-to email:** Where replies to the receipt go.

## Message

* **Subject line:** The receipt email subject. Required.
* **Callback URL:** An optional page to send donors to after a successful submission, such as a thank-you page on your website.
* **Footer disclaimer:** Text at the bottom of the receipt, such as "Tax-deductible to the extent allowed by law."

## Confirmation Page

* **Logo:** The logo shown on the confirmation page.
* **Message:** The message shown after the form is completed.

The logo and message also appear in the email receipt when the receipt is sent.

## Variable Tokens

Insert these tokens in the subject line or the confirmation message to personalize the receipt:

* `{{first_name}}`
* `{{last_name}}`
* `{{donation_amount}}`
* `{{suffix}}`
* `{{title}}`

Example: "Thank you, `{{first_name}}`!" reads "Thank you, Maria!" for a donor named Maria.

When you're done, click **Save**.

## Event Receipts

On Event Pages, the buyer gets the receipt. Tickets are attached when **Send ticket with receipt email?** is set to Yes in the Event panel. See [Manage Events](/action-pages/action-page-basics/manage-events.md).

## Related Articles

* [Page Builder Overview](/action-pages/page-builder.md)
* [Submissions](/action-pages/action-page-basics/submissions.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 by asking a question.

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

```
GET https://docs.anedot.com/action-pages/page-builder/receipts-and-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.