How can we help?

What is the targeting logic for percentage rollouts?

The variation a user receives is determined based on the users key. When a percentage rollout is evaluated it generates a hash from the user's key, the user's secondary attribute if available, and a hidden salt attribute stored in the flag. The SDK then uses this hash to generate a percentage which is used in conjunction with the percentage rollout configuration to determine the variation a user receives.

Was this article helpful?
1 out of 2 found this helpful
Have more questions? Submit a request