> 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/get-inspired/test-subscription-pricing.md).

# Test subscription pricing

## Grow subscriber revenue with a subscription price test

Subscribers are your most valuable customers. Testing their price separately from one-time prices shows you what grows recurring revenue without touching the rest of your store.

#### How to set it up

1. Contact support (<support@intelligems.io>) to confirm your account is set up with duplicate products and redirection. Subscription price tests need both.
2. Go to Pricing and create a new price test with your subscription products.
3. Set test group prices for the subscription. Your one-time prices stay unchanged.
4. Connect the duplicate products in your subscription app, such as Recharge or Skio, following the setup guide.
5. QA your test, then start it.

{% hint style="info" %}
Subscribers keep the price they signed up at after the test ends.
{% endhint %}

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2FhRJ98MuOcMjJ5n0lwKlP%2Fsubscription-price-test.png?alt=media&amp;token=f9d5835d-92b7-4a55-a440-46407db5f983" alt=""><figcaption></figcaption></figure>

[Create this experience now →](https://app.intelligems.io/pricing)


---

# 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/get-inspired/test-subscription-pricing.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.
