Mutually Exclusive Groups in Zoho PageSense

Mutually Exclusive Groups

Mutually exclusive groups prevent a visitor from being assigned to more than one experiment within the same group. Use them when experiments could overlap, for example, when they run on the same page or affect the same part of a visitor's journey. This helps reduce interference between experiments and keeps their results easier to interpret. To manage mutually exclusive groups, go to Settings > ME Groups in your PageSense project. Mutually exclusive groups support Web A/B Testing and FullStack A/B Testing. The setup and experiment membership rules differ by type.

How mutually exclusive groups work  

When a group is Active, PageSense assigns visitors so that each visitor is enrolled in only one experiment within that group at a time.

Group type
Visitor assignment
Environment
Experiment membership
Web A/B Testing
Based on cookie/session ID
Not applicable
An experiment can belong to multiple Web A/B groups.
FullStack A/B Testing
Deterministic server-side assignment based on user ID and project ID
Required
An experiment can belong to only one FullStack group at a time.

Understand group statuses  

A group can have one of three statuses:
  • Active: The group meets the activation requirements, and mutual exclusivity is enforced.
  • Inactive: Mutual exclusivity isn't enforced. PageSense moves a group to Inactive automatically when it no longer meets the activation requirements, such as when fewer than two experiments remain. A restored archived group also returns to Inactive. You can't manually set a group to Inactive.
  • Archived: The group has been archived and is removed from the default view. Its experiments continue to run independently, without mutual exclusivity.
You can edit an Inactive group and activate it again once it meets the requirements. Restoring an archived group moves it to Inactive; restoring it doesn't activate the group automatically.

Create a Web A/B group  


Mutually exclusive groups are particularly useful when you are running multiple experiments on the same page, similar pages, or targeting the same audience segment. By grouping these experiments together, PageSense ensures that each visitor is exposed to only one experiment from the group.
Name
The Name field is used to assign a unique name to the mutually exclusive group. This helps you easily identify the group when managing multiple experiments across your project.

For example, you may create groups such as:
  • Homepage Experiments
  • Pricing Page Tests
  • Checkout Optimization Tests
Using clear naming helps teams understand the purpose of the group and the experiments included in it.


Description

The Description field allows you to add additional information about the purpose of the mutually exclusive group. This may include details about the experiments included, the pages being tested, or the optimization goal.


Providing a short description helps maintain clarity for teams managing multiple experiments.



Select Experiments
The Select Experiments section allows you to choose which experiments should be included in the mutually exclusive group.
Once experiments are added to the group:
  • Visitors will be assigned to only one experiment within the group.
  • They will not be eligible for other experiments in the same group.
  • This prevents experiments from overlapping and affecting each other’s results.

You can select experiments that are in different statuses such as Running, Draft, or Paused, depending on your testing workflow.


Traffic Allocation

The Traffic Allocation setting lets you control how the visitor traffic is distributed among the experiments included in the group.

You can assign a specific percentage of traffic to each experiment. PageSense will then distribute eligible visitors according to the defined allocation.


For example:

  • Experiment A – 50% traffic
  • Experiment B – 50% traffic

This ensures that experiments receive the intended portion of traffic while still maintaining the rule that each visitor participates in only one experiment from the group.


Create a FullStack A/B group  

Steps to create
  1. Go to Settings > ME Groups.
  2. Click Create group.
  3. Enter a name for the group.
  4. Select FullStack A/B Testing as the group type.
  5. Select an environment before adding experiments.
  6. Select the eligible FullStack experiments from that environment.
  7. Set the traffic allocation for each experiment. The combined allocation can't exceed 100%; any unallocated traffic is holdout traffic.
  8. Review the group details and click Create group.
 For FullStack groups, keep these rules in mind:
  1. The environment is required and must be selected before you add experiments.
  2. Only experiments from the selected environment are available for selection.
  3. All experiments in the group must belong to the same environment.
  4. The environment list comes from the environments configured for your project.
  5. You can't change the environment after creating the group.
  6. If you change the environment while creating a group, the experiments already selected are cleared because the list of eligible experiments changes.
  7. You can't change a group's type after it has been created.
FullStack experiment membership rules  
  1. A FullStack experiment can belong to only one FullStack group at a time.
  2. When you add an experiment to a FullStack group, PageSense checks whether it already belongs to another FullStack group:
  3. If it belongs to an Active group, you can't activate another group containing that experiment until you resolve the conflict.
  4. If it belongs to an Inactive or Archived group, you can add it to another group.
  5. This also applies when you restore an archived group. If one of its experiments is already part of another Active FullStack group, resolve the conflict before activating the restored group.
  6. These membership restrictions apply only to FullStack groups. A Web A/B experiment can belong to multiple Web A/B groups.

Activate a group  

Activate a group
  1. A group must contain at least two experiments to be activated.
  2. Go to Settings > ME Groups.
  3. Open the Inactive group.
  4. Review its experiments and traffic allocation.
  5. Click Activate.
For FullStack groups, PageSense also checks whether any experiment belongs to another Active FullStack group. Resolve any membership conflicts before activating the group. Once the group is Active, PageSense enforces mutual exclusivity for its experiments.

 Add or remove experiments  

Add experiments
  1. Go to Settings > ME Groups and select the group.
  2. Click Edit.
  3. Add the eligible experiments.
  4. Review the traffic allocation and save your changes.
For FullStack groups, the experiment must belong to the group's selected environment and must not conflict with another Active FullStack group. Experiments in Inactive or Archived FullStack groups can be added to another group.

Remove experiments
  1. Go to Settings > ME Groups and select the group.
  2. Click Edit.
  3. Remove the experiment.
  4. Review the traffic allocation and save your changes.
Removing an experiment or reducing its traffic allocation can affect visitors already assigned to experiments. If fewer than two experiments remain, PageSense automatically moves the group to Inactive, and mutual exclusivity is no longer enforced.
NotesImportant: Changes to experiments or traffic allocation can affect visitor allocation immediately. PageSense displays a warning before you confirm changes that may affect allocation.

Edit a group  

You can edit a group's name, description, traffic allocation, and experiments. The group type can't be changed after creation, and a FullStack group's environment is fixed.

Setting

Web A/B group

FullStack group

Name and description

Can be edited

Can be edited

Group type

Can't be changed

Can't be changed

Environment

Not applicable

Can't be changed after creation

Traffic allocation

Can be edited

Can be edited

Experiments

Eligible Web A/B experiments can be added or removed. An experiment can belong to multiple Web A/B groups.

Eligible experiments from the group's environment can be added or removed, subject to FullStack membership rules.


Changing the name or description doesn't affect visitor allocation. Changes to experiments or traffic allocation can affect allocation immediately.


What happens when an experiment is deleted?
  1. PageSense updates a group automatically when an experiment in it is deleted:
  2. Two or more experiments remain: The deleted experiment is removed from the group, its traffic allocation becomes holdout traffic, and the group keeps its current status.
  3. Fewer than two experiments remain: The group moves to Inactive, and mutual exclusivity is no longer enforced.
  4. PageSense informs you about the impact when you delete the experiment.

What happens when a FullStack environment is deleted?
An environment can be deleted only when no experiments are mapped to it. When you delete an environment, PageSense also deletes all mutually exclusive groups mapped to that environment. This behavior applies only to FullStack A/B Testing because environments are supported only for FullStack experiments. Web A/B experiments don't use environments, so this behavior doesn't apply to Web A/B groups.


 Delete a group  

Deleting a group doesn't delete its experiments. The experiments continue to run independently.
Deletion
  1. Go to Settings > ME Groups.
  2. Select the group you want to delete.
  3. Click Delete.
  4. Review the confirmation message and confirm the deletion.


When you delete a group, PageSense removes its experiment associations and no longer enforces mutual exclusivity for those experiments. Visitors who are already assigned to an experiment remain in that experiment. If the group contains running experiments, PageSense displays a warning before deletion. Without mutual exclusivity, visitors may be exposed to multiple experiments, which can affect the consistency of experiment results. 

Archive or restore a group  


Archive a group
You can archive an Active or Inactive group to remove it from the default view without deleting the group.
  1. Go to Settings > ME Groups.
  2. Select the group.
  3. Click Archive.
  4. Review the warning and click Archive group.
Archiving doesn't stop or delete the experiments. They continue to run independently, and mutual exclusivity is no longer enforced.

Restore an archived group
  1. Go to Settings > ME Groups.
  2. Open the Archived view.
  3. Select the group and click Restore.
The group returns to Inactive. Review its experiments and traffic allocation, add experiments if needed, and activate it when it meets the requirements. For FullStack groups, resolve any conflicts with other Active FullStack groups before activation.

 Frequently asked questions  

How many experiments are required to activate a group?
At least two experiments must be in the group.

Can I manually change a group to Inactive?
No. PageSense moves a group to Inactive automatically when it no longer meets the activation requirements. A restored archived group also returns to Inactive.

Can a Web A/B experiment belong to multiple groups?
Yes. A Web A/B experiment can belong to multiple Web A/B groups.

Can a FullStack experiment belong to multiple groups?
No. A FullStack experiment can belong to only one FullStack group at a time. It can't be part of more than one Active FullStack group.

Why can't I activate a FullStack group?
An experiment in the group may already belong to another Active FullStack group. Resolve the membership conflict before activating the group.

Can I change a group's type or environment after creating it?
You can't change the group type after creation. For a FullStack group, you also can't change its environment.

What happens to traffic that isn't allocated to an experiment?
Traffic that isn't allocated to an experiment is treated as holdout traffic and isn't assigned to an experiment.

Does deleting or archiving a group stop its experiments?
No. The experiments continue to run independently. However, mutual exclusivity is no longer enforced, so visitors may be exposed to multiple experiments.

What happens if I delete a FullStack environment?
You can delete an environment only when no experiments are mapped to it. Deleting it also deletes all mutually exclusive groups mapped to that environment. This applies only to FullStack A/B Testing; Web A/B experiments don't use environments.






We’ve designed this documentation to guide you every step of the way. If you need further assistance or have any questions, don’t hesitate to contact us at support@zohopagesense.com - we’re always here to help!