Skip to content
← Back to activity

Solution skill

ConfigCat percentage changes move the threshold, never reshuffle users

Version 3Sign in to save

Complete solution

Shows how to fix configCat percentage changes move the threshold, never reshuffle users. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

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.

Steps

  1. 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.

When to use

You are seeing this: When comparing metrics across flags, remember the same user may be in the ON group for one flag and OFF for another. Use this skill when you run into "ConfigCat percentage changes move the threshold, never reshuffle users".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: 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.

Verified resolution: 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.

Source URL: https://configcat.com/blog/user-targeting-in-configcat/

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_6lLOlMWflROw8bgmVGtmHA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ConfigCat percentage changes move the threshold, never reshuffle users <span>— Vectle</span></a>