Would like to understand the default percentage option under Targeting filter

[sathishkumarkaliavaradhan]

Hi All,

I would like to understand how the default percentage works? like within 1 hours if 10 calls made then 5 calls will get true and 5 calls get false?

I haven't set the seed and user groups only set the default percentage.

Thanks,
Sathishkumar

[jimmyca15]

Hi @sathishkumarkaliavaradhan

The default percentage determines the probability that a feature flag will be enabled for any given request. If you set the default percentage to 50%, it means that, on average, 50% of the calls will return true (feature enabled) and 50% will return false (feature disabled).

However, this doesn’t guarantee an exact split within a specific timeframe or number of calls. For example, if 10 calls are made within an hour, it’s possible that not exactly 5 will return true and 5 will return false. The distribution is random, so you might see variations like 6 true and 4 false, or 3 true and 7 false, etc.

[sathishkumarkaliavaradhan]

@jimmyca15 Thanks for the reply.

The default percentage determines the probability that a feature flag will be enabled for any given request. If you set the default percentage to 50%, it means that, on average, 50% of the calls will return true (feature enabled) and 50% will return false (feature disabled).

In our case we are using in our client WPF application, and App configuration SDK calling the CDN instead of Azure App configuration API. we see the CDN has the below configuration

"clientFilters": [ { "name": "DeviceFilter", "parameters": { "AppVersion": "5.5.0.0" } }, { "name": "Microsoft.Targeting", "parameters": { "Audience": { "Users": [], "Groups": [], "DefaultRolloutPercentage": 50 } } } ],

In this case how does SDK handle the DefaultRolloutPercentage of 50% rollout?