---
title: "Configure A/B/n test settings"
slug: "configure-a-b-n-test-settings"
abstract: "How to configure the goal of an A/B/n test before you set it live, and adjust other test settings, such as traffic assignment, allocation, and sample size calculations."
---

# Configure A/B/n test settings

If you don't want to use the default test values, you must configure your goal and adjust the test settings before [you start running an A/B/n test](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/get-started-with-a-b-n-testing/start-an-a-b-n-test.html "Start an A/B/n test"). These settings define how the [A/B/n test](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/a-b-n-testing.html "A/B/n testing") runs and can impact the accuracy of your test results.

## Access the settings

You can manually access the test settings to configure your goal and other parameters. If you start a test without making the required configurations, you will be prompted to edit them first.

To access the test settings:

1. In the Page builder **Editor** mode, open the page that contains the A/B/n test you want to edit.
2. In the right-hand pane, click **Configure**.

    ![Click Configure in the right-hand pane to access the test settings.](https://doc.sitecore.com/api/markdown-image/sai/en/users/sitecoreai/images/Configure.png)

3. In the **A/B/n test settings** dialog, [configure your goal](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/get-started-with-a-b-n-testing/configure-a-b-n-test-settings.html#configure-the-goal "Configure the goal") and [assign traffic](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/get-started-with-a-b-n-testing/configure-a-b-n-test-settings.html#assign-traffic-to-variants "Assign traffic to variants") to your variants. You can make any necessary changes in the **Optional configuration** section to avoid using default values.

## Configure the goal

Sitecore uses the [goal](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/get-started-with-a-b-n-testing/a-b-n-test-hypothesis-and-goal.html "A/B/n test hypothesis and goal") metrics of an A/B/n test to assess the performance of each variant and determine the winner. To start your A/B/n test, you must configure the goal of your test by indicating the pages where the goal should be tracked.

To configure the goal:

1. In the **A/B/n test settings** dialog, you'll see the name of your test. To edit it, enter the new name in the field provided.

    In the **Configure test goal** section, click on the goal you want to track.

    ![Choose the goal of your test in the A/B/n test settings dialog.](https://doc.sitecore.com/api/markdown-image/sai/en/users/sitecoreai/images/ConfigureGoal.png)

    The following goals are available:

    - **Increase page views** to measure the views of one or more other pages of the site.
    - **Increase form submissions** to measure submissions for the specific form component being tested.
        > [!note]
        > The **Increase form submissions** goal is available only for tests of a Sitecore Form component. It appears when either of the following conditions is met:
        > - The tested rendering contains the `ComponentName` rendering parameter with the value `SitecoreForm?formId=....`
        > - The tested rendering uses the Sitecore Form wrapper ID 62DD1639-9F28-4040-8738-C886480B2127.
        > 
        > This goal is not available for general page tests or non-form components.
    - **Decrease bounce rate** to measure the percentage of visitors who enter a specific page on a website and then leave without continuing to view other pages.
    - **Decrease exit rate** to track how many visitors leave your site from a specific page, after navigating through other pages.
2. If you selected the **Increase page views** goal, you must specify one or more pages where you want to track the goal: in the **Site tree** section, click :mdiChevronDown: and select one or more pages from the drop-down menu.

    > [!note]
    > The goal-tracking pages you selected must be published in order to [start the test](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/get-started-with-a-b-n-testing/start-an-a-b-n-test.html "Start an A/B/n test").

3. Click **Save**.

## Assign traffic to variants

You can adjust the default traffic percentages while your test is in *Draft* status. By default, if your test includes only two variants, Sitecore splits the traffic equally, assigning 50% to Variant A (Control) and 50% to Variant B. For any additional variants, the default traffic assignment is 0%.

To assign traffic to variants:

1. In the **A/B/n test settings** dialog, click **Assign traffic**.
2. Enter the traffic percentage for each variant using whole, rounded percentages. Each variant must have at least 1% traffic assigned, and the total percentage for all variants must equal 100%.

    ![Set the percentage of traffic assigned to each variant.](https://doc.sitecore.com/api/markdown-image/sai/en/users/sitecoreai/images/AssignTraffic.png)

3. Optionally, if you have more than two variants and want each variant to automatically receive an equal share of traffic, click **Evenly distribute**. For example, if you have Variants A, B, and C, the traffic percentages will be split into 34%, 33%, and 33%, respectively.
4. Click **Save**.

## Set automated actions based on the test outcome

You can make the changes to the default automated actions while your test is in *Draft* status. By default, Sitecore selects what happens after your test reaches [statistical significance](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/test-metrics-and-calculations.html#statistical-significance "Statistical significance") based on the test outcome.

You can start your A/B/n test without changing the default automated actions.

To set automated actions based on the test outcome:

1. In the **A/B/n test settings** dialog, in the **Optional configuration** section, click **Automated actions**.

    By default, the A/B/n test is configured to assign all visitor traffic to the winner if there is one, or to keep running the test if the results are inconclusive.

    ![Select the actions you want to happen automatically after your A/B/n test reaches statistical significance.](https://doc.sitecore.com/api/markdown-image/sai/en/users/sitecoreai/images/Oncompletionactions.png)

2. Select the action you want to happen automatically after your A/B/n test reaches statistical significance, based on the outcome.
    - If there is a winning variant:
        - **Assign all the traffic to the winning variant** - to redirect all visitor traffic to the best-performing variant.
        - **Assign all the traffic back to the control variant** - to redirect all visitor traffic back to Variant A (Control).
    - If the test results are inconclusive:
        - **Keep running the test** - to maintain the current traffic assignment and continue the A/B/n test.
        - **Assign all the traffic back to the control variant** - to redirect all visitor traffic back to Variant A (Control).
3. Click **Save**.

## Edit the advanced options

You can make the changes to the default values in **Advanced options** while your test is in *Draft* status. By default, Sitecore sets the percentage of visitor traffic to include in your A/B/n test and the [minimum sample size](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/test-metrics-and-calculations.html#minimum-sample-size "Minimum sample size") required for each variant.

You can start your A/B/n test without changing the default values in **Advanced options**.

To edit the advanced options:

1. In the **A/B/n test settings** dialog, in the **Optional configuration** section, click **Advanced options**.

    By default, Sitecore allocates 100% of visitor traffic to the A/B/n test and calculates a minimum sample size of 21,110 visits per variant, required to achieve [statistical significance](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/test-metrics-and-calculations.html#statistical-significance "Statistical significance").

    ![Set the test traffic allocation and adjust the minimum sample size in the Advanced options section.](https://doc.sitecore.com/api/markdown-image/sai/en/users/sitecoreai/images/AdvancedOptions.png)

2. To edit the default traffic allocation, adjust the percentage of overall visitor traffic you want to include in the test, between 1% and 100%. For example, setting this to 20% means that only 20 out of 100 visitors will participate in the test.
3. To edit the default minimum sample size, edit the following fields:
    - **[Base rate](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/test-metrics-and-calculations.html#minimum-sample-size "Minimum sample size")** - the current conversion rate of the control variant, set at a default of 2%. This rate can be set between a minimum of 0.5% and a maximum of 50%. Increasing the base rate decreases the required minimum sample size.
    - **[Minimum detectable difference](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/test-metrics-and-calculations.html#minimum-sample-size "Minimum sample size")** - the smallest amount of change from the Base rate that you want the test to detect, set at a default of 20%. This can be set between a minimum of 1% and a maximum of 50%. Increasing this value decreases the required minimum sample size.
    - **[Confidence level](https://doc.sitecore.com/sai/en/users/sitecoreai/a-b-n-testing/test-metrics-and-calculations.html#minimum-sample-size "Minimum sample size")** - the level of certainty required to determine that the differences observed between variants are statistically significant and not due to chance. The default level is 95%, but this can be set between a minimum of 80% and a maximum of 99%. Increasing the confidence level increases the required minimum sample size.
4.  To revert the sample size parameters to their default values, click **Reset to defaults**.
5. Click **Save**.

## Configure audience targeting

By default, an A/B/n test is shown to all site visitors. Audience targeting lets you restrict the test to a specific audience so that only visitors who meet your defined conditions are included in the test and randomly assigned to a component variant. Visitors who do not match the audience conditions are not exposed to the test.

You can configure audience targeting while your test is in *Draft* status.

To configure audience targeting for an A/B/n test:

1. In the **A/B/n test settings** dialog, in the **Optional configuration** section, click **Audience targeting**.

    By default, all site visitors are included in the A/B/n test.

2. Click **Configure audience**.
3. In the **Configure audience targeting** modal, click **Add condition** and do one of the following in the right-hand pane:
    - Select an existing custom or [out-of-the-box condition](https://doc.sitecore.com/sai/en/users/sitecoreai/personalize/specifying-variables-for-conditions.html "Specifying variables for conditions").
    - Click **Create** to [build a new custom condition](https://doc.sitecore.com/sai/en/users/sitecoreai/personalize/create-a-custom-condition/create-a-custom-condition.html "Create a custom condition").
4. On the **Build** tab, specify the details of the selected condition.

    For more information about the available conditions and their details, see [Condition templates](https://doc.sitecore.com/sai/en/users/sitecoreai/personalize/specifying-variables-for-conditions.html "Specifying variables for conditions").

5. Optionally, do the following:
    - To add more conditions, click **Add condition** and repeat the previous steps.
    - [To create a group of conditions](https://doc.sitecore.com/sai/en/users/sitecoreai/personalize/work-with-condition-groups.html "Work with condition groups"), click **Add group**.
    - To move a condition or group of conditions higher or lower in the list of conditions, click the up :mdiArrowUp: or down :mdiArrowDown: arrow on the right-hand side of the condition.
6. When you have finished configuring the audience, click **Preview** to view the conditions in an easily readable format and in the [order](https://doc.sitecore.com/sai/en/users/sitecoreai/personalize/understanding-the-order-of-operations-in-conditions.html "Understanding the order of operations in conditions") they are evaluated.
7. On the **Build** tab, click **Save**.
8. In the **A/B/n test settings** modal, click **Save**.

When the A/B/n test is live, it runs only for visitors who meet the defined audience conditions. These visitors are randomly assigned to one of the test variants. Visitors who do not match the audience are excluded from the test and always see the original component on the page.