> 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/getting-started/tests-vs.-personalizations.md).

# Tests vs. Personalizations

Every change you make in Intelligems, whether it's a new price, a checkout badge, a shipping threshold, or a homepage banner, starts the same way: you build it once. From there, you decide how it goes live.

Ship it as a **Personalization** and it runs always-on for the audience you choose. Everyone who matches your [targeting](/general-features/targeting.md) sees the change, all the time.

Run it as a **Test** and your traffic splits between a control group and one or more variants, so you can measure what the change is worth before you give it to everyone.

Nothing about the setup changes between the two.

### **Which one to pick**

You don't need to know in advance whether something "should" be a test or a personalization. A good rule of thumb:

* Not sure it'll work? Test it. Add a control group and run it long enough to get a [statistically significant](/analytics/overview/experiment-analytics/statistical-significance.md) result.
* Already confident, or making a small, low-risk change? Skip straight to a Personalization and ship it live.

{% hint style="info" %}
**On the fence? Test it.** You can always roll a winning test group out as a Personalization. You can't go the other way and turn a Personalization into a Test.
{% endhint %}

### **How they differ**

This works the same way in every module: [Content](/content-experiences/content-experiences-overview.md), [Merchandising](/merchandising-experiences/offer-modifications.md), [Pricing](/pricing-experiences/pricing-experiences-overview.md), [Shipping](/shipping-experiences/shipping-testing-getting-started.md), [Checkout](/checkout-experiences/getting-started-with-checkout.md), and [Post-purchase](/post-purchase-experiences/getting-started-with-post-purchase-upsells.md).

|                 | Personalization                         | Test                                                                                                        |
| --------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Audience        | Everyone who matches your targeting     | Split between a control group and one or more variants                                                      |
| Multiple Groups | None                                    | This can be a control group or alternate change to test against.                                            |
| Goal            | Ship a change you're confident in       | Find out what the change is worth in revenue or profit before you commit                                    |
| Running it      | Enable and disable it whenever you want | Start it, pause it, and end it once you have your answer                                                    |
| Reporting       | Visitors, orders, and revenue it drove  | Full [experiment analytics](/analytics/overview/experiment-analytics.md), with significance for every group |

### **Rolling out a winning test group**

When a group wins, you don't have to rebuild it. [Roll it out](#rolling-out-a-winning-test-group) and Intelligems ends the test and creates a Personalization carrying the same modifications, ready for you to target and activate. You can roll out more than once from the same test, so if one group won with a particular audience and another won everywhere else, each can go live to the audience it won with.

{% hint style="info" %}
**Three types roll out differently.** Price experiences apply the winning prices straight to Shopify, for all visitors, once, at the moment you end them. A [theme change](/content-experiences/content-experiences-overview/how-to-set-up-a-theme-change-experience/ending-a-theme-test.md) rolled out to all visitors should be done directly to Shopify. [Shipping experiences](/shipping-experiences/shipping-testing-getting-started/ending-a-shipping-test.md) can't be rolled out, so you'll need to make the winning rates live in Shopify yourself.
{% endhint %}

### **Where to find yours**

Your **Dashboard** lists every experience in your store, and each module in the left nav lists its own. On both, the **All Experiences**, **Tests**, and **Personalizations** tabs filter the list, and every row is tagged with the mode it's running in.

[Experiment Analytics](/analytics/overview/experiment-analytics.md)

[Sitewide Analytics](/analytics/overview/sitewide-analytics.md)


---

# 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/getting-started/tests-vs.-personalizations.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.