# Mutually Exclusive Settings {% hint style="info" %} Mutually Exclusive Settings can be created and managed separately in the Production Environment and the Development Environment. {% endhint %} ### Overview In general, even when multiple tests run simultaneously, each test is distributed independently.\ For example, if two tests, Test 1 and Test 2, run simultaneously, assignments such as (Test 1: A, Test 2: A) and (Test 1: A, Test 2: B) occur — since the distribution of individual experiments is distributed fairly to other experiments, there is no problem.\ (See Group 1 in the image below) ![](/files/XsiBta8UZL1Rv0y5dQoa) ![Tests the user was exposed to](/files/02PX8fXsiwyGestadzQ5) However, if Test 1 and Test 2 affect each other in terms of UX or system, or cannot run simultaneously, or if you want to rigorously measure the individual effect of a specific test, you need to allocate traffic exclusively for each test. That is, **this feature is recommended when you need to configure traffic between specific experiments to not overlap.** ![Mutually Exclusive Group test](/files/K8cuglgDJnkO4Z7lgOjw) For example, if you run Test 1 (changing the search button color) and Test 3 (changing the search button position) simultaneously and want to check the click rate of the search button across both tests, it is difficult to measure the individual effect of each test. In such cases, you can add A/B Tests to a **Mutually Exclusive Group** to accurately measure the impact of each test. ### Configure Mutually Exclusive Settings In the Dashboard's **`A/B Test`** menu, go to **`Mutually Exclusive Settings`** in the left tab, and click the **`+ Configure Mutually Exclusive Settings`** button to create new mutually exclusive settings. ![Create a Mutually Exclusive Group](/files/do5rP5bV9pKxRFVdbRbK) ### Step 1. Configure Mutually Exclusive Settings ![Mutually Exclusive Group information](/files/9Vm6w75vRCLgr2OXDXcX) * **Update**\ Mutually Exclusive Settings can only be used with SDK version 2.0.0 or higher. If you are using an older SDK version, you must update. Clicking this button takes you to a page with update instructions. * **Mutually exclusive settings name**: Required. A default name is provided. Enter the name of the mutually exclusive group you want to create. * **Mutually exclusive settings description**: Optional. A description helps other team members understand the mutually exclusive settings. * **Mutually exclusive settings target**: Refers to all users. ### Step 2. Add a Mutually Exclusive Group ![Add a Mutually Exclusive Group](/files/9vHVBFuHAN8Q7yfXGA97) Click the **`Add Mutually Exclusive Group`** button to create up to 10 independent mutually exclusive groups.\\ ### Step 3. Configure the Mutually Exclusive Group ![Configure the Mutually Exclusive Group](/files/wO15fDeUlQaYToL2LMkN) 1. **Group name**: Required. Enter the name of the mutually exclusive group. 2. **Group traffic setting**: Traffic refers to the feature that configures how many users out of all users should be exposed to the A/B Test. You can set traffic within the available allocation. (Note: the minimum traffic for a mutually exclusive group is 10%.) 3. **Add A/B Test**: You can add the A/B Tests to run in a mutually exclusive manner. However, tests added to the same group are not mutually exclusive with each other. ### Add an A/B Test ![Add A/B Test](/files/eomC8JEcgEw3WbYGYETw) You can add existing A/B Tests in Draft status to a mutually exclusive group. ### Remove an A/B Test ![A/B Test addition complete](/files/y3z8mgKFr7wF1BEVmNfa) Click the trash can icon to remove an added A/B Test at any time. ![Remove an A/B Test](/files/szgDWV5Fz3Of0RzngAJY) However, if a running A/B Test is removed from the mutually exclusive group, that test is exposed to all users.\ For a running experiment, users beyond the configured traffic will be exposed, which will affect the experiment results. ![Screen with multiple groups added](/files/rg5hAUFBZB5p8AwPIFLq) This shows multiple mutually exclusive groups added.\ The three groups in the image are mutually exclusive with each other, and users assigned to one group are no longer exposed to other tests. (e.g., a user in the Design Team's group is not exposed to the Marketing Team's \[New Signup Exposure Timing Test].) * Click \[Configure] to modify the group settings. * Click the icon to the right of \[Configure] to delete the group. (Note: groups with A/B Tests added cannot be deleted.) ### A/B Test detail screen ![A/B Test - Check Mutually Exclusive Group](/files/FbilwkE9P9IuMJK1n1RL) You can check the mutually exclusive settings information for that test in the upper area of the A/B Test detail screen.\ Click the settings name to view the details of the mutually exclusive group the test has been added to. ### Conclude A/B Test When an A/B Test is concluded, the configured Winner group is exposed only to some users as set in the mutually exclusive settings.\ By removing the A/B Test from the mutually exclusive group, you can expose the changes to all users. ![Conclude A/B Test](/files/skpeFo43hD2LT8dfBdy0) After concluding the test, click the mutually exclusive settings name at the top to go directly to the detail screen.\ To expose the A/B Test results to all users, the test must be removed from the mutually exclusive group. ![A/B Test detail screen after conclusion](/files/O5ugWlKFTZTBOPx8mqSV) \[Note] * **Experiments that have already started (Running, Paused, etc. status) cannot be configured for mutually exclusive settings.** You can configure mutually exclusive settings for a version-updated or Draft experiment. * Mutually exclusive settings can be applied regardless of experiment type (MAB, AB, URL). * **Mutually Exclusive Group target** refers to whether the user is within the specific experiment exposure target. * Example: Mutually Exclusive Group target O means a user included in group 1's experiment group called experiment 1.\ Mutually Exclusive Group target X means a user included in group 2's experiment group called experiment 1. {% hint style="info" %} To expose the A/B Test to all users after conclusion, remove it from the mutually exclusive group. By removing the A/B Test from the mutually exclusive group, you can apply the changes to all users. {% 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.hackle.io/en/ab-test/mutually-exclusive-group.md?ask= ``` 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.