Remote Config rollouts
Remote Config rollouts give you the ability to safely and gradually release newfeatures and updates to your app. Using aRemote Configparameter, you can release new app features ina controlled manner to specific user groups. As your rollout proceeds, monitorits success usingFirebase Crashlytics andGoogle Analytics. UseRemote Config rollouts to:
- Minimize potential issues: Identify and address any bugs or issuesbefore they impact a large portion of your user base.
- Gather valuable feedback: Collect feedback from a limited audience anditerate on your implementation before rolling out to a wider audience.
- Enable iterative development: Make quick, iterative changes towidely-deployed apps while mitigating risk
- Monitor metrics you care about: Compare app stability betweenrollout and control groups withCrashlytics and useGoogle Analytics to monitor metrics like revenue and engagement.
For example, if you created an app that incorporates generative AI andstores prompts within aRemote Config JSON parameter, you might want to:
- Create a rollout that updates the parameter that contains your LLM prompt(s)to a small percentage of your user base.
- Monitor the resulting performance--have conversions increased or decreased?What about engagement? Are there more or fewer crashes?
- Depending on the results of the rollout, you may decide to:
- Roll back your change.
- Update the prompt parameter value to adjust and refine your model'sresponse.
- Increase your rollout percentage to roll out to a larger audience,ultimately rolling out 100% of your users.
You can alsoaccess thehistory of all of yourchanges using theFirebase console.
Monitoring forRemote Config rollouts is available for the following versions of FirebaseSDKs:
- Firebase iOS SDK v10.24.0+
- Firebase SDK for Android SDK v21.6.0+ (Firebase BoM v32.6.0+)
Crashlytics andGoogle Analytics are optional, but providesignificant value by measuring app stability and reporting key metrics likerevenue, conversions, and user engagement. Rollout metrics are availablefor the following versions:
- Crashlytics Android SDK v18.6.0+ (Firebase BoM v32.6.0+)
- Crashlytics iOS SDK v10.24.0
- Firebase SDK forGoogle Analytics (any version)
Key capabilities
| Target by user attributes | Deliver features to specific user segments based on user properties, app behavior, or any other relevant criteria. |
| Staged rollouts | Gradually increase the percentage of users exposed to a new feature over time, reducing the risk of unexpected issues. |
| Monitor stability | UseCrashlytics to monitor potential issues (like crashes, non-fatal errors, and non-responsive apps) that may be introduced by your feature release. |
| Gain insight into key metrics | Ensure that your new release positively affects theGoogle Analytics metrics you care about, like conversions, revenue, and user engagement. |
| Rollback functionality | If rollout results show potential issues, roll back to a previous version of the feature for all or a specific segment of affected users. |
How does it work?
Remote Config rollouts rely on three key components:
- Remote Config stores andmanages your app's configuration data, including feature flags andconfiguration parameters.
- Crashlytics providesreal-time crash reporting and performance monitoring so that you can trackthe impact of your rollout and quickly identify any trending issues.
- Google Analytics provides theability to target rollouts based on user attributesand monitor how yourlaunch affects key metrics like revenue, user engagement, and conversionevents.
For more information, seeAboutRemote Config rollouts.
Implementation Path
| ConfigureRemote Config | Define your feature flags and configuration parameters in theFirebase console. | |
| Set upCrashlytics | IntegrateCrashlytics into your app to monitor its performance and identify any issues. | |
| Set upGoogle Analytics | IntegrateAnalytics into your app to view key metrics like revenue and user retention. | |
| Implement rollout logic | ConfigureRemote Config in theFirebase console and in your app to access and apply feature flags and configuration parameters based on user targeting criteria. | |
| Monitor and iterate | MonitorCrashlytics data and user feedback to track the rollout's impact and make adjustments as needed. |
Policies and limits
A/B Testing experiments andRemote Config rollouts share the total experimentlimit: 24. For example, if you are running 12 A/B Tests, you arelimited to 12 running rollouts.
Next steps
- Learn moreaboutRemote Config rollouts.
- Get started withRemote Config rollouts.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-04 UTC.