> 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-discount-decision.md).

# The Discount Decision

A discount is the fastest lever on the post-purchase page and the easiest one to overpay for. The shopper has already converted, so some brands find they don't need one at all. For others, 10% is what turns a look into a click.

The discount applies uniformly to every item in the offer, so this is one number to test rather than a per-product exercise.

*What this test design might look like:*

|              | **Control** | **Variant A** | **Variant B** |
| ------------ | ----------- | ------------- | ------------- |
| **Discount** | No discount | 10% off       | 20% off       |

{% hint style="info" %}
Read this one on [profit per visitor](/analytics/overview/experiment-analytics.md) rather than acceptance rate. A 20% offer will almost always be accepted more often than a 10% offer. Whether it earns more is the question.
{% endhint %}

You can set no discount, a percentage off, or a fixed amount off. Percentage off keeps the offer proportional across a mixed catalog, which matters if the products in the offer vary a lot in price.


---

# 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-discount-decision.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.