> 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/one-visitor-one-test-on-web-experimentation.md).

# One visitor One test on Web experimentation

## Activate One visitor One test Option on Web experimentation and Personalization

To enable this option, go to:

{% stepper %}
{% step %}
Go to : **Settings > Advanced Settings** 
{% endstep %}

{% step %}
Select **1 visitor 1 test option** 
{% endstep %}

{% step %}
Check the toggle to enable it.

* If you toggle on: a visitor will see only one experiment at a time.
* If you toggle off: a visitor can see more than one experiment.
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}

* Personalization and Patch scenarios are not affected and will continue to be displayed. 
* This option is compatible with the [Mutually Exclusive Experiment](/web-experimentation-and-personalization/campaign-creation-and-dashboard/mutually-exclusive-experiments-feature.md) feature. Consider that if you create several Exclusion Groups, then your visitors will only see one experiment across all the groups
  {% endhint %}

## How does the prioritization mechanism work?

* The tag evaluates eligible campaigns in ascending numerical order of their IDs.
* The first campaign where the visitor matches all targeting conditions is the one they are assigned to.
* There is no additional prioritization logic beyond this ID order.
* Suppose the visitor falls into untracked traffic for the first eligible campaign (i.e., not assigned due to traffic allocation). In that case, they may still be assigned to the next eligible campaign in the list.<br>

This mechanism works the same way on desktop and mobile browsers, as long as cookies are enabled.


---

# 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/one-visitor-one-test-on-web-experimentation.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.