[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["\u003cbr /\u003e\n\nWhen you build an app that includes both Firebase Remote Config and\nGoogle Analytics, you gain the ability to understand your app users better\nand to respond to their needs more quickly. You can use Analytics\n[audiences](https://support.google.com/firebase/answer/6317509)\nand [user properties](https://support.google.com/firebase/answer/6317519)\nto customize your app for segments of your\nuser base with flexibility and precision.\n\nIntegrating the Google Analytics SDK provides insights that help you\ntailor your offerings with [A/B Testing](/docs/ab-testing),\n[Remote Config personalization](/docs/remote-config/personalization), and\n[Remote Config rollouts](/docs/remote-config/rollouts). You can analyze the results to\nunderstand how different choices impact key metrics like revenue and engagement.\n| **Warning:** To use audiences and user properties with Remote Config, you must enable [Google Analytics data sharing](//support.google.com/firebase/answer/6383877) for your project. In your app, you'll need to ensure Firebase Analytics is present and data collection is available as well.\n\nTo learn more about analyzing app usage with Google Analytics, see the\n[Analytics introduction](/docs/analytics).\n\nTo customize your app using segments you may have identified outside Firebase,\nsee the [imported segments documentation](/docs/projects/import-segments).\n\nRemote Config and user properties\n\nRemote Config now lets you use combinations of Analytics user\nproperties to create\nconditions, allowing you to customize your app for segments of your user base\nthat you have defined.\n\nFor example, you could define the following user properties in\nGoogle Analytics for use in an exercise app with a range of exercise\nactivities at different durations and difficulty levels:\n\n- Exercise_Interest\n- Preferred_Exercise_Duration\n- Preferred_Difficulty_Level\n\nThen, you could create conditions that use these properties (individually, or\nin combination) to tailor the appearance and behavior of your app for specific\nusers. For example, you could design your app so that users who are interested\nin running see an image of a jogger when your app is loading. Or, you could\ndefine segments of your user base by exercise duration and difficulty level so\nthat casual users are first presented with a suggestion for a shorter, easier\nworkout, whereas serious athletes are invited to start a 40-minute run\nwhen our app starts up.\n|\n|\n| **Caution:** You can't use a small set of user property names\n| reserved by Google:\n|\n| - **Age**\n| - **Gender**\n| - **Interest**\n|\n| If you create an audience containing any of these disallowed properties, it\n| won't be available for creating conditions.\n\nIf the behaviors of your users change in ways that alter their user properties,\nthose updates are collected by Google Analytics, which can change the\nbehavior and appearance of their app instance after the next fetch request. A\nfull range of operators are available so that you can create rules that include\nor exclude users with specific user properties or combinations of user\nproperties.\n\nYou can also combine other Remote Config rules with rules based on user\nproperties, to deliver customized app behaviors to audience segments like\nthe following:\n\n- 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**).\n- Users who are interested in either weight lifting or weight loss (**Exercise_Interest** contains **weight** ) who use your app on an Apple device (**OS type** == **iOS** ) with an English-language UI (**Device language** == **English**).\n\n| **Note:** On Web, it can take several hours for a property to be available for targeting. See the documentation for [user properties on Web/JavaScript](/docs/analytics/user-properties?platform=web) for more information.\n\nTarget by first open time\n\nAfter you link Google Analytics and Remote Config, you can\ntarget users based on the first time they open your app (using the\nAnalytics event `first_open`) for Remote Config parameter fetches and\npersonalizations, and A/B Testing experiments.\n\nYou can use **First Open Time** to:\n\n- Target new users.\n- Target user groups who joined during a specific time period in the past.\n- Create and test onboarding flows and welcome experiences for new users.\n- Create custom experiences for users who join during specific time periods.\n\nFor example, say you have an online shopping app with users in multiple\ncountries, and want to advertise special holiday deals to new app users. For\nsomething like a Black Friday sale, which applies to US users, you can set up a\ncondition for your Remote Config or A/B Testing experiment that targets\na specific iOS or Android app, then select all US users (**Device in\nregion/country** == **United States** ) who first open your app in the month\nleading up to the sale (**First open After 11/01/2022 12:00 AM Los Angeles\nTime** and **First open Before 11/26/2022 12:00 AM Los Angeles Time**).\n\nUser targeting by first open time is available after you select an Android or\niOS app. It is currently supported by the following Remote Config SDK\nversions: Apple platforms SDK v9.0.0+ and Android SDK v21.1.1+\n(Firebase BoM v30.3.0+).\n\nYou can target users that first launch your app at any time, as long as a\nsupported SDK is installed and Analytics is enabled.\n\nNext Steps\n\nTo learn more about user properties, see the following guides:\n\n- [Set user properties on Apple platforms](/docs/analytics/user-properties?platform=ios)\n- [Set user properties on Android](/docs/analytics/user-properties?platform=android)\n- [Set user properties on Web/JavaScript](/docs/analytics/user-properties?platform=web)\n\n| **Note:** [Automatically collected user properties](//support.google.com/firebase/answer/6317486) are not currently available when creating Remote Config conditions.\n\nTo learn more about how conditions are created by combining rules, see\n[Remote Config Parameters and Conditions](/docs/remote-config/parameters).\n\nTo add a Remote Config condition to your project, see\n[Add or edit a condition](//support.google.com/firebase/answer/6386651#add_a_condition).\nYou can create parameters, rules and conditions in the\n[Firebase console](//console.firebase.google.com/project/_/config)."]]
