> For the complete documentation index, see [llms.txt](https://swtchd-io.gitbook.io/swtchd.io-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swtchd-io.gitbook.io/swtchd.io-docs/testing-and-tracking/set-up-a-test.md).

# Set up a test

### Step 1: Add your page versions

Paste the URLs of the versions you want to test.

* Free: 2 versions
* Pro: up to 8 versions

### Step 2: Generate tracking links

You can do one or both.

#### Link tracking

* Paste the outbound links you want to track (one per line).
* Click **Generate Tracking Links**.
* swtchd returns a unique tracking link for each version.
* Use the generated tracking links in each version’s button URLs.

#### Form submit tracking (thank-you page)

* Add a title + description for a thank-you page.
* Click **Generate Tracking Links**.
* swtchd generates tracking links per version.

Use these links as your form’s “redirect after submit”.

### Step 3: Review & launch

Launch the test once links are generated.

Traffic is split evenly across your versions.

Note: Your tracking link will all remain accessible from the analytics section.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://swtchd-io.gitbook.io/swtchd.io-docs/testing-and-tracking/set-up-a-test.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.