Firebase remote config versus A/B testing features

1.5k Views Asked by At

I can not find it anywhere, so I hope someone already stumbled upon this and can give me an answer.

I have been playing for a long time with Firebase remote config. In some occasions I have set parameters to be applied with different values to certain % of my user base.

Recently I started being interested in proper A/B testing and saw that Firebase has a feature for this (in beta right now). In the description of the A/B testing feature they state that one of the use cases is by setting parameters through remote config to alter the app's behaviour (makes sense, this is what I did until now).

My question though is whether A/B testing feature is doing anything different (or in addition to) to what remote config is doing. In particular, I am very interested in knowing whether remote config ensures me that when users open the app multiple times they will always be getting the same remote config values (maybe through tracking their device/user ID?) or is this only achieves if I use A/B config?

My experiments on this are not conclusive. It seems though that remote config does not ensure the same values over time.

1

There are 1 best solutions below

5
On

Firebase A/B Testing builds on top of Firebase Remote Config, and Google Analytics for Firebase (and some other Firebase products) to offer full A/B testing capabilities.

Once a user is part of a certain group in an A/B Testing experiment, they will remain part of that group for the duration of the experiment.

When you use Firebase Remote Config without A/B Testing, you are in control of the groups completely yourself. So in that case you determine what value(s) the user gets.