使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Firebase A/B Testing
plat_ios
plat_android
Firebase A/B Testing 通过简化产品和营销实验的运行、分析和调整方式,帮助您优化应用体验。它使您能够测试对应用界面、功能或互动性宣传活动所做的更改,以便在广泛发布之前了解这些更改对关键指标(如收入和用户留存率)有何影响。
您可以通过 FCM 创建 A/B Testing,测试不同的营销消息;也可以通过 Remote Config 创建,测试应用内所做的更改。
准备好开始了吗?选择产品:
创建 Remote Config 实验 创建消息传递实验
主要功能
运行测试并提升您的产品使用体验 |
通过 Remote Config 创建实验,在实验的变体中更改应用的行为和外观,并测试哪种产品使用体验能最有效地带来您最关注的效果。
|
使用 Notifications Composer 寻找再次吸引用户的方法 |
使用 A/B Testing 帮助您找出最有效的措辞和消息设置来吸引用户使用您的应用。
|
安全地发布新功能 |
发布新功能之前,最好先让一小部分用户参与测试,确保测试结果符合您的目标。等到对 A/B Testing 结果有了信心后,再向全部用户发布新功能。
|
定位用户群 |
使用应用用户的相关数据运行有针对性的 A/B 测试。例如,您可以定位运行特定应用版本、平台、语言的一部分用户,或选择与某个 Google Analytics 用户属性值相匹配的用户。
|
工作原理
创建实验后,您可以创建某项用户体验的多个变体,然后衡量这些变体对您的预期目标(如提高应用内购买量)的达成情况。您可以使用以“AND”逻辑串联的多个条件来定义目标用户群;例如,您可以限定目标用户群为特定应用版本的用户,且这些用户属于某个 Analytics 受众群体,如与客户端设置的自定义 Google Analytics 用户属性匹配的“崩溃用户”。

使用 Remote Config 进行实验时,您可以对一个或多个参数进行更改,从而改变应用的行为和外观。您可以利用此功能进行细微的更改(如修改最佳配色方案和菜单选项位置)或更显著的更改(如测试全新的功能或界面设计)。使用 Notifications Composer,您可以运行实验以找到要在通知消息中使用的正确措辞。
无论您的实验使用 Remote Config 还是 Notifications Composer,您都可以监控实验,直到找出领先变体,即在完成目标方面表现最佳的变体。您可以在一小部分用户群体中开始实验,然后随着时间的推移逐步提高参与实验的用户比例。如果在第一个实验中没有找出比基准更能实现您目标的变体,您可以开始新一轮实验,找到改进应用的最佳方法。
您还可以对照您的目标跟踪其他指标(应用崩溃、用户留存率和收入),便于您更好地了解实验结果及其对应用的使用体验所产生的影响。
实现流程
|
将 Remote Config 或 Firebase Cloud Messaging 添加到您的应用中 |
如果您的应用已经在使用 Remote Config 或 Cloud Messaging(或两者都使用),您可以跳到下一步。 |
|
定义您要通过 A/B 测试进行评估的变体 |
无论您是要做细微更改还是要添加新界面或功能,如果您可以使用 Remote Config 来控制此类更改,就可以通过 A/B Testing 针对此类更改测试多个变体。
您还可以搭配使用 A/B Testing 和 Notifications Composer,针对再互动宣传活动测试多个变体,然后再向所有用户发布宣传活动。
|
|
定义成功的衡量标准 |
在使用 Notifications Composer 的实验中,您可以使用 Analytics 事件来定义实验目标并比较实验变体。在 Remote Config 实验中,您可以使用 Analytics 事件或转化漏斗来定义实验目标。
|
|
监控您的实验以找到胜出变体 |
您可以只在几个用户中开始实验,如果早期结果还不错,再逐步扩大用户范围。监控实验时,您可以看到是否有变体导致了更多的应用崩溃或对应用的使用体验产生了其他影响,还可以看到哪个变体最接近您的目标。 |
后续步骤
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-04。
[null,null,["最后更新时间 (UTC):2025-08-04。"],[],[],null,["Firebase A/B Testing \nplat_ios plat_android \n\nFirebase A/B Testing helps you optimize your app experience by\nstreamlining the way you run, analyze, and scale product and marketing\nexperiments. It gives you the power to test changes to your app's UI, features,\nor engagement campaigns to see how they impact your key\nmetrics (like revenue and retention) before you roll them out widely.\n\nA/B Testing works with FCM so you can test different marketing\nmessages, and with Remote Config so you can test changes within your app.\n\n\u003cbr /\u003e\n\nReady to get started? Choose a product:\n\n[Create Remote Config experiments](/docs/ab-testing/abtest-config)\n[Create messaging experiments](/docs/ab-testing/abtest-with-console)\n\nKey capabilities\n\n|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Test and improve your product experience | Create experiments with Remote Config to make changes to the behavior and appearance of your app across the variants in your experiment, and test which product experience is most effective at driving the results you most care about. |\n| Find ways to re-engage your users by using the Notifications composer | Use A/B Testing to help you find the most effective wording and messaging settings for bringing users into your app. |\n| Safely roll out new features | Don't roll a new feature out without making sure it meets your goals with a smaller subset of users first. Once you have confidence in your A/B Testing results, roll the feature out to all your users. |\n| Target user groups | Run targeted A/B tests using data about your app users. For example, you could target a subset of users running a specific app version, platform, language, or select users that match a Google Analytics [user property](https://firebase.google.com/docs/analytics/user-properties) value. |\n\nHow does it work?\n\nWhen you create an experiment, create multiple variants of a user experience\nand measure how well the variants perform toward a goal that you want to achieve\n(such as boosting in-app purchases). Your targeted\nuser group can be defined by multiple criteria chained with \"AND\" logic; for\nexample, you could limit the group to users of a particular app version\nwho belong to both an Analytics\naudience such as \"crashing users\" that match a custom Google Analytics\nuser property set by the client.\n\nWith Remote Config, you can experiment with changes to one or more\nparameters to alter the behavior and appearance of your app. You could use this\nfor subtle changes like tinkering with the best color scheme and positioning of\nmenu options, or for more significant changes like testing a completely new\nfeature or UI design. With the Notifications composer, you can experiment to\nfind the right wording for a notification message.\n\nWhether your experiment uses Remote Config or the Notifications composer, you can\nmonitor your experiment until you identify a *leader*, the variant that best\naccomplishes your goal. You can start your experiment with a small percentage of\nyour user base, and increase that percentage over time. If your first\nexperiment does not reveal a variant that accomplishes your goal better than the\nbaseline, you can start a new round of experimentation to find the best way to\nimprove your app.\n\nYou can\nalso track other metrics (app crashes, retention, and revenue) along with\nyour goal so that you can have a better understanding of the outcome of your\nexperiment and how it impacts the experience of using your app.\n\nImplementation path\n\n|---|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Add Remote Config or Firebase Cloud Messaging to your app | If your app already uses Remote Config or Cloud Messaging (or both), you can skip to the next step. |\n| | Define the variants that you want to evaluate with an A/B test. | Whether your change is subtle or the addition of a new UI or feature, if you can control that change using Remote Config, you can test multiple variants on that change with A/B Testing. You can also use A/B Testing with the Notifications composer to test multiple variants on your re-engagement campaign before you roll it out to all users. |\n| | Define how you will measure success | With an experiment that uses the Notifications composer, you can use an Analytics event to define the goal of your experiment and compare experiment variants. With a Remote Config experiment, you can use either an Analytics event or a conversion funnel to define the goal of your experiment. |\n| | Monitor your experiment to find the winning variant | You can start your experiment with just a few users, and then roll it out to more users if early results look good. As you monitor your experiment, you will see whether some variants cause more app crashes or other impacts on the app experience, and you can also see which variant makes the most progress toward your goal. |\n\nNext steps\n\n- Learn more about experiment concepts and best practices in [About Firebase A/B Testing](/docs/ab-testing/ab-concepts).\n- Get started creating experiments for [Remote Config](/docs/ab-testing/abtest-config), [the Notifications composer](/docs/ab-testing/abtest-with-console), or [In-App Messaging](/docs/ab-testing/abtest-inappmessaging).\n- Learn more about the Firebase features that interact with A/B Testing: [Google Analytics](/docs/analytics), [Firebase Remote Config](/docs/remote-config), [Cloud Messaging notifications](/docs/cloud-messaging/concept-options#notifications), [In-App Messaging](/docs/in-app-messaging), [AdMob](/docs/admob), and [Remote Config personalization](/docs/remote-config/personalization)."]]