> 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/pricing-experiences/pricing-experiences-overview/price-test-common-use-cases/the-double-down.md).

# The Double Down

Iterate based on the results from the test above. Let's say you run the test outlined above, and find that you see higher conversion and higher revenue per visitor on Product A at the $9 price point and on Product B you don't see a change in conversion across the three price points, but you see an increase in revenue per visitor on the $22 price point. Because [price elasticity is a curve](https://blog.intelligems.io/intelli-blog/price-elasticity), it may make sense to run another test drilling in further on the price for these products.

*What this test design might look like based on the above scenario:*

<table data-header-hidden><thead><tr><th width="242"></th><th></th><th></th><th></th></tr></thead><tbody><tr><td></td><td><strong>Control Price</strong></td><td><strong>Lower/Higher</strong></td><td><strong>Even Lower/Higher</strong></td></tr><tr><td><strong>Product A</strong></td><td>$9</td><td>$8</td><td>$7</td></tr><tr><td><strong>Product B</strong></td><td>$22</td><td>$24</td><td>$26</td></tr></tbody></table>

{% hint style="info" %}
Note that this is one scenario where your Control Group is not what has been live on the site, but rather the 'winner' from the previous test.
{% endhint %}


---

# 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/pricing-experiences/pricing-experiences-overview/price-test-common-use-cases/the-double-down.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.