> 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/starting-a-price-test.md).

# Starting a Price Change Experience

Learn how to launch a Price Test in the Intelligems app.

Now that the test is live, we recommend going through the add to cart and checkout process in a few incognito browsers so you can get added to different test groups and ensure everything is working as expected. If you have not already QA'ed your test before launching it, run [Atlas QA](/general-features/atlas-ai/atlas-qa.md) from the QA & Preview tab, then work through [this checklist](/pricing-experiences/price-test-qa-checklist.md). Please [reach out to our support team](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) with any issues!

Starting a Price Change puts your prices in front of shoppers and begins collecting the conversion and revenue data you'll read in your results. On most integrations it also raises your Shopify prices to the highest price in the experience, so read Step 4 before you click Start.

{% hint style="info" %}
Starting a Personalization works the same way through Step 3. A Price Change Personalization can only reduce prices, so your Shopify prices aren't updated and you won't see the pop-up in Step 4.
{% endhint %}

### **Step 1: Confirm the Intelligems script is in your live theme**

In addition to Intelligems Javascript, confirm any other theme changes completed during the integration are in your live theme as well. If not, publish the script and any changes before proceeding.

### **Step 2: Click Start**

In the left nav, go to **Pricing**, find your experience in the list, and click **Start**. You can also open the experience and click **Start** in the top right.

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2F41YQ7PyHOLaEbPoFD8SR%2FScreenshot%202026-08-10%20at%201.09.22%E2%80%AFPM.png?alt=media&amp;token=b5b0e280-3c6d-4743-903c-f01d7efabca2" alt=""><figcaption></figcaption></figure>

**Start** is a split button. **Start Test** takes the experience live now. **Schedule Test** sets a start and end date so it goes live on its own.

{% hint style="warning" %}
**If Start doesn't go through,** one of these is usually why:

* **Your plan doesn't include Pricing.** You can build a Price Change on any plan, but launching one needs the Pricing module, and Pricing isn't available on a trial. The app will offer you plan options.
* **A Shipping Test is running.** If your Price Change integration uses Shopify Functions with the Expand operation, we block you from starting one while the other is live. See Can I run a shipping test and a price test at the same time?
* **Your pricing integration isn't finished.** [Reach out to our support team](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) and we'll check the configuration on our side.
  {% endhint %}

### **Step 3: Confirm the integration and your QA**

**Confirm QA** opens with two checkboxes: one confirming the [Price Integration](/pricing-experiences/price-testing-integration-guides.md) is complete for your store, and one confirming you've [QA'd the experience](/pricing-experiences/price-test-qa-checklist.md). **Confirm** stays greyed out until both are ticked.

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2FF85Yw79RjsyS3qQntXCE%2FScreenshot%202026-08-10%20at%201.13.49%E2%80%AFPM.png?alt=media&amp;token=25be677e-e617-4597-9f09-5bbc12ba8d52" alt=""><figcaption></figcaption></figure>

### **Step 4: Choose whether to update your Shopify prices**

**If your integration uses Shopify Functions,** a pop-up asks whether Intelligems should update your Shopify prices. Select **Yes, Update My Prices and Start Test**.

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2F3ZNlzJ6U1nCuKtD7bgYt%2FScreenshot%202026-08-10%20at%201.15.32%E2%80%AFPM.png?alt=media&amp;token=659505cc-b292-44ab-aeff-e2253800f1f5" alt=""><figcaption></figcaption></figure>

We raise every product in the experience to the highest price you've set, then discount it back down for the lower groups. Raising it first keeps a shopper from seeing a lower price in Google Shopping or a Facebook shop and then landing on a higher price on your site.

{% hint style="info" %}
If every price in the experience is at or below your control price, your Shopify prices aren't altered when you start. Read more on why we update your Shopify prices.
{% endhint %}

{% hint style="info" %}
Some accounts see a second option, **No, I'll Update My Prices**. It shows up only once Intelligems has turned on Skip Catalog Price Update for your store, which we do on request for Functions integrations. If you need your Shopify prices left alone, [reach out to our support team](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) rather than looking for the option in the pop-up.
{% endhint %}

**If your integration uses duplicate products,** this pop-up doesn't appear. You'll see a modal listing the duplicate products created for each price group. As long as you followed [these steps](/pricing-experiences/price-testing-integration-guides/integration-guide-using-duplicate-products/step-4-configure-duplicate-products.md) to configure them, click **Start Test**.

{% hint style="warning" %}
**Testing a currency other than your store's default?** Set your prices in Shopify Markets for that market before you start. Functions can't change market-specific prices, and any market set to auto-convert takes its price from your default-currency base price, so a live default-currency test raises those markets too. See Multi-Currency Testing.
{% endhint %}

### **Step 5: Check your site**

Run through add to cart and checkout for each group and confirm the prices match what you set.

To land in a specific group, add the `?igTg=` parameter with that group's ID to your store URL. Sticky bucketing keeps you in the first group you're assigned to, so opening more incognito windows won't reliably move you. General FAQs has the steps for finding a group ID.

Your Shopify base price is now the highest price in the experience for everyone, including visitors your targeting excludes. That's the price update from Step 4. Your preview link shows group prices only, so the two won't match.

If you haven't QA'd yet, work through the [Pricing Experience QA Checklist](/pricing-experiences/price-test-qa-checklist.md). [Reach out to our support team](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) with any issues.

### **What happens next?**

When you're ready to wrap up, see Ending a Price Change Experience.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intelligems.io/pricing-experiences/pricing-experiences-overview/starting-a-price-test.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.