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 a 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 .

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

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

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

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 .

👉 To learn how to configure targeting, please read .

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 .

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 .

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 .

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

Use cases

Multipage tests can be used in the following cases:

A redirect test (or split test) enables you to test the performance of a new page, created and hosted outside of AB Tasty. This page is used as a variation within an A/B test campaign.

This type of test is useful when modifications involve a significant amount of work (e.g.: a brand-new design).

In this case, 2 URLs are involved:

• The source URL, that is to say the one corresponding to the original version. This is the URL from which you want your visitors to be redirected.

• The destination URL, that is to say the new page used as a variation. This is the page the visitors will be redirected to when they land on the source URL.

As in a classic A/B test, after analyzing the results of your test, you will see if the destination URL has performed better than your original version depending on the goal you wanted to reach (e.g., increasing the number of clicks, the number of pages viewed, decreasing the bounce rate).

A Split Test is a type of A/B test. To create a Split Test, you must create an A/B test (go to Web Experimentation, click the Create button and select A/B Test) and activate the Redirection option from the visual editor.

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

Configuration

Step 1: Main information

The Main Information page is the first step toward your new Split 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 URL field, enter the URL you want to load in the editor. This URL corresponds to the source URL. It’s important if you want to set up trackings on this page, such as action trackings.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

To run a Split test, you don’t need to create any specific content. The objective of this setup is to use the classic A/B test campaign workflow to activate a redirection of traffic from the former page (the original) to the new one(s) (the variations).

Variation 1 corresponds to the redirect page. To create the redirection, click on Variation 1 in the header navigation and select the redirect option. You can then paste the URL of the page you want to redirect to in the popin.

We recommend ticking the following boxes:

• Check the accessibility of the page - This option automatically pauses the test when the redirected URL is no longer online (with an email alert to the admins of the account). Once your landing page is available again, another email will be sent and you will be able to play the test again.

• Keep AT Internet referrer in URL - If you use AT internet, this will ensure that you keep the original URL.

• Enable redirection - This option allows AB Tasty to perform the redirection. You must select it. If you want to redirect to several pages, you can select the Regular expression option and enter the regular expression in the URL field.

In a redirected variation, you cannot add Variation JavaScript or make changes. Turning an existing variation (with changes) into a redirection variation deletes all the changes. Only action trackings can be added as they are not specific to a single variation but to the whole campaign.

👉 To learn more about the redirection option of the visual editor, please read the

Step 3: Goals

As primary and/or secondary goals, you can choose action trackings which are common to the original variation and to the new page. For example: if your Split Test consists of testing a new landing page layout, your primary goal should be the bounce rate, along with optional secondary goals.

As the URL of the original version of your page is different from its variations, the code will probably be different. If you want to track clicks on the main CTA of both pages, follow these steps:

• First, add action tracking to the original page. You can access the original page in the editor – it’s displayed by default in the Original tab in the top banner of the visual editor. As with every tracker, AB Tasty will try to detect the presence of the tracked element in both the original and the variation pages, even if this element is present on only one of the two.

• Next, do the same for the variation you want to test. If you return to the Variation tab, you will see the original version of your page – that’s normal; it’s because you’ve used this URL in the Main Information Page. To load the new one, go back to the Main Information Page and paste the new URL in the field named URL to load in the editor, and click save. Then go back to the editor. Your new page will be loaded in the Variation tab.

For the most efficient workflow in setting up an A/B test, list all your metrics and their trackers on a separate sheet or document (for example metric “click rate”, so tracker “click tracking on the element #mainCTA). Then implement all the trackers in the original variation, before finally implementing them all in the variation. Each time, you can copy and paste the tracker names from the list, to ensure none are overlooked and your associated metrics will have the same names. This is necessary to ensure all relevant data is collected under the same KPI in your campaign report.

👉 To learn how to configure Goals, please read .

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.

You must target the source URL.

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

Traffic allocation must be identical for each variation.

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

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.

• Activate Sequential testing to detect if your experiment will not be successful at all based on the results of your primary goal (if it is based on a Conversion/Transaction Rate).

👉 To learn how to configure Advanced options, please read .

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 .

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

If the AB Tasty tag is not implemented on the page which you want your visitors to be redirected to, they will be able to view the page but no data will appear on the reporting of your campaign.

An A/B Test consists of modifying one element on one page (e.g. homepage, basket page, etc.) or a string of equivalent pages that share the same layout (e.g. all of your product pages, all of your results pages, etc.), and measuring if the new variation(s) will be more or less performing than the original.

To learn more about the differences between each type of test, refer to the Types of campaigns article. If you don’t know which type of campaign to choose, our virtual assistant Ally can help you.

To create an A/B test, go to Web Experimentation, click the Create button and select A/B 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 A/B 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.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

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

With the visual editor

With the Visual Editor, you can make simple modifications such as changing the color of a button, replacing an image, changing the wording of an element. If it is clickable, always put an action tracking on the element you modify.

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

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 .

Step 3: Goals

As the primary goal enables you to determine which variation takes precedence over the others, you should choose the action tracking related to the element you have modified. Indeed, it is the user behavior that is more likely to be affected by the modification you have made in the editor.

👉 To learn how to configure Goals, please read .

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.

Be careful when entering the targeted pages (in the Where section) of your test to ensure that it will display correctly on the pages you want to target (e.g. Product pages).

👉 To learn how to configure targeting, please read .

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 .

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.

• Activate Sequential testing to detect if your experiment will not be successful at all based on the results of your primary goal (if it is based on a Conversion/Transaction Rate).

👉 To learn how to configure Advanced options, please read .

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 .

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

Use cases

A/B tests can be used in the following cases:

An A/A test is a type of campaign that enables you to gather insights about your website by tracking events or specific behaviors using the AB Tasty tag.

This is a type of test for which:

• The traffic allocation is 0% on the original version and 100% on the variation.

• The variation is empty: you don’t create any new content to push, so the campaign is totally transparent for your visitors.

• You have set up goals to follow in the reporting.

So, what’s the point of an A/A Test?

• Gathering baseline data: All market analytics tools track events differently (technologically and also in the way they calculate certain metrics). Thus, it’s normal to observe differences between the metrics displayed by two different analytics tools. With an A/A Test, you can collect your visitors’ main KPIs using AB Tasty and establish a baseline to analyze your future campaigns more accurately.

• Analyzing before and after revamp: If you’re planning a large revamp of an important feature on your website and can’t A/B test the two versions, it’s important to have a record of the previous performance of this feature. For example, let’s say you want to change the structure of your navigation bar. If you launch an A/A Test before the release, you’ll get the exact click rates for each tab. After the revamp, another A/A Test will enable you to collect the new click rates on the new tabs and, after several weeks, you’ll be able to measure the impact of your release on the navigation behavior.

• Adding click zones or segment performance:

To learn more about the differences between each type of test, refer to the article. If you don’t know which type of campaign to choose, can help you.

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

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

Configuration

Step 1: Main information

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

👉 For more information on how to configure this step, refer to .

Step 2: Editor

As the A/A test objective is not to change content of your website but to gather data and insights, you can still use the Visual Editor but only to create trackers.

In the Editor, you can add trackers to your campaign, such as click trackings, custom trackers and widget trackers.

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

Step 3: Goals

Once you’ve set up your trackers, you can preconfigure your future reporting to easily identify the metrics needed to track your primary goal. The notions of primary and secondary goals are not significant with A/A Tests because the objective here is to recall all the trackers you’ve set-up in the editor.

Once your campaign has started, you can add secondary goals, but action tracker such as clicks or widgets won’t be retroactive in your reporting and will be calculated from the date you added these metrics as goals. All the other goals will be calculated from the date you launched your A/A Test, even if you add them afterward.

By default, A/A Test will embed some goals like:

• Transaction Goal

• Bounce Rate

• Number of pages viewed

• Revisit Rate

The Transaction Goal will be set as the Primary Goal if you have a transaction tag implemented. If not the bounce rate will.

👉 To learn how to configure Goals, please read .

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. However, you can't change WHEN visitors will see the campaign depending on the recurrence as the A/A test will be instantly trigger.

Be careful when entering the targeted pages (in the Where section) of your test to ensure that it will display correctly on the pages you want to target (e.g. Product pages).

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

By default, traffic allocation it is locked to 100% of your traffic to the variation.

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

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 .

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 tracker you applied 👉 To learn how to use the QA Assistant, please read .

If you want to launch your A/A 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

A Patch or Multipage Patch consists of modifying:

• One or several elements on one page (for example, your homepage, basket page, etc.) or several pages that share the same layout (all your product pages or all your results pages, etc.).

• One or several elements on different pages (for example, your homepage, basket page, etc.) or several pages that share a different layout (all your product pages and all your results pages, etc.).

Patching your website means changing a piece of code to correct an error or to push out an important piece of content or information as soon as possible.

The objective of patching is not experimental or personalization, but only to make a very fast change to a page of your site to fix an error or update something urgent. Therefore, you don't have to set up Goals and it does not generate any reporting.

A patch campaign:

• is always pushed to all of your audience – you can’t choose a specific segment.

• is always pushed to 100% of your traffic.

• can’t be analyzed as it does not generate any reporting.

• can tell you how many unique visitors have been exposed to the patch (this data is pushed directly to the dashboard).

To learn more about the differences between each type of test, refer to the article. If you don’t know which type of campaign to choose, can help you.

To create a Patch or Multipage Patch, go to Web Experimentation, click the Create button and select Patch or Multipage Patch.

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

Configuration

Step 1: Main information

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

We recommend adding a description to your campaign to add useful information you want to share with your team. For example: “This patch will fix a typo error on product # 447 158”. In the URL field, enter the URL you want to load in the editor.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

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

With the visual editor

The visual editor enables you to manage your Patch by adding or removing new variations, creating visual modifications, or adding action tracking (click tracking) to record the performance of the elements you’re about to challenge.

You can’t add trackings because patch campaigns have no reporting and are aimed at following performance.

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

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 .

Step 3: Targeting

By default, a patch is displayed to your whole audience, that’s why you can’t change the WHO section when targeting a patch.

👉 To learn how to configure targeting, please read .

Step 4: Advanced options

The advanced options are not mandatory.

• Select a loading method for your campaign.

👉 To learn how to configure Advanced options, please read .

Step 5: 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 modifications you've made

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

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

In AB Tasty, you can display campaigns even if your visitors have not yet given their consent. For patch campaigns, no data is collected but, by default, they are displayed only when the visitor has given their consent. To display patches to all visitors including those who have not yet given their consent, go to Settings > Cookies > Cookie deposit and check the Patch box. For more information, refer to .

Use cases

Use case 1: Creating a patch from scratch

You can create a patch from scratch, for example:

• To correct a typographical error

• To modify a legal mention

• To add a health message

• To hide a CTA (e.g.: when experiencing a stock shortage)

Use case 2: Transforming a winning test variation into a patch

To transform a winning test variation into a patch, apply the following steps:

1. From the dashboard, hover over the test you want to use as a reference for your patch.

2. Click and Duplicate.

3. Choose Patch from the first dropdown menu.

4. Choose the variation you want to push to 100% of your users (the winning one) and validate: Your patch appears in the test dashboard.

Your campaign set-up is imported from the source test but you can add or modify information if needed. Make sure you have a description of your patch campaign.

You can also duplicate the winning variation of a multipage test into a patch. In this case, you must create one patch per page as this type of campaign does not allow you to have several pages.

If you are in need of inspiration or looking to accelerate your ideation process Evi Ideas is here to help. Evi Ideas is a feature designed to help you generate experiment ideas using AI.

Using generative AI CRO Experimentation Expert Agent, continuously improved to provide best practices, UX guidance, and cognitive bias considerations, Ideas Generator, provide relevant and actionable test ideas from an image or Gif.

Here’s how it works:

A Multivariate test enables you to test combinations of changes simultaneously on your website. You can change several elements on a page simultaneously (e.g., the color and wording of a CTA) and identify which of the possible combinations performs 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. Unlike an A/B test, which involves testing each hypothesis in a different test, a multivariate test allows you to run hypotheses at the same time and to find the best combination of all. The purpose of multivariate tests is to measure the interactive effects between several supposedly independent elements (e.g. page title and visual illustration). A subtest contains variations that will be tested independently across multiple combinations. For example, if your goal is to test a simple CTA, you might want to create three subtests: Color, Shape, Wording, with as many variations of colors, shapes and wordings as necessary. AB Tasty will create all the possible combinations and display them randomly to your traffic.

To learn more about the differences between each type of test, refer to the Types of campaigns article. If you don’t know which type of campaign to choose, our virtual assistant Ally can help you.

To create a Multivariate test, go to Web Experimentation, click the Create button and select Multivariate Test.

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

The number of combinations created is calculated as follows: [Number of variations of the 1st subtest]*[Number of subtests]. The more subtests with variations you configure, the more traffic you need to allocate the different combinations. In this case, the readiness of your campaign and data reliability takes more time to be reached than a classic A/B test.

Configuration

In Multivariate Tests, you can’t add goals with our standard goals setup step - it is not available for this type of test. Only the transaction goal is available and preselected. This is also why, in the editor, you can't add action trackings or tracking widgets.

Step 1: Main information

The Main Information page is the first step toward your new Multivariate 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.

By default, only one subtest is created, but you can add as many subtests as necessary. For each subtest, enter the URL you want to load in the editor. In most cases, you must enter the same URL for all subtests.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

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

With the visual editor

For each subtest, you can add as many variations as you want. For example, if your subtest one is related to the color of a button. In a variation 1, you can test the blue color and in a variation 2, a red color.

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

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 .

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

Step 3: Targeting

Be careful when entering the targeted pages (in the Where section) of your test to ensure that it will display correctly on the pages you want to target (e.g. Product pages). To trigger the test only for visitors using a specific device, use the Device criterion in the triggers section. When the Who, How and Where sections have the same configuration for each sub-test, you can use the .

👉 To learn how to configure targeting, please read .

Step 4: Traffic allocation

All users must be tracked. Each percentage of the targeted traffic is assigned to a subtest.

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

Step 5: 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 .

Step 6: 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 .

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

Use cases

Multivariate tests can be used in the following cases: