Skip to content

Individual targeting

Individual targeting is a per-flag, per-environment list of (context kind, key) → variation overrides. It is the highest-priority targeting layer above targeting rules, so an individually targeted context always gets the variation you pin to it, regardless of what the rules say.

user / user-123 → variation: true
user / user-456 → variation: false
organization / acme → variation: true

Each row is exact match: a context whose targetingKey is user-123 matches the first row; a context with kind organization and key acme matches the third.

  • Pinning yourself or a customer. Force a known account on or off for support, demos, or bug reproduction.
  • VIP allow-list. A short list of “always on for these users” without writing a rule.
  • Permanent exception. A handful of accounts that should never see a new feature.

Individual targeting is the right tool for short, exact, one-off lists. As soon as the list:

  • Grows past a few dozen entries, or
  • Has a definition (everyone in a customer cohort, everyone in a country) rather than a hardcoded list,

reach for a segment. Segments are easier to keep in sync, are reusable across flags, and do not bloat the datafile.

The dashboard does not stop you from individually targeting thousands of users, but you will notice it in datafile size and SDK init time.

In the evaluation order, individual targeting sits between the off-switch check and the targeting rules:

  1. Off / archived check.
  2. Individual targeting. Exact (kind, key) match wins immediately.
  3. Targeting rules.
  4. Default rule.

An individual target also overrides percentage rollouts. If you pin user-123 to true and the default rule is a rollout that would have bucketed them into false, they still get true.

Individual targeting is off by default per organization. An admin enables it from Organization features. When off, the section is hidden in the flag editor.