> 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/which-experience-should-i-build.md).

# Which experience should I build?

Every experience starts with a change you want to make to your store. You pick the type of change first, build it, and then decide whether it runs as a test or a personalization.

{% hint style="info" %}
The create flow changed in July 2026. You now choose the experience type first and test or personalization second. [Here's a short walkthrough](https://www.loom.com/share/9aa70f1286da429f94a4d9ba0d1b483f).
{% endhint %}

### **Start from what you want to move**

| I want to                                          | Build in      |
| -------------------------------------------------- | ------------- |
| Find the price that makes me the most profit       | Pricing       |
| Get bigger orders out of a discount                | Merchandising |
| Cover my shipping costs without losing conversions | Shipping      |
| Change what a shopper sees on the page             | Content       |
| Convert more of the shoppers who reach checkout    | Checkout      |
| Add revenue to an order after it's placed          | Post-purchase |

Which modules you can build in depends on your plan. Every paid plan includes Content.

### **The 22 experience types**

Click **New experience** and these show up as cards, grouped by module. The **All** tab lists every one of them together.

| Module        | Type                  | What it changes                                                  |
| ------------- | --------------------- | ---------------------------------------------------------------- |
| Content       | Content Edits         | Headlines, copy, and on-page elements.                           |
| Content       | Redirects             | Sends traffic to a different URL.                                |
| Content       | Styles & Javascript   | Injects your own CSS and JavaScript.                             |
| Content       | Theme Change          | Swaps the live theme for another one.                            |
| Content       | Template Changes      | Serves a different page template.                                |
| Merchandising | Amount off Products   | Discounts specific products by percentage or amount.             |
| Merchandising | Amount off Order      | Applies an automatic cart-wide discount.                         |
| Merchandising | Volume Discount       | Tiered pricing that rewards larger quantities.                   |
| Merchandising | Free Gift             | Adds a free gift when the cart hits a threshold.                 |
| Pricing       | Price Change          | The product price itself, everywhere it appears and at checkout. |
| Pricing       | Amount off Products   | The same type that appears under Merchandising.                  |
| Shipping      | Shipping Rates        | Your rates, flat or tiered by price or weight.                   |
| Shipping      | Free Shipping         | The cart value at which shipping becomes free.                   |
| Checkout      | Upsell                | Recommends add-ons during the checkout flow.                     |
| Checkout      | Trust Badge           | Shows trust signals to reduce hesitation.                        |
| Checkout      | Shipping progress bar | Shows how close the cart is to the threshold you set.            |
| Checkout      | Call Out              | A promo or message banner.                                       |
| Checkout      | Static Image          | A custom image block.                                            |
| Checkout      | Brand Logo            | Your logo, for added assurance.                                  |
| Checkout      | Countdown Timer       | A live countdown.                                                |
| Checkout      | Text Only             | A plain text block.                                              |
| Post-purchase | Post-purchase Upsell  | One-click add-ons after checkout.                                |
| Post-purchase | Post-purchase Funnel  | Chains several offers after the order. Coming soon.              |

{% hint style="info" %}
**Amount off Products sits in two modules.** It's one type. Build it from Merchandising or from Pricing, whichever you're already in.
{% endhint %}

Checkout types need Shopify Plus. Post-purchase works on every Shopify plan.

### **If you don't have a hypothesis yet**

Start from something that worked for another store and adapt it. [**Quick Start Experiences**](/general-features/common-use-cases.md) in your left nav has some great ideas.

Still stuck, or not sure which type fits the change you have in mind? [Open a ticket](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) and we'll point you at the right one.


---

# 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/which-experience-should-i-build.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.