> For the complete documentation index, see [llms.txt](https://docs.optibase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optibase.io/features/tests/what-is-a-variant.md).

# What is a Variant

*How to create an A/B Variant:* [Create an A/B Variant](/features/tests/create-an-a-b-variant.md)

*How to create a Split Variant:* [Create a Split Variant](/features/tests/create-a-split-variant.md)

A variant is an alternative version of something on your website — a section, component, or full page — that you test against your original to see which performs better.

Variants are the building blocks of A/B Tests and Split Tests in Optibase. You create them to test ideas, measure results, and improve conversion performance based on real user behavior.

***

### Why it matters

Variants help you move from guessing to knowing.

Instead of assuming what users prefer, you can test design, layout, or copy changes and let the data tell you what works best. Every variant is an opportunity to increase conversions, improve user experience, and reduce friction.

***

### Types of Variants in Optibase

#### A/B Test Variants (Variant Group

In an A/B Test, each variant represents a small change to a specific part of your page — without creating a new URL.

You can test things like:

* A new button color
* Updated headline text
* Reordered content
* Different image or icon

Visitors are randomly shown one of the variants. You track which version leads to more conversions.

**Main Variant**

The Main Variant is the original version of the page in an A/B Test. It’s:

* The default version shown when the test is in Draft
* The fallback when a test is restricted by geo, browser, or device rules

> *Example: You create a Main Variant with a red “Get Started” button and a Variant A with a blue one. Optibase will show one or the other to users and track which leads to more signups.*

***

#### Split Test Variants (URL-Based)

In a Split Test, each variant is a completely separate Webflow page with its own URL.

This type of test is best when you want to compare:

* Entirely different layouts or designs
* Alternative landing pages
* Separate page flows or structures

Users are randomly directed to one of the variant URLs, and Optibase tracks which page performs better based on your conversion goals.<br>

**Entry Variant**

The Entry Variant is the primary page that acts as the entry point for your Split Test. It works like this:

* If a user lands on the Entry Variant URL, Optibase decides whether to keep them there or redirect them to another variant
* If a user lands directly on a non-entry variant (e.g. from a paid ad), no redirection occurs — the test still tracks performance

> *Example: You create two landing pages with different content structures. The Entry Variant is your main campaign page. Visitors might be redirected to the alternate version based on test settings.*

### Summary: A/B vs Split Variants

| Scope              | One section or element | Full page (different URLs) |
| ------------------ | ---------------------- | -------------------------- |
| Setup location     | Within the same page   | Across separate pages      |
| Main/Entry variant | Main Variant           | Entry Variant              |
| Use case           | Test small changes     | Compare different layouts  |

### Tips for Working with Variants

* Name your variants clearly so you can track what was tested
* Only test one change per A/B Test for clean results
* Use Split Tests when your changes affect the whole user journey
* Set clear conversion goals before publishing a test
* Start simple — don’t overcomplicate with too many variants

***