> 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/split-url-test.md).

# Split URL Test

Umbraco Engage enables running A/B tests on different versions of a page.  This article covers how and when to use this type of test.

Split URL testing in Umbraco Engage allows you to compare different versions of a page to see which one performs better.

To set up a Split URL test, you must create multiple versions of a page. Each version can have different designs, text, or buttons based on the options setup in Umbraco.

You can start a Split URL test from the [Engage section](/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-section.md). The type is selected in the **Test setup** section.

![Split URL Test](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-b9d2fc5071b589637959d0d0eee1320fad63ad17%2Fsplit-url-test.png?alt=media)

When you set up the A/B test, you can send 50% of visitors to page A and 50% to page B. This way, you can see which page helps achieve the goal of the test better.

Split URL tests are particularly useful for optimizing elements like checkout workflows, where small changes can impact conversions.


---

# 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/split-url-test.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.