> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/account/technical-implementation/one-visitor-one-experiment-option.md).

# One visitor One experiment option

Suppose you are running several experiments at once on your site or application. In that case, a visitor will see each of them as soon as they enter the targeting, which may influence the results, since one experiment can impact the results of another.

To avoid this, we offer an option that allows you to display only one experiment per visitor, even if multiple experiments are running.

Learn more about this option (activation and prioritization rules) in our dedicated articles:

:point\_right: [1 visitor 1 test for Web experimentation](/account/technical-implementation/one-visitor-one-experiment-option/one-visitor-one-test-on-web-experimentation.md)

:point\_right: [1 visitor 1 test for FE\&R](/account/technical-implementation/one-visitor-one-experiment-option/one-visitor-one-test-on-fe-and-r.md)

{% hint style="warning" %}

* If you activate it while you have active experiments, it might create biases in your campaign results. We advise you to end all pending tests before enabling the option and launching new ones.
* Activating this option while conducting two experiments (one on your home page and another on the cart page) impacts traffic distribution. Visitors who view the home page before the cart will only experience the home page experiment, reducing traffic allocation for the cart experiment. Consequently, gathering adequate statistics for experiments on deeper pages (like product pages or conversion funnels) will take longer.
  {% endhint %}


---

# 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.abtasty.com/account/technical-implementation/one-visitor-one-experiment-option.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.