# 1 Visitor 1 Experiment

When running multiple experiments simultaneously on your site or application, visitors may be exposed to several experiments at once. This can impact results, as experiments may influence each other.

To prevent this, Feature Experimentation and Rollout lets you limit each visitor to **one experiment at a time**, even when multiple experiments are running.

### Where to find the 1 Visitor 1 Experiment Option

<figure><img src="/files/A7d8lwr0wgUgoDDGT7pe" alt=""><figcaption></figcaption></figure>

You can configure the Visitor Experiment Option at the environment level:

**Settings → Feature Experimentation →** [**Environment Settings**](https://app2.abtasty.com/settings/feature-experimentation/environment)

This option applies to all Feature Experimentation campaigns running in the selected environment.

#### 1 Visitor 1 Experiment enabled &#x20;

When this option is set to `true`, a visitor can be exposed to **only one experiment at a time**.

If multiple experiments are running, the visitor is assigned to the first eligible experiment they encounter, and will not be exposed to any other experiment.

{% hint style="info" %}
This option only affects **A/B campaigns**.

All **Personalization** and **Feature Toggle** campaigns continue to work as expected.
{% endhint %}

#### 1 Visitor 1 Experiment disabled&#x20;

When this option is set to `false`, visitors may be exposed to **multiple experiments** during their journey.

This is the default behavior when no limitation is applied.

#### Important considerations

{% hint style="warning" %}
**Decision API only**

This feature is only available with **Decision API**. Bucketing-based implementation, are not supported.
{% endhint %}

{% hint style="warning" %}
**Impact on Traffic distribution**

Enabling this feature affects experiments on different pages.

**Example:** If you have experiments on the home page and cart page, visitors who land on the home page first will only see the home page experiment. They won't be included in the cart page experiment.

**Result:** Experiments on deeper pages (product pages, checkout steps, confirmation screens etc.) receive significantly less traffic, requiring more time to reach statistical significance.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/sdk-and-environments/managing-environments/1-visitor-1-experiment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.