A combined test stacks multiple changes, such as a price change and a shipping rate change, into a single experiment 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, shipping, offer, URL redirect, template, theme, visual editor, and checkout. 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.
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.
In the ABConvert dashboard, click Create New Test and select Combined Test.
2
Add basic information and configure traffic split
Enter a descriptive name for your experiment, 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.”
3
Configure your audience
Define which visitors should enter the experiment using audience targeting and traffic allocation rules. Read more in the Audience targeting guide.
4
Add and configure changes
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.
The Changes step with a price change completed and a shipping change in setup.
The change picker.
5
Review and launch
Review your full experiment configuration. The review screen summarizes what each group sees across all changes. We recommend using Preview test to check the variant on your storefront before launching. When everything looks correct, click Launch test.
The review summary. Each group lists its version of every change.
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.
Can I run a combined test alongside other tests?
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
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
