Design page variations
By designing page variations, you define alternative content on page level, including various page elements. For example, your variables may be:
- Page content
- Page layout and widgets
- Call-to-action or any other button’s text, color, size, or location
NOTE: Keep in mind that all page variations are hosted on the same URL.
A best practice is to have one variable at a time, so that you know which one made the difference.
To design page variations:
- Open the original page for editing.
NOTE: You must create an A/B test before designing page variations.
- Expand the A/B menu and select the variation you want to design.
- To create a variation, modify any part of the page, including its layout, widgets, and content.
For more information, see Edit the content of page.
For example, your A/B test goal is to get more form submissions. You can experiment by putting a shorter form on the original page and putting a longer form on the variation page to measure which form has more submissions.
To preview any variation you made to the original page do one of the following:
- Navigate to Marketing » A/B testing. Expand the Actions menu and select Preview page variations.
- Open the original page for editing and navigate to A/B » Preview page variations.
When a variation is served to a specific visitor, they see this same variation all the time. That is, Sitefinity CMS never shows multiple variations to the same visitor and the randomization happens only during the first visit.
Page variations in multilingual mode
When working in multilingual environment with synced pages, the modifications you make to any of the language versions of the page are applied to pages in all cultures. When editing the content of a page in a language version that is not the original, you are creating an A/B test page variation only for this language. That is, only when visitors browse this specific language version of the page, they are served with page variations of this A/B test.
For more information about pages in multilingual mode, see Translate an existing page.
RECOMMENDATION: We recommend when ending an A/B test for a language version of a page, to save the page variations as drafts, instead of directly publishing a variation. Then make sure that modifications you made to page content and text are translated in the other language versions.