> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abconvert.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Combined Test: Getting Started
> A/B test multiple changes together in one test so each visitor sees one coherent experience.
## What is a combined test?
A combined test stacks multiple changes, such as a price change and a shipping rate change, into a single test with a single traffic split. Each group sees its own version of every change, so each visitor experiences all the changes together as one package.
You can combine any test type: [price](/experiments/price-test), [shipping](/experiments/shipping-test), [offer](/experiments/offer-test), [URL redirect](/experiments/url-redirect-test), [template](/experiments/template-test), [theme](/experiments/theme-test), [visual editor](/experiments/visual-editor-test), and [checkout](/experiments/checkout-test). You can add each test type once. Each change has the same requirements as when you run it as its own test. For example, a shipping change still requires the Shopify Carrier Service API.
## When to use it
* **Price + shipping (total-cost framing):** Increase product prices and lower or remove the shipping fee. The customer pays a similar total either way; you're testing whether "higher price, free shipping" converts better.
* **Shipping + theme (consistent storefront messaging):** Change your shipping rates and pair them with a theme that mentions the new rates in its banners and product pages, so the promise on the page matches the rate at checkout.
* **Price + content:** Raise a product's price and use the visual editor to strengthen the value messaging on the product page, testing whether better positioning supports a higher price point.
A combined test measures all changes as one package. It can't tell you which change drove the result. To measure a change on its own, run it as its own test instead.
## When NOT to use it
* **You need to know which individual change caused the lift.** Run each change as its own test instead.
* **The changes do not belong to one strategy.** A combined test works best when every change supports the same shopper experience.
* **One included change is not ready to launch.** Each change has the same requirements as the standalone test type, so finish those requirements first.
* **You only need to test a page-level copy or design edit.** Use a [visual editor test](/experiments/visual-editor-test) when the change does not need pricing, shipping, offer, checkout, template, or theme logic.
## Set up a combined test
In the ABConvert dashboard, click **Create New Test** and select **Combined Test**.
Enter a descriptive name for your test, write a clear hypothesis, and select your primary success metric. By default, traffic is split evenly between the Control and Variant groups. You can adjust the traffic allocation or add more variants.
Write the hypothesis about the overall strategy. "Customers prefer all-inclusive pricing" beats "raise price by 10% and make shipping free."
Define which visitors should enter the test using audience targeting and traffic allocation rules. Read more in the [Audience targeting](/experiments/audience-targeting) guide.
Click **Add change** and pick a test type. Each change appears as a card in the list. Expand it to walk through the same configuration steps as the standalone test. Each type can be added once.
Review your full test configuration. The review screen summarizes what each group sees across all changes. We recommend using [Preview test](/experiments/lifecycle#preview-before-you-launch) to check the variant on your storefront before launching. When everything looks correct, click **Launch test**.
## Common mistakes
* **Reading the result as if each change was measured separately.** A combined test tells you whether the package won, not which part of the package won.
* **Stacking unrelated ideas.** Keep the hypothesis about one strategy, such as total-cost framing, not a grab bag of changes.
* **Forgetting standalone requirements.** A shipping change still needs shipping setup, and a price change still needs price-test readiness.
* **Skipping Preview test.** Preview the full package so each test group sees the intended version of every change.
## Combined test FAQs
A visitor is assigned to one group on their first visit, and that assignment stays the same on every page and every visit. Each change then applies where its own configuration targets: storewide changes like price and shipping apply everywhere, while page-scoped changes like a visual editor change appear only on the pages they target.
Yes. The same conflict rules apply as for tests running on their own. For example, only one active test can modify a given shipping zone.
While a theme test is running, your combined test can't include changes that conflict with it:
* a theme change
* a visual editor change
* a template change, if a theme in the theme test doesn't have the template you want to test