Use Firebase Remote Config with Analytics

When you build an app that includes both Firebase Remote Config and Google Analytics for Firebase, you gain the ability to understand your app users better and to respond to their needs more quickly. You can use Analytics user properties to customize your app for segments of your user base with flexibility and precision.

To learn more about analyzing app usage with Google Analytics for Firebase, see the Analytics introduction.

Remote Config and user properties

Remote Config now lets you use Analytics user properties to create conditions, allowing you to customize your app for segments of your user base that you defined much more precisely than was previously possible.

Using Remote Config with Analytics audiences has some limitations that are not present when you use user properties. Specifically, a user is a permanent member of an audience after they are assigned to it. By comparison, you can define user properties so that they are only temporarily true for specific users.

For example, you could define the following user properties in Google Analytics for Firebase for use in an exercise app with a range of exercise activities at different durations and difficulty levels:

  • Exercise_Interest
  • Preferred_Exercise_Duration
  • Preferred_Difficulty_Level

Then, you could create conditions that use these properties (individually, or in combination) to tailor the appearance and behavior of your app for specific users. For example, you could design your app so that users who are interested in running see an image of a jogger when your app is loading. Or, you could define segments of your user base by exercise duration and difficulty level so that casual users are first presented with a suggestion for a shorter, easier workout, whereas serious athletes are invited to start a 40-minute run when our app starts up.

If the behaviors of your users change in ways that alter their user properties, those updates are collected by Google Analytics for Firebase, which can change the behavior and appearance of their app instance after the next fetch request. A full range of operators are available so that you can create rules that include or exclude users with specific user properties or combinations of user properties.

You can also combine other Remote Config rules with rules based on user properties, to deliver customized app behaviors to audience segments like the following:

  • Users who like yoga (Exercise_Interest exactly matches yoga), who use your app on an Android device (OS type == Android), located in Canada (Device in region/country == Canada).
  • Users who are interested in either weight lifting or weight loss (Exercise_Interest contains weight) who use your app on an iOS device (OS type == iOS) with an English-language UI (Device language == English).

Next Steps

To learn more about user properties, see the following guides:

To learn more about how conditions are created by combining rules, see Remote Config Parameters and Conditions.

To add a Remote Config condition to your project, see Add or edit a condition. You can create parameters, rules and conditions in the Firebase console.

Send feedback about...

Need help? Visit our support page.