> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases.md).

# Post-purchase Experience Use Cases

{% hint style="info" %}
Post-purchase experiences are available on the Smart Checkout & Post-Purchase and Unlimited plans. They work on every Shopify plan, including stores that aren't on Shopify Plus.
{% endhint %}

The post-purchase page is the one moment where a shopper has already paid and their payment details are still on file. Adding a product takes one click, so a small offer here can lift AOV without touching checkout itself.

Every use case below is a Post-purchase Upsell experience. Build the offer once, then choose how to run it:

* **Run a test.** Split traffic between offers and let the results tell you which one earns more per order.
* **Create a personalization.** Show one offer to everyone, or only to shoppers whose order meets a rule you set.

[Tests vs. Personalizations](/getting-started/tests-vs.-personalizations.md)

### **Where to start**

| Use case                                                                                                                                                     | What it moves                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
| [The Add-On Audition](/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases/the-add-on-audition.md)       | Finds the product shoppers will actually accept as an add-on                 |
| [The Discount Decision](/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases/the-discount-decision.md)   | Shows what a discount costs you in margin against what it buys in acceptance |
| [Recs vs. Picks](/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases/recs-vs.-picks.md)                 | Tests Shopify's recommendations against a list you pick yourself             |
| [The Countdown Question](/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases/the-countdown-question.md) | Measures whether a visible deadline moves shoppers or just adds noise        |

### **Before you run any of these**

Post-purchase offers only render on orders Shopify allows them on. Accelerated checkouts (Shop Pay, PayPal, Apple Pay, Google Pay, and buy-now-pay-later services), gift-card-only orders, local pickup and local delivery, draft orders, orders under $0.50, and orders placed in a currency other than your store's primary currency all skip the page. Read the full list before you size the traffic you expect.

[Post-Purchase Upsell FAQs](/post-purchase-experiences/post-purchase-upsell-faqs.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.intelligems.io/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases.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.