---
title: "How to A/B test a Sitecore form to optimize for conversions - Part 2"
description: "Part 2 of the Sitecore form A/B testing walkthrough: completing the variant setup and launching the test. TechGuilds covers steps four through six in detail."
canonical: "https://www.techguilds.com/blog/how-to-test-a-sitecore-form-part-2/"
type: "BlogPosting"
author: "Sana Kamalmaz"
publishedAt: "2020-03-05T05:00:00.000Z"
updatedAt: "2026-08-12T19:09:58Z"
source: "https://www.techguilds.com/llms.txt"
---

# How to A/B test a Sitecore form to optimize for conversions - Part 2

In part 1 of [How to A/B test a Sitecore form to optimize for conversions](https://www.techguilds.com/blog/how-to-test-a-sitecore-form-part-1), we walked through steps one through three, where we created a variation of the form and created a component test. In this part we'll continue to set the test parameters and start testing.

## Step four: Set the test parameters and start the test

- Upon saving the page in the previous step, you should see this message at the top of the page: “The item is in the ‘Awaiting Approval’ workflow state in the ‘_Demo_’ workflow. Approve with TestApproveReject

[Image: Test in draft]

Note: if you don’t see this message, try changing the workflow status of the page to draft in the **Content Editor** and refresh the page in **Experience Editor**

- Click **Approve with Test,** add a comment, and proceed to the **Preview and start test** dialog box

The **Preview** tab shows you the variations you have created to test

  - Select one of the variations to see a larger view of it
  - In the **My expected effect of changes** box, you can set that you expect a negative, no, or positive change to the engagement value due to the change you’re introducing in the test

The **Variables** tab shows a number of test parameters that you can control

  - **Variables in the test** shows the number of variables
  - **Experiences created** shows the total number of experiences/variations, the traffic allocated, and the confidence level
  - The **percentage of visitors exposed to test** is set to 100% by default. This means that by default, all visitors will participate in the test. If you have 2 experiences, your visitors will be split in half, 50% will see the first experience, and 50% will see the second
  - **Statistics** allows you to set the confidence level that you want to have in the test results. The higher the confidence level, the larger the sample needs to be and the longer the test will take (depending on your traffic)

[Image: Variables tab]

The **Objective** tab is where you define what you’re looking to improve by introducing the change, whether you want the winner to be selected automatically, and the maximum and minimum durations of the test

[Image: Objective tab]

At the top of the **Preview and start test** dialog box, there’s a message that tells you how many experiences you have, how many visitors you need to find the winning experience, and -based on historical traffic data- how long it will take to get this number of visitors.

[Image: Preview and start test box]

We will leave most things as they are in the **Preview and start test** dialog box, but we’ll change:

- In the **Preview** tab, under **My expected effect of changes**, set it to positive
- In **Objective** tab, under **Test objective**, select the goal that is associated with this form’s conversion. In this example I’d already created a goal that gets triggered when the form is submitted. It’s called ‘Free guide downloaded’. So, I’ll select it here and click **Start test**

You’ll know that the test has started when you see the following:

  - The optimization tab has a red dot next to it
  - There’s a message at the top of the page that says there’s an active test
  - The floating toolbar shows that there are variations of the form and you can toggle to see each

[Image: Test started]

And there you have it! You’ve created an A/B test to optimize a Sitecore form for conversions.

This is a simple scenario, where we tested changing the copy of the action button. That’s just one of a myriad of things that you can A/B test in a form.

In the next post, we’ll be looking at the results of a component test in Sitecore. Stay tuned!

In this series

[How to A/B test a Sitecore form to optimize for conversions - Part 1](https://www.techguilds.com/blog/how-to-test-a-sitecore-form-part-1) [How to A/B test a Sitecore form to optimize for conversions - Part 3](https://www.techguilds.com/blog/how-to-test-a-sitecore-form-part-3)