Firebase Remote Config - "user in random percentile" with a key

Question

I am studying the use of the Firebase User Percentile Random Conditions to specify different segments of the client base for A / B testing and have a few questions after looking at the documentation for the parameters and configurations of the remote Firebase configuration :

Each application instance is constantly mapped to a random integer or fractional number in accordance with the key defined in this project.

• Assuming a similar setUserProperty this value is stored for all generated percentiles (i.e., without keys and with keys) until the application is deleted . Is this the correct assumption?

• If the condition displays a random percentile that is <= 50, and then changes this condition only to the target <= 10 (but does not modify the key associated with the random percentile), I expect that 11-50 percentiles now correspond to the following condition (maybe by default), but the original 0 to 10 percentile should still match the condition. Are these assumptions correct?

• Once a random percentile is created for the user, does this value apply to any mutations until the key for that percentile changes? For example, for the key "firebase_test" user. The percentile is 47%. Until user A removes the application, the user percentile value will always be 47% for "firebase_test" .

• Is FirebaseRemoteConfig single-user mode permanent? I assume that fetching after the cache expires will ignore any values ​​returned earlier by getValue methods and simply return the last configured value.

• Is there a way to print the percentile value that the user has assigned for the given keys (and also there is no key)? For example, a call to mFirebaseRemoteConfig.getPercentile("firebase_test") will return 1.234 .

Thanks!

Answer 1

• This is true on iOS. I believe in Android, this value will remain even if you uninstall / reinstall the application.

• Yes, this assumption is true. (Here's how you can do a gradual deployment of a function with a remote configuration)

• I think so, although if you have certain problems, I would be glad to hear "em

• This is true if you also remember to call applyFetched after receiving these new values.

• No, now there is no way to do this.