First of all … Why do I want user properties? 🙄Thanks to the Firebase Analytics user properties we can analyze the behavior of users who perform certain actions within the app.
User properties will allow us to segment or filter the activity of APP users . For example, type of subscription selected (annual subscription, monthly subscription, pay-as-you-go), favorite team selected by the user (Example of the LFP APP).With user properties and events we can create groups or cohorts of users to analyze their behavior.To implement the user properties we will need the help of the developers, so the first thing is to plan the measurement, setting objectives and collecting all the necessary information in a document. This will help us to transmit the information to the different components of the team or other departments (IT, free mobile number database Product, etc).UPDATE MAY / 2020: Firebase allows archiving of user properties. The limit is still 25 properties per account.👉What are user properties?The user properties in Firebase are how “custom dimensions” of Google Analytics, we provide information about user attributes, ie, about how are users who perform actions within the app.When an event is launched, it contains user attributes (parameters) that we want to know (sex, age, country, app version, device category …).For example:Event: He clicked on “rent a car”.
It is launched when the user clicks on the “rent a car” button. An event will be posted to the console.User properties: Along with the event the user attributes will arrive. gulf email list Automatic and personalized ones: Sex: “Man”, Country: “Spain”, App version: “2.0.3”, Car preference: “Berlina”, etc* Custom dimensions in Analytics can be hits, sessions, or users, while user properties in Firebase are always users.⚙️How to create user properties in Firebase AnalyticBefore planning what you need, keep in mind that Firebase collects some user properties automatically with the configured SDK
NOTE : Some property does not show data. For example, those of interests are only shown if we have the advertising ID added in the compilation of the APK.
Add user properties to the consolThe first thing is to add the properties to the console , for this it is important that we write the name as it will appear in the app. I recommend not changing the name after a while, so think about it from the beginning.NOTE: Capital letters count, so “ClientUser” will not be the same as “clientuser”. We would be measuring different thingsRemember that as in Analytics we cannot use these properties to save personal information (email, telephone, ID …).Implement the code
Add the code in the app that includes the user property in the development environment we are using (Android Studio or XCode). This part is up to the developers so we will need your help.Check what works
With Firebase’s DebugView we can activate debugging mode to see what we have implemented.Once we have verified that everything works, and without retroactive effect, we will begin to obtain data from the implemented user properties.