LiftCanary

Guides

Exclusion groups

Keep experiments that touch the same page or goal from sharing visitors.

Two experiments that change the same page, or chase the same goal, can spoil each other's results: a visitor who sees a new hero and a new banner tells you about the pair, not about either one. An exclusion group makes its experiments mutually exclusive: nobody is in two of them.

How it works#

A group splits visitors into 10,000 buckets with a hash of their id and the group's own salt. Each experiment in the group owns a slice of those buckets in its environment, for example the first 40% and the remaining 60%. A visitor only enters the experiment whose slice holds them. The experiment's audience, traffic and variation split then apply as usual, inside its slice.

Each visitor falls in one bucket of the group, so they can enter at most one of its experiments. Inside its slice, an experiment's own audience, traffic and variation split apply as usual.

TopicWhat happens
SlicesGiven out in order, first fit, so a stopped experiment's slice is reused by the next one.
ChangingOnly while the experiment is a draft. A running experiment's slice is fixed: moving it would move visitors in or out mid-test.
StoppingFrees the slice. Shipping a winner turns it into a rollout for the whole audience, outside the group.
Full groupWhen no free slice is large enough, creating or editing the experiment is refused with the share that is left.
BucketingOn the same id as the experiment (the user id, or the bucketing id you pass), so a person keeps their slice across devices when you identify them.

In the dashboard#

Create a group under Exclusion groups in the project. Then, on a draft experiment, pick the group in the Exclusion group card and the share of the group's visitors it should get. The group page shows each environment's slices and what is still free.

With the API#

Create a group, then an experiment in it
POST /v1/projects/shop/exclusion-groups
{ "key": "homepage", "name": "Homepage" }

POST /v1/projects/shop/experiments
{ "name": "New hero", "flag": "hero", "environment": "production",
  "exclusion": { "group": "homepage", "share": 4000 }, "start": true }

share is in buckets (4000 = 40%). PATCH /v1/projects/:project/experiments/:id with exclusion (or null to leave) changes a draft. The experiment shows its slice as exclusion: { group, start, end, share }, and the datafile carries it on the rule.