With A/B testing - also known as split testing - you can compare two versions of a project in order to determine which one performs better. This is done by randomly showing one version to a group of users and the other version to another group of users, and then analyzing the results to see which version had a higher completion rate.

To conduct an A/B test, you first need to choose a project, and then the changes you want to test. This could be different Headers, Images, a Button, or any other elements on your project.

You can have the initial iteration of the project as the control (the original version), and the duplicate project as the variation (the modified version) - we usually recommend duplicating the original project and making the changes on the duplicate, that way you won't have to recreate the whole project from scratch.

The duplicate project will be a draft, so make sure to publish it once you've made the necessary changes and want to start A/B testing. Rest assured, you can still edit your projects and make changes to them even after they have been published.

While in the dashboard area, head over to the "A/B Tests" tab on the navbar.

Then click the button "+ Create new A/B test" and give your test a name - this helps to keep things organized if you're running multiple tests at the same time.

On the next page, you'll be able to edit the following settings of the A/B test you just created:

On this same page where you can edit the test's settings, you'll also have the option "Show the same project upon refresh during the same session" which you can enable.

Checking this option will make so that the project the user initially got will remain the same one, regardless if they reload the page, or use that same URL to open the project in a new page.

Once you're done setting things up, it will be time to select the two projects you want to A/B test. Start by making sure that the two projects you want use on the test have been published, then simply pick your project A and project B from the respective dropdowns, and click "➡️ Start A/B Test" once you're ready.

Once the test is running, you can track and analyze the following metrics:

After a sufficient amount of data has been collected, you can determine which version of the project performed better and mark it as the winner. The more data you have, the better.

You can also click on your project's name while the test is running, and this will take you to that project's Analytics page. This is separate from A/B Testing however, and you can read more about it here.

This is an especially important step when doing A/B testing. The reason for this is that if you use the URL or embed code from your project's "Share & Embed" page, you'll just be sharing that one project - so you won't be making use of the A/B test that you just set up.

Instead, you'll need to use the URL/embed code that are provided to you on the "Share your A/B Test" page:

The page looks similar to the "Share & Embed" page, but it allows you to share the test you just created, and it is accessible by clicking the "Share your A/B Test" button.

You can also just copy the URL (see above screenshot) and share it, if you're not planning to embed the test.

If you do decide to embed your test however, then the process is the same as embedding a normal project. For more information about embedding, make sure to check out our dedicated article here.

If you still have any questions about this feature that are not covered in the article, feel free to contact support.