How to create a Multipage Test

A Multipage test enables you to test a new version of one or several elements across a user’s journey, that is to say on different pages which don’t share the same structure (such as the homepage, the product pages and the basket page). These element(s) may have different layouts depending on page structure. As for A/B tests, after analyzing the results of your test, you need to decide which version has performed best according to the goal you wanted to reach (e.g., increasing the number of clicks, the number of pages viewed, decreasing the bounce rate). You can then apply these changes directly to your website.

To create an multipage test, go to Web Experimentation, click the Create button and select Multipage Test.

👉 To learn about the different ways to create a campaign, please refer to How to create a campaign.

Configuration

Step 1: Main information

The Main Information page is the first step toward your new Multipage Test campaign.

We recommend establishing a hypothesis of your test according to the following model: If I apply [this change on my webpage] to [this audience], then [it will impact] and enables to enhance [this goal]. And to add it in the hypothesis field.

In the Pages section, enter the URL you want to load in the editor for each page or group of pages. Each page coincides with a part of the user's journey you want to test. You need to include at least 2 pages which must be different (e.g.,: the product pages and the basket page).

👉 For more information on how to configure this step, refer to How to set-up Main Information step.

Step 2: Editor

You have two ways to create content for your campaign in AB Tasty:

With the visual editor

You must adapt the modification to each page you have configured. Each page has the same number of variations, as you build an entire new user’s journey. If it is clickable, always put an action tracking on the element you add or modify in order to follow the performance of your campaign (e.g.,: cross to close the popin, CTA in the popin etc.). Don’t forget to put these action trackings on each page.

👉 To learn how to use the Visual Editor, discover options, and dive into our widget libraries, please read the Visual Editor Guide

With the code editor

The Code Editor enables you to declare your code (JavaScript, CSS) without having to load the Visual Editor. The Code Editor is the best solution for developers who want to save time.

👉 To learn how to use the Code Editor, please read the Code Editor Guide

Step 3: Goals

As the primary goal enables you to determine which variation takes precedence over the others, for Multipage tests, exceptionally, your primary goal should be the result of the user’s journey, regarding the main goal of your test: retention (primary goal should be the number of viewed pages), loyalty (revisit rate) or conversion (transaction rate). You should also choose the action tracking related to the elements you have modified as secondary goals. Indeed, this is the user behavior that is most likely to be affected by the modification you have made in the editor.

👉 To learn how to configure Goals, please read Campaign flow: Goals step

Step 4: Targeting

You have to declare WHERE your campaign should be visible on your website (e.g. on every page, on specific pages, on only one page, etc.), for WHOM (e.g. your whole traffic, mobile users only, etc.), and in WHICH conditions (e.g. after a certain number of pages, when it’s cold outside, etc.) it should appear. You can also decide WHEN visitors will see the campaign depending on the recurrence you choose.

The target pages (Where section)must be different for each page, as they relate to a specific step in the user’s journey. The segment(s) (Who section) must be the same for each page. Don’t forget to configure the targeting for each page. If one or several sections (Who, Where, How) have the same configuration, you can use the Replicate targeting option.

👉 To learn how to configure targeting, please read How to setup a campaign targeting.

Step 5: Traffic allocation

By default, traffic allocation is set equally for each variation (50/50 for an A/B test, 33/33/33 for an A/B/C, etc.). For statistical reasons, it is recommended to not make uneven traffic allocation.

👉 To learn how to configure Traffic allocation, please read Traffic allocation.

Step 6: Advanced options

The advanced options are not mandatory.

• Enable the third party tool(s) you have connected to AB Tasty to send your test data to your tool.

• Select a loading method for your campaign.

👉 To learn how to configure Advanced options, please read Campaign flow: Advanced Options.

Step 7: QA

The QA of the campaign is one of the most important steps before launching your campaign into production. The QA allows you to verify and test in real condition :

- the targeting configuration - the tracking - the modifications you've made

👉 To learn how to use the QA Assistant, please read QA Mode & QA Assistant.

If you want to launch your A/B Test at a specific hour on a specific day, and/or if you want to pause it at a specific hour on a specific day, see our guide on scheduling.

Use cases

Multipage tests can be used in the following cases:

🖊️ Action / modification	🎯 Goal(s)
Changing the color of the ‘Add to cart’ CTA, visible on product pages and list pages (quick buy)	Limiting anxiety of the CTA and easing the add to cart action.
Adding delivery fee information on different pages (every 5 items in the product list, in the product description of the product pages and as a banner in the cart page).	Monitoring the impact of giving more transparent information about delivery fees across the customer’s journey.
Replacing indoor pictures with outside photographs throughout the website.	Finding the best way to shoot your models regarding the appetence of your audience for real life photographs.