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. |
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.
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:
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.
Important: Changes to experiments or traffic allocation can affect visitor allocation immediately. PageSense displays a warning before you confirm changes that may affect allocation.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. |