[null,null,["最后更新时间 (UTC):2025-08-12。"],[],[],null,["\u003cbr /\u003e\n\nWith Remote Config personalization, you automatically provide users\none of several alternative user experiences, in order to optimize for an\nobjective of your choice.\nSee an [Overview](/docs/remote-config/personalization) of this feature.\n\nHere's how to get started.\n\n1. Instrument your app with Analytics and Remote Config\n\nBefore you can start providing personalized user experiences, your app needs to\nbe using Analytics and Remote Config.\n\n1. If you didn't enable [Google Analytics](/docs/analytics) when you\n created your Firebase project, enable it on your project's\n [Integrations](//console.firebase.google.com/project/_/settings/integrations) page.\n\n2. Make sure you're using at least the following versions of the\n Remote Config SDK:\n\n - iOS: 7.5.0 and above\n - Android: 20.0.3 (Firebase BoM 26.4.0) and above\n - C++ 7.1.1 and above\n - Unity: 7.1.0 and above\n\n Only these versions (and newer) perform the logging necessary for the\n personalization system to learn how to optimize for your objective.\n3. Add [event logging](/docs/analytics/events) calls to your app.\n\n At a minimum, log an event when a user completes the objective action you're\n optimizing for. For example, if you want to optimize for Play Store rating\n submissions, log an event every time a user rates your app.\n\n In addition, you should explicitly log any\n [Analytics events](https://support.google.com/analytics/answer/9267735)\n relevant to your app that aren't\n [automatically logged](https://support.google.com/analytics/answer/9234069).\n By logging these contextual events, you can improve the quality of your\n personalizations.\n4. Implement the different user experiences you want to be possible in your\n app. This could be as simple as personalizing how often ads are shown to\n each user, or more substantial alternatives, such as implementing different\n layouts.\n\n5. Make the different user experiences configurable based on the value of\n a Remote Config parameter.\n See [Get started with Remote Config](/docs/remote-config/get-started)\n and [Remote Config loading strategies](/docs/remote-config/loading).\n\nAt this point, you can deploy your app to the App Store or Play Store. Users\nwill continue to get the default experience you configured, but because you can\ncontrol the experience with a remotely configurable variable, you can start\nexperimenting with automatic parameter personalization.\n\nYou will need to have a critical mass of users using your updated app before the\npersonalization system can begin to optimize individual experiences.\n\n2. Configure parameter personalization in the Firebase console\n\nNow that your instrumented app is in users' hands, you can use the\nFirebase console to set up personalization.\n\n1. On the [Remote Config](//console.firebase.google.com/project/_/config) page of\n the Firebase console, find the parameter that controls the user\n experience you want to personalize, and click the pencil icon to edit it.\n\n2. On the **Edit parameter** pane, click **Add new \\\u003e Personalization**.\n\n3. Define two or more alternative values. \"Alternative values\" are a special\n name for the parameter values that the personalization algorithm can choose\n for your users. The format of the values you use here must match the\n [data type](/docs/remote-config/parameters#parameter_value_data_types) that\n your Remote Config parameter uses.\n\n | **Tip:** Choose alternatives that you expect to produce a large difference in outcomes. The system will learn faster and create more value when alternatives are less similar to each other.\n4. Choose an objective. You can choose one of the following:\n\n - Select from a list of prebuilt objectives for metrics like revenue and engagement.\n - Add a custom metric based on any other Google Analytics event that\n you'd like to optimize by typing the event name into the **Objective**\n field and clicking **Create event**.\n\n Because these events may be dynamic or custom, they may not appear in the\n drop-down. To ensure the metric you specify precisely matches an active\n Analytics event, verify the event in **Analytics** \\\u003e **Events**.\n\n | **Tip:** Choose an objective that fully captures the behavior you want to optimize. The algorithm only considers the objective when assigning alternatives and measuring performance.\n5. Select whether to optimize for the number of events (**COUNT** ) or the sum\n of all events' values (**SUM**).\n\n In some cases, this option is pre-selected for built-in Analytics\n events. For example, **SUM** will always be selected for **User engagement**\n time to optimize for total time spent. If you choose **Ad clicks** ,\n personalizations are optimized for **COUNT**, or total number of ad click\n events.\n6. If you selected **SUM**, enter the name of the event parameter to\n aggregate.\n\n In most cases, the event parameter name is `value`, but you might\n have a custom metric with a specific value you want to aggregate. For\n example, if you had an event with different currency types with parameters\n like `USD`, `JPY`, `AUD` and so on, you could optimize for Australian revenue\n by specifying `AUD` as the event parameter (and, in the next step, be sure to\n configure a targeting condition for users in Australia!).\n | **Important:** The value passed by the event must be an `int`, `double`, or `float` to be summed/aggregated.\n7. Optionally, choose up to two additional metrics to track. While these will\n not affect the personalization algorithm, these results can help you better\n understand performance and trends. For example, if your personalization\n optimizes for ad clicks, you may want to track user engagement between the\n baseline and personalized groups.\n\n Tracked metrics will appear in the Personalization results summary,\n organized by tab.\n8. Define or select a targeting condition for the personalized parameter.\n Only users who meet this condition will get a personalized experience.\n Some commonly used conditions are to limit personalization to only users\n of a particular platform or to only users in a particular region.\n\n |\n | **Tip:** Choose large enough target segments\n | to generate plenty of result data---personalization performs best\n | with at least 10,000 users and 1,000 successful outcomes per week.\n |\n |\n | You can use the **User exists** condition to ensure that\n | all users of all apps within your project are targeted for\n | personalization.\n\nWhen you're satisfied with your alternatives, objective, additional metrics, and\ntargeting, you're done! Save and deploy your changes to start personalizing your\nusers' individual experiences. Users will begin to receive personalized\nparameter values in a few hours, but it will take up to 14 days for the system\nto learn about your user and achieve the best performance.\n\nYou can see how a personalization is performing by selecting it from the\n[Personalizations page](//console.firebase.google.com/project/_config/personalizations)\nor by clicking on the parameter's targeting condition on the\n[Remote Config](//console.firebase.google.com/project/_/config) page.\n| **Tip:** You can use the [Personalizations list view](//console.firebase.google.com/project/_config/personalizations) to search for a specific personalization by name or objective, and can sort by Name, Start time, or Total lift.\n\nFor more information about interpreting results, see\n[Understand personalization results](/docs/remote-config/personalization/about#understand-personalization-results)."]]