> For the complete documentation index, see [llms.txt](https://docs.caraml.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caraml.dev/user-guides/01_getting_started-1/07_running_experiments.md).

# Running Experiments

Experiments can be run using [routers](https://github.com/caraml-dev/turing/blob/main/docs/concepts.md) or independently.

Based on the segmenters enabled for the project and the experiment variables mapped to them (in the project's settings), all the variable(s) must be provided in the fetch treatment request body. For each segmenter below, one of the specified (group of) variables can be configured in the project settings and subsequently, included in the fetch treatment call.

| Segmenter        | Fetch Treatment Input (One of)  |
| ---------------- | ------------------------------- |
| S2ID             | `s2id`, `(latitude, longitude)` |
| Days of the Week | `tz` (timezone), `day_of_week`  |
| Hours of the Day | `tz` (timezone), `hour_of_day`  |

## Running Experiments with Turing Routers

When deploying a Turing router, the experiment engine can be configured to 'Turing Experiments'. For more information, check [Turing - Creating a Router](https://github.com/caraml-dev/turing/tree/main/docs/how-to/create-a-router).

## Running Experiments with API

Experiments can be run independently using the POST endpoint (See details on the Treatment Swagger, in [Getting Started](/user-guides/01_getting_started-1.md)), with the required segmenter values and randomization unit (which may be optional for some Switchback experiments) in the request body.


---

# 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://docs.caraml.dev/user-guides/01_getting_started-1/07_running_experiments.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.