> 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/flagship-deprecated/api-keys-and-settings/visitor-experiment-option.md).

# visitor experiment option

If you are running several experiments at once on your site or application, a visitor will see each of them, which may influence the results, since one experiment can impact the results of another.

To avoid this, we offer an option that enables you to display only one experiment per visitor, even if there are several running.

To enable this option, click "Settings" in the menu, then select "Environment & Security" and under the "1 visitor 1 test" section, toggle the option "I want my users to be assigned only one experiment at a time" on.

![mceclip0.png](/files/RTcsLbmhbJRcHbJ6cuXR)

* If you toggle the option on: a visitor cannot see more than one experiment.
* If you toggle the option off: a visitor can see more than one experiment.

| ![](https://flagship.zendesk.com/hc/fr/article_attachments/206687118/FontAwesome_f0a4_1__512.png) | This option is only available for Decision-API for now. If you implemented Flagship using bucketing, don't panic, it's on our roadmap to manage it too. |
| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |

This option only affects Experiments (A/B Test). All Personalization and Feature management scenarios will continue to work as expected.

| ![](https://flagship.zendesk.com/hc/fr/article_attachments/218021027/eclair.png) | <p><strong>If you activate this option while two experiments are active (an experiment on your home page and a second experiment on the cart page), all visitors who see the home page before the cart page will only see the home page experiment. The quantity of traffic that may be allocated to the cart experiment will therefore be significantly reduced. This option may increase the time required to obtain enough statistics on an experiment targeting a page or a screen located deeper in the site/app (product pages, conversion tunnel, form confirmation page, etc.).</strong><br></p> |
| -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


---

# 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/flagship-deprecated/api-keys-and-settings/visitor-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.
