> 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/testing-prices-with-subscriptions.md).

# Testing Prices with Subscriptions

Read this article to understand how to run price tests if your store offers subscriptions.

## Introduction

If you offer subscriptions as an option on your product(s), testing prices is a bit more complex. Intelligems supports testing both one-time and subscription prices for your store's products, and this article will walk through the basics on what is possible, and how to get started.

{% hint style="warning" %}
Subscription price changes are available as a **Test** only. You can't run one as a Personalization. See [Pricing Experiences FAQs](https://docs.intelligems.io/pricing-experiences/price-testing-faqs.md) for the full list of price limits by mode.
{% endhint %}

### **What you can test**

Intelligems supports a wide variety of tests on subscription products. Some examples include:

* **Test one-time prices, keep the subscription discount % the same.** The subscribe-and-save discount (e.g., 10% off) stays fixed, so the subscription price moves up or down along with the one-time price. For example, if the one-time price goes from $50 to $60, a 10% discount takes the subscription price from $45 to $54.
* **Test one-time prices, keep the subscription price the same.** The subscription price stays fixed, so only the one-time price changes. This means the discount customers see for subscribing changes too. For example, if the subscription price is $45 and the one-time price goes from $50 to $60, the subscription discount grows from 10% off to 25% off. This is useful when you want to change one-time pricing without touching what subscribers pay, but it can make subscribing look more or less attractive.
* **Keep the same one-time price, test different subscription discounts.** Vary the subscribe-and-save discount (e.g., 10% vs. 15% off) to see how it affects subscription uptake and revenue.

## How does Intelligems implement subscription tests?

Subscription price tests run on duplicate products. Subscription apps show one-time and subscription prices based on the product itself, so each test group needs its own copy of the product. Intelligems creates the duplicates when you save the test, and you add them to your subscription app like any new product. See [Managing Duplicate Products](https://docs.intelligems.io/pricing-experiences/pricing-experiences-overview/managing-duplicate-products-when-redirecting-to-duplicate-pdps.md) for the steps.

## Which subscription apps is Intelligems compatible with?

Intelligems works with all major subscription apps through duplicate products, including:

* Recharge
* Stay.Ai
* Skio
* Prive
* Smartrr
* Loop
* Ordergroove

For anything not listed, reach out to our support team.

## Which Intelligems plans qualify for subscription testing?

Smart Pricing has to be on your plan before you can start a subscription test. You can build the test without it, but the app will stop you at launch and ask you to choose a plan. See plan details.

## Can I perform the integration with Intelligems on my own if I offer subscriptions?

Testing subscriptions often requires a more [involved integration & setup](https://docs.intelligems.io/pricing-experiences/price-testing-integration-guides/integration-guide-using-duplicate-products.md) than typical price tests. As a result, we recommend having Intelligems perform the integration if this applies to your store. [Reach out to our support team to learn more](https://portal.usepylon.com/intelligems/forms/intelligems-support-request)!

## I've read all of the above and am ready to set up my test. How do I do this?

Create your price test as usual, then set up the duplicates in your subscription app. This guide walks through it:

{% content-ref url="/pages/rnd20RLEnJYN8uqwmMd4" %}
[Managing Duplicate Products](https://docs.intelligems.io/pricing-experiences/pricing-experiences-overview/managing-duplicate-products-when-redirecting-to-duplicate-pdps.md)
{% endcontent-ref %}


---

# 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/testing-prices-with-subscriptions.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.
