透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Firebase A/B Testing
plat_ios
plat_android
Firebase A/B Testing可協助您最佳化應用程式體驗,方法為:
簡化執行、分析及擴充產品和行銷的流程
實驗。透過這項功能,您可以測試應用程式的 UI、功能,
或參與式廣告活動,瞭解對主要成效指標的影響
再逐步推出報表
A/B Testing 支援 FCM,供您測試不同的行銷做法
訊息和 Remote Config,方便您測試應用程式內的變更。
準備好了嗎?選擇產品:
建立 Remote Config 個實驗
建立訊息實驗
主要功能
測試及改善產品體驗
|
使用Remote Config建立實驗來變更行為
以及不同變化版本的應用程式外觀
測試哪項產品體驗最能達成預期成果
最在乎的是什麼
|
使用通知編輯器,找出重新吸引使用者的方法 |
使用「A/B Testing」
可協助您在 Google Cloud 專案中
吸引使用者進入您的應用程式
|
安全地推出新功能 |
如要推出新功能,請務必先確認功能是否符合您的目標
並優先考量一小群使用者確定您可以放心使用
A/B Testing 結果,歡迎向所有使用者推出這項功能。
|
目標使用者群組 |
使用應用程式使用者的相關資料,執行指定目標 A/B 版本測試。
舉例來說,您可以指定一部分執行特定應用程式的使用者
版本、平台、語言,或選取符合
Google Analytics
使用者屬性值。
|
運作原理
建立實驗時,請為使用者體驗建立多個變化版本
,並衡量變化版本在達成預期目標方面的成效
(例如提高應用程式內購次數)。您的指定目標
使用者群組可由多個以「AND」串連的條件定義邏輯;的
例如,您可以將群組限制為只有特定應用程式版本的使用者
同時屬於Analytics
目標對象,例如「流失的使用者」符合自訂 Google Analytics
由用戶端設定的使用者屬性。

使用 Remote Config 即可測試一或多項變更
修改應用程式的行為和外觀。您可以使用
可進行細微變化,例如將色彩配置調整為最佳色彩配置和位置
或進行更顯著的變更,例如測試全新的
包括功能或使用者介面設計使用通知編輯器,您可以嘗試
找出適當的通知訊息用語
無論實驗使用的是 Remote Config 還是通知編輯器,您都可以
監控實驗,找出成效最佳的勝出版本
可以達成您的目標。您可以對一小部分的
並逐漸提高這個比例如果您的第一個
實驗並不會顯示可達成您目標的變化版本
基準,您可以開始新的實驗,找出最適合
改善應用程式
你可以
同時追蹤其他指標 (應用程式當機、留存率和收益)
這樣才能更瞭解您
以及對應用程式使用體驗的影響
實作路徑
|
在應用程式中新增 Remote Config 或 Firebase Cloud Messaging |
如果您的應用程式已使用 Remote Config 或 Cloud Messaging
您可以直接跳到下一個步驟。
|
|
定義您要透過 A/B 版本測試評估的變化版本。 |
無論是細微變更,還是加入新 UI 或功能,
使用 Remote Config 控制這項變更
A/B Testing 支援該變更的變化版本。
您也可以將 A/B Testing 與通知編輯器搭配使用,測試多個變化版本
,再向所有使用者推出應用程式。
|
|
定義評估成效的方式 |
如果在實驗期間使用通知編輯器,您可以使用 Analytics
事件來定義實驗目標,並比較實驗變化版本。
進行Remote Config實驗時,您可以使用 Analytics
定義實驗目標。
|
|
監控實驗以找出勝出的變化版本 |
您一開始可以只邀請幾位使用者進行實驗,之後再全面推出
初期結果看起來不錯時,還能增加的使用者人數。監控實驗時
以瞭解某個變化版本是否造成更多應用程式當機或其他影響
您也可以知道哪個變化版本的成效最高
你的目標進度
|
後續步驟
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間:2025-07-25 (世界標準時間)。"],[],[],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)."]]