--- title: Better User Targeting with Firebase Remote Config description: Firebase Remote Config now supports targeting users by custom user properties, not just Firebase Analytics audiences. User properties let developers create... canonical: https://daily.dev/posts/better-user-targeting-with-firebase-remote-config-5nbyrajkn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Better User Targeting with Firebase Remote Config | daily.dev og:description: Firebase Remote Config now supports targeting users by custom user properties, not just Firebase Analytics audiences. User properties let developers create... og:url: https://daily.dev/posts/better-user-targeting-with-firebase-remote-config-5nbyrajkn og:image: https://api.daily.dev/og/posts/5NbyrAjKn.png og:image:alt: Better User Targeting with Firebase Remote Config og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Better User Targeting with Firebase Remote Config **[Firebase](https://daily.dev/sources/firebase-blog)** · 5 min read · 0 upvotes · 0 comments ## Summary Firebase Remote Config now supports targeting users by custom user properties, not just Firebase Analytics audiences. User properties let developers create smaller, dynamic, ad-hoc targeting groups without hitting the 50-audience limit or dealing with the fact that audience membership is permanent once joined. Examples show tiering game players by level or personalizing fitness app content by favorite activity, with string and numeric comparison support and easy adjustment of tier thresholds without code changes. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How is targeting users by user properties different from using audiences in Firebase Remote Config? User properties allow smaller, ad-hoc, dynamic targeting groups, while audiences are capped at 50 and shared across other Firebase features like Analytics reports and AdWords remarketing. Audiences are also permanent once a user joins, so a group like 'players below level 10' would eventually include everyone who ever played. User properties let conditions update automatically as values change, such as a player's level. _Developers weighing Firebase targeting strategies can follow platform changes like this on daily.dev._ ### How does Firebase Remote Config handle numeric comparisons on user properties? User properties are stored as strings by default, but Remote Config automatically converts them to numbers for numeric comparisons, so "42" evaluates to 42 and "3.14159" evaluates to 3.14159. Strings that don't parse as integers or floats, like "Level_42", always fail numeric comparisons. String comparisons like exact match or contains are also supported. _daily.dev helps developers keep up with platform quirks like this when building personalization logic._ ## Similar posts on daily.dev - [Optimize your Firebase Remote Config usage](https://daily.dev/posts/optimize-your-firebase-remote-config-usage-woddfd7ym) · Firebase · 1 upvotes · 1 comments - [Dynamic configuration in Java with Server-Side Firebase Remote Config](https://daily.dev/posts/dynamic-configuration-in-java-with-server-side-firebase-remote-config-yvb4sfjnd) · Firebase Developers · 0 upvotes · 0 comments --- Tags: [#mobile](https://daily.dev/tags/mobile), [#firebase](https://daily.dev/tags/firebase), [#ab-testing](https://daily.dev/tags/ab-testing) [View this post on daily.dev](https://daily.dev/posts/better-user-targeting-with-firebase-remote-config-5nbyrajkn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Better User Targeting with Firebase Remote Config","url":"https://daily.dev/posts/better-user-targeting-with-firebase-remote-config-5nbyrajkn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/better-user-targeting-with-firebase-remote-config-5nbyrajkn"},"datePublished":"2026-08-23T12:18:39.352Z","dateModified":"2026-08-23T12:29:20.602Z","description":"Firebase Remote Config now supports targeting users by custom user properties, not just Firebase Analytics audiences. User properties let developers create...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/better-user-targeting-with-firebase-remote-config-5nbyrajkn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,firebase,ab-testing","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Better User Targeting with Firebase Remote Config"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/better-user-targeting-with-firebase-remote-config-5nbyrajkn#faq","mainEntity":[{"@type":"Question","name":"How is targeting users by user properties different from using audiences in Firebase Remote Config?","acceptedAnswer":{"@type":"Answer","text":"User properties allow smaller, ad-hoc, dynamic targeting groups, while audiences are capped at 50 and shared across other Firebase features like Analytics reports and AdWords remarketing. Audiences are also permanent once a user joins, so a group like 'players below level 10' would eventually include everyone who ever played. User properties let conditions update automatically as values change, such as a player's level. Developers weighing Firebase targeting strategies can follow platform changes like this on daily.dev."}},{"@type":"Question","name":"How does Firebase Remote Config handle numeric comparisons on user properties?","acceptedAnswer":{"@type":"Answer","text":"User properties are stored as strings by default, but Remote Config automatically converts them to numbers for numeric comparisons, so \"42\" evaluates to 42 and \"3.14159\" evaluates to 3.14159. Strings that don't parse as integers or floats, like \"Level_42\", always fail numeric comparisons. String comparisons like exact match or contains are also supported. daily.dev helps developers keep up with platform quirks like this when building personalization logic."}}]} ```