> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests.md).

# Types of A/B Tests

Get an overview of the available types of A/B tests you can run with Umbraco Engage.

Four different types of A/B tests are available:

* [Single-page tests](/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/single-page-ab-test.md) to test a specific page within Umbraco.
* A way to test [multiple pages](/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/multiple-pages-test.md) at the same time.
* Test an entire [Document Type](/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/document-type-test.md) and all of the pages using this type.
* [Split URL testing](/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/split-url-test.md). This enables you to select two or multiple pages and serve one of these URLs per visitor.

The A/B tests are set up within an Umbraco context. You can reuse properties that are already created. Umbraco Engage is also aware of the structure of your website and concepts like Document Types.

When setting up the A/B test, you can select the type of test you want to set up.

![When you set up an A/B test you have to choose which type of test you want to use.](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-4911c3aa16c3f271e9897d90e77931049b474ff0%2FABTest-SetupTest-v16.png?alt=media)

A Single-Page test can only be started in the A/B test [Workspace View](/umbraco-engage/marketers-and-editors/introduction/workspace-views.md) and not from the Engage [section](/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-section.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.