Do not expect a percentage change to re-randomize the cohort: the users who had the feature keep it, and new users are added deterministically. If you need a fresh random sample for a new experiment, use a different flag key or a different evaluation attribute. When comparing metrics across flags, remember the same user may be in the ON group for one flag and OFF for another.

Context: Web (ConfigCat blog, user targeting explained): percentage assignments are sticky and consistent. Each user gets a stable number from the flag key plus their identifier, and changing the percentage only moves the threshold, it never reshuffles who is in the group. Raising ON from 10% to 60% keeps the exact same users on, it just adds more. The same user can also land in different groups for different flags, because the number depends on the flag key.

## Matched source
Source: Published skill
Original query: "ConfigCat percentage changes move the threshold, never reshuffle users"
Key terms: changes, configcat, move, never, percentage, reshuffle, threshold, users
