> 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/upsells-and-upgrades.md). # Upsells and Upgrades Ask donors to make their gift monthly before checkout, and offer connected pages after a gift, with Pre-conversion upsell and Post-conversion upgrades. Upsells and upgrades help you grow a gift at the moment a supporter is ready to give. A **Pre-conversion upsell** asks a donor to turn a one-time gift into a monthly recurring gift before checkout finishes. **Post-conversion upgrades** show donors one or more connected Action Pages right after a successful gift. You'll find both in the Page Builder under **Workflows > Pre-conversion upsell** and **Workflows > Post-conversion upgrades**. This article covers how to set up each one. {% hint style="info" %} Pre-conversion upsells work on Donation Pages. Post-conversion upgrades work on Donation Pages and Lead Pages. Neither is available on Event Pages. {% endhint %} ## Before You Begin * To save changes, you need **Action Pages: Edit permissions**. * To connect pages to an upgrade, create those Action Pages first. ## How They Fit in the Donor Journey **Workflows > Donor journey** shows the steps a supporter moves through in order: 1. **Pre-conversion upsell:** A recurring offer shown before the donor submits. 2. **Page submission:** The donor submits the form and completes checkout. 3. **Post-conversion upgrades:** Upgrade offers shown after a successful gift. 4. **Confirmation receipt:** The receipt the donor receives. Click any step to open its panel. ## Set Up a Pre-Conversion Upsell To set up a pre-conversion upsell: 1. Go to **Action Pages > Pages**. 2. Click the name of the Donation Page you want to edit. 3. Select **Workflows > Pre-conversion upsell**. 4. Check **Offer recurring conversion before submit**. 5. Choose an existing recurring upsell preset, or fill in the fields below. 6. Click **Save**. ### Upsell Content * **Internal name:** A name for this upsell, so your team can find it later. Required. * **Body:** The message asking the donor to give monthly. You can use these variables: `{{ask}}` for the monthly amount, `{{impact}}` for the result of your impact formula, and `{{first_name}}` for the donor's first name. * **Accept button** and **Accept qualifier:** The button donors click to switch to a monthly gift, and the text under it. The defaults are "YES!" and "Convert my gift to a monthly gift and help us reach more people." * **Decline button** and **Decline qualifier:** The button donors click to keep their one-time gift, and the text under it. The defaults are "No, thanks." and "Process my original one-time gift." The default body reads: "`{{first_name}}`, before we process your gift, would you consider giving a monthly recurring gift in the amount of `{{ask}}`?" ### Ask Calculation The monthly amount you ask for is based on the donor's one-time gift. * **Ask percent:** The percentage of the one-time gift to ask for each month. Use a whole number from 1 to 100. The default is 60. * **Minimum ask:** Enter an amount greater than zero and less than your **Maximum ask**. The default is $15. * **Maximum ask:** The most you'll ask for each month. The default is $1,000. * **Round to nearest:** The ask rounds up to the nearest multiple of this amount. The default is $5. * **Impact formula:** The formula used to calculate `{{impact}}`. The default is `({{ask}}*12)/60`. The monthly ask is the **Ask percent** of the one-time gift, capped at your **Maximum ask**, then rounded up to the nearest multiple you set in **Round to nearest**. For example, with the defaults, a $100 one-time gift becomes a $60 monthly ask. ### When Donors See the Upsell The upsell appears when a donor chooses a one-time gift that's at or below your **Maximum ask**. It doesn't appear for recurring gifts or for payments made with express checkout or Bitcoin. ## Set Up Post-Conversion Upgrades Post-conversion upgrades show donors connected Action Pages after their gift goes through. You decide which pages to show based on the amount of the original gift. To set up post-conversion upgrades: 1. Go to **Action Pages > Pages**. 2. Click the name of the Donation Page or Lead Page you want to edit. 3. Select **Workflows > Post-conversion upgrades**. 4. Check **Offer an upgrade after checkout**. 5. To reuse an upgrade from another page, search for it in **Attach existing upgrade** and select it. To build a new one, enter a **Configuration name** and click **Add upgrade**. 6. Set up each upgrade, as described below. 7. Click **Save**. ### Upgrades and Breakpoints Upgrades run in order after submission when the original amount is below each breakpoint. * **Name:** A name for the upgrade. Required. * **Breakpoints:** Each breakpoint covers a range of gift amounts. **From** is filled in for you, and you set **Up to**. Every upgrade needs at least one breakpoint. Click **Add breakpoint** to add another range, and use the breakpoint's options to copy, remove, or reorder it. Gifts above your last breakpoint don't get an upgrade. ### Connected Action Pages For each breakpoint, add the Action Pages donors see when their gift falls in that range. 1. In **Add an action page**, search by page name or page ID. 2. Select the page to connect it. Each breakpoint needs at least one connected page. You can't connect the page you're editing or an Event Page. If you connect more than one page, add a **Multi-page call to action** to introduce the choices. ### Amount Presets To change the giving amounts shown on the connected pages for a breakpoint: 1. Check **Override default amounts for this breakpoint**. 2. Choose **Currency** or **Percentage**. 3. Enter each amount, and add an optional description. 4. Click **Add amount** to add more. With **Percentage**, each amount is a percent of the donor's original gift total. For example, a 25% preset on a $33 gift shows an $8.25 upgrade amount. Amounts are rounded to whole cents, and a 0% preset isn't shown. When you're done, click **Save**. ## Related Articles * [Page Builder Overview](/action-pages/page-builder.md) * [Giving Amounts and Frequencies](/action-pages/page-builder/giving-amounts-and-frequencies.md) * [Abandoned Actions](/action-pages/page-builder/abandoned-actions.md) * [Exit Intent](/action-pages/page-builder/exit-intent.md) * [Receipts and Confirmation Page](/action-pages/page-builder/receipts-and-confirmation-page.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/upsells-and-upgrades.md?ask=&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.