Page content, two-page and template tests

Page content

A Page content test changes elements on your store for one version.

• Pages to change answers Where should the change appear?: All product pages, All collection pages, Home page, or Specific pages by path (up to 5 patterns).
• Each change is one of Change text, Change a link or image or Show or hide. Up to 10 changes per version.
• You identify the element with a CSS selector. There is no point-and-click picker yet.
• Changes apply when the element appears and can hide the page for up to 300 ms while the version loads.

Personalize for an audience

A Page content test with an audience rule can personalize instead of splitting traffic 50/50. On Audience, choose Only some shoppers, add a condition such as device, country or customer tags, then turn on Personalize for this audience.

• Everyone in the audience sees the change, except a held-out group that keeps the original. Held-out group (%) starts at 10% and can be 1% to 50%.
• The test has the original (the holdout) and one change. The traffic split is set by the holdout and cannot be edited while personalization is on.
• Results read as lift from personalization against the holdout, so you can see whether showing the change to this audience earned more than leaving it alone.
• Personalization needs an audience rule. If you switch back to everyone, the test cannot launch until you add a condition or turn personalization off.

Two pages

A Two pages test sends shoppers to a page you already built.

• Original page answers Which page do you want to test? Only shoppers who open it are split.
• Each version page must be a page on your own store. Shoppers cannot be redirected away from checkout, and a version page cannot be the original.
• Query parameters and UTM tags are kept on the redirect.
• Search engines may see both pages. Add a canonical tag on Version B pointing to the original if both stay public.

Page template

A Page template test shows some shoppers the same page with another theme template, such as a second product page layout. Create the alternate template in your theme first (in the theme editor, Add template).

• Pages to test: All product pages, All store pages, Home page, or One page by path. Only shoppers who open those pages are split.
• Each version picks one of the alternate templates your live theme has for that kind of page. If we can't read your theme, type the template's name instead: product.fancy.json is fancy.
• Shoppers in a version stay on the same address; the page is shown with ?view= and the template's name added. Query parameters and UTM tags are kept, and a page that already has ?view= is not changed again.
• Launch checks that the template is in your live theme. If you remove it later, shoppers see the default template.
• The address and canonical tag stay the same, so search engines keep indexing the original page. The page can be hidden for up to 300 ms while it switches.