> 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/merchandising-experiences/offer-modifications/how-to-set-up-an-amount-off-products-experience.md). # How to Set Up an Amount off Products Experience An Amount off Products Experience takes a percentage or a dollar amount off the specific products you choose. The discount applies automatically in the cart, so shoppers get it without entering a code and there's nothing for a coupon site to pick up. Run it as a **Test** and Intelligems holds back a control group and reports what the discount did to AOV and profit per visitor. Run it as a **Personalization** and the discount stays on for the audience you target. {% hint style="warning" %} This offer changes the totals in the cart and at checkout. It does not change the prices shown on your product or collection pages, and it won't add a strikethrough. If you need the discounted price to appear on the PDP, use a Price Change Experience instead. {% endhint %} ### **Where to start** ### 1. Create the experience **Amount off Products** appears under both **Merchandising** and **Pricing** in the **Choose an Experience to create** modal. It's the same experience type either way, so start from whichever module you're already in: * On the left navigation, click **Merchandising**, then **New Merchandising Experience** * Or click **Pricing**, then **New Pricing Experience** Pick the **Amount off Products** card. {% hint style="info" %} Merchandising is a module you subscribe to, and the Test and Personalization paths aren't always enabled together. Check your plan before you build. {% endhint %} ### 2. Choose: Test or Personalization * **Running it as a Test?** * Rename the Test and add a Description. This is optional and internal only, but tests can stay live for weeks, so the more detail here, the more your future self will thank you. * Click the **+** button to create a group for each variation (2–5 groups) and name them. * Use the slider to set the traffic split for each group. * Click **Next Step** when you're done. * Note: the more groups you add, the longer it'll take to reach [statistical significance](/analytics/overview/experiment-analytics/statistical-significance.md). * **Running it as a Personalization?** Skip groups entirely. You're building one always-on version for your targeted audience. ### **3. Set up the offer** These fields are the same in both modes. * **Discount name:** the name shoppers see in their cart and at checkout. It's the line that tells them why they're paying less, so name it after the offer rather than after your internal campaign. * **Discount value:** choose **Percentage off item** or **Fixed amount off per item**, then enter the amount. A fixed amount tends to land better on higher-AOV products, where a flat dollar figure feels more meaningful than a percentage. * **Minimum purchase requirements:** off by default, so the discount applies with no threshold. Check the box to require a **Quantity of items** or a **Subtotal of items** first. A threshold gives shoppers a reason to add one more unit, which lifts AOV. * **Applies to:** select which products the discount covers. If you don't select any, all products are eligible. You can select by Product Type, Vendor, Status, or Collection, or search for individual products. * **Combinations:** **Shopify discounts** and **Intelligems discounts** are both checked by default, so the offer stacks. Clear a box to stop it stacking with that kind of discount. Combining with a Shopify discount also depends on the Shopify side, so that discount has to be set to combine in your Shopify admin or it won't stack no matter what you check here. * **Maximum Discount Amount:** check **Limit total amount discounted** to cap what one customer can take off. Worth setting on a percentage discount, where a large cart can give away more margin than you planned for. * **Purchase type:** one-time purchases only by default. You can switch to subscription purchases only, or to both. {% hint style="info" %} If you choose a subscription option, the discount will only apply to the first order. It will not apply to any refills. {% endhint %} ### **4. Add components** Components tell shoppers the offer exists. Amount off Products supports two: * **Progress Bar** shows how close the cart is to your threshold, which nudges shoppers to add another unit. * **Offer message** carries the promotion on your homepage, so shoppers know about the discount before they reach the cart. {% hint style="warning" %} The Progress Bar counts your whole cart toward the threshold, not just the products you selected under **Applies to**. If you've scoped the discount to one collection, the bar will still fill on items that won't be discounted. Scoping the offer to all products keeps the bar and the discount aligned. {% endhint %} You add components here in the builder and style them in Global Styles. ### **5. Set targeting (optional)** For a Test, a visitor's group is assigned on their first visit and stored via a first-party cookie, so they'll see the same variant on repeat visits during the test. For a Personalization, everyone who matches your targeting sees it every time. Either way, you can narrow who's included in several ways, all under the Audience option unless noted: * UTM parameters * JavaScript expressions * Device type (mobile or desktop) * New vs. returning visitors * [Mutually Exclusive Tests](/general-features/targeting/mutually-exclusive-experiments.md) prevent visitors from being targeted by related experiments at the same time, to avoid interaction effects {% hint style="warning" %} If you built your test groups by duplicating existing Personalizations, any targeting set on those Personalizations is ignored. The test's own audience, currency, and page targeting is used in its place. {% endhint %} ### **6. Configure analytics** Choose whether analytics should default to only orders containing specific products (helpful if your offer targets a particular PDP), or orders containing any products in your shop. You can always change this later in your Analytics filters. What you configure next depends on which path you chose in step 2: * Personalization? Add any [Custom Metrics](/analytics/overview/custom-events.md) you want to track, beyond the built-in ones. * Test? Choose your Key Metrics and Primary Metric to measure against your control group, plus any [Custom Metrics](/analytics/overview/custom-events.md). ### **7. Preview and activate** Preview your changes on the live site, then activate. The [Merchandising Experience QA Checklist](/merchandising-experiences/offer-test-qa-checklist.md) covers what to check in the cart and at checkout before a shopper sees it. {% embed url="" %} --- # 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/merchandising-experiences/offer-modifications/how-to-set-up-an-amount-off-products-experience.md?ask=&goal= ``` `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.