Split URL testing in Umbraco Engage helps you compare different versions of a page.
You create different versions of a page. Each version can have different designs, text, or buttons based on the possibilities that have been setup in Umbraco.
When you set up the A/B test, you can send 50% of visitors to page A and 50% to page B. This way, you can see which page helps achieve the goal of the test better.
The split URL test is a great way to test different checkout workflows, for example.
Umbraco Engage enables running A/B tests on pages using a specified Document Type. This article covers how and when to use this type of test.
Test all pages using a specific Document Type with this test. Select the Document Type(s) you want to test and Umbraco Engage makes sure the correct CSS and JavaScript is inserted to the correct pages.
The test type "Document Type" can be started in the Engage section and in the Content App. The type is selected in step 2 of the setup.
The test allows you to select one or more Document Types within Umbraco. On all pages using the selected Document Type(s) the A/B Test will render the additional CSS and JavaScript you will enter. The CSS and JavaScript must not create any side effects on these pages. This is a manual task.
Once you have selected the pages you want to test, you can specify one or more variants. For each variant, it is possible to click the Edit button. This will bring up a popup that allows you to write JavaScript or CSS:
In this example, some JavaScript changes the page's background color.
You can save and preview whether your code works by clicking Save & preview.
After creating all variants, start your A/B testing as written in the Setting up the A/B test article.
Umbraco Engage provides the option to set up A/B testing on individual pages. This article covers how and when to use this type of test.
The Single-Page test allows an editor to start an A/B test without a single line of code.
When you select the Single-Page test type you can create two or more variants.
The first variant is always the original content and the published page. Variant B is the first variant that can be created and with the button 'Add a variant' more alternatives can be added. More variants mean that a test should run for longer to become reliable.
The variant can be given a name and if you click on Edit you will open up the split view editor:
On the left side, the original content is shown (Original) and the variant is shown on the right. In this side-by-side editing mode, you can edit the content for your variant.
Some properties are inactive (visually indicated because they are greyed out). Which properties you can edit is specified in the setup of the properties of your Document Type.
Specifying when segmentation is allowed can be done per property using the Allow segmentation value.
In the overview of the Document Type, you will see if properties can be segmented as they will have the Vary by segments label:
Sometimes you cannot adjust a specific property because it was not configured when Umbraco was set up. In those cases, you can use the CSS/JavaScript field to add a code-snippet to make these adjustments. The best way is to do it via property editing in the split view edit mode. You do not have to write any CSS or JavaScript code.
To do this click CSS/JavaScript in the A/B Testing editor bar:
This will give the editor a popup where CSS and JavaScript can be entered:
These lines of code will automatically be inserted at the bottom of the page.
Use the Save & preview button to make sure all works as expected. This can also be done via the "Save & preview" option in the editor bar.
Once the variant is set up, finish the A/B Test via the Back to A/B test button in the editor bar.
Finish the steps in the Settings up the A/B test article to verify and start your A/B Test.
Because of the unique implementation of Umbraco Engage, the content will automatically be updated for this variant.
The algorithm will determine which variant of the propety needs to be rendered.
Umbraco Engage provides the option to run A/B tests across multiple pages. This article covers how and when to use this type of test.
The Multiple Pages test allows you to across multiple pages at once. In Umbraco, you can select the pages you want to test. For all these pages you can specify which type of CSS or JavaScript will be added to the specific variant. The multiple pages test requires you to write (or copy in) some CSS and JavaScript code.
The test type Multiple pages can be started in the Marketing section and in the Content App. The type is selected in step 2 of the setup.
The test allows you to select one or more pages within Umbraco. On all these pages the A/B Test will render the additional CSS and JavaScript you enter. The CSS and JavaScript must not create any side effects on these pages. This is a manual job that cannot be automated with Umbraco Engage.
Once you have selected the pages you want to test, you can specify one or more variants. For each variant, it is possible to click the Edit button. This will bring up a popup that allows you to write JavaScript or CSS:
In this example, some JavaScript is added to change the page's background color.
You can save and preview whether your code works by clicking Save & preview.
After you have created all variants start your A/B testing as described in the Setting up the A/B test article.
Get an overview of the available types of A/B tests you can run with Umbraco Engage.
Three different types of A/B tests are available:
to test a specific page within Umbraco.
A way to test at the same time.
Test an entire and all of the pages using this type.
. This enables you to select two or multiple pages and serve one of these URLs per visitor.
The A/B tests are set up within an Umbraco context. You can reuse properties that are already created. Umbraco Engage is also aware of the structure of your website and concepts like Document Types.
When setting up the A/B test, you can select the type of test you want to set up.
A Single-Page test can only be started in the A/B test and not from the Engage .