> 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/the-add-on-audition.md).

# The Add-On Audition

The product you offer matters more than anything else on the post-purchase page. Shoppers have already bought what they came for, so the offer has to read as an add-on rather than a second decision. Low-cost accessories, consumables, and companion items tend to clear that bar. A second full-price hero product usually doesn't.

Run three or four candidates against each other and let profit per visitor pick the winner.

*What this test design might look like:*

|           | **Control**             | **Variant A**       | **Variant B**     | **Variant C**            |
| --------- | ----------------------- | ------------------- | ----------------- | ------------------------ |
| **Offer** | Shopify recommendations | Accessory under $25 | Consumable refill | Two small items together |

{% hint style="info" %}
Turn on **Exclude products in order** so you're not offering someone the item they just bought, and **Exclude out of stock items** so a winning variant doesn't quietly stop rendering when inventory runs out. Both live in General Settings.
{% endhint %}

[How to Set Up a Post-Purchase Upsell Experience](/post-purchase-experiences/getting-started-with-post-purchase-upsells/how-to-set-up-a-post-purchase-upsell-personalization-or-test.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/the-add-on-audition.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.