This article is an introduction to the tool to locate the user in the fundamental concepts and be able to deepen the analysis of the applications by using Firebase Analytics.
If you work in Mobile or App Marketing, you should know this tool and start getting familiar with it. It is the future of analytics in applications and I warn you that it is not as intuitive as Google Analytics. For your personalized implementation, we will need to go hand in hand with a developer.
What is Firebase Analytics?
Firebase Analytics is a mobile analysis tool developed by Google. It is included in Firebase, as are other solutions, such as automatic notification management, version testing, etc. With this tool, we can manage the development, stability, analysis and growth of our application.
*For progressive web applications we must continue using Google Analytics, since they are considered web.
Find below a very complete tutorial:
Start with Firebase
To start with Firebase Analytics, we need a Firebase account, download the SDK and implement it in our application. Once this is done, we can begin to obtain data from our application. We will find events of two types:
- Basic or general events: are collected automatically without the need to implement more code in the application. Some examples are; open the application, the time of use, the active users, etc.
- Custom or specific events: these are events that do not come by default and that we will implement in the code. For example; registration (login), login, …
View data in Firebase Analytics
To see the analytical data of our application, we have two options. On the one hand, we can use Google Analytics, which would be the traditional option, and on the other hand, we can visualize the data through Firebase Analytics.
I recommend using Firebase even if it’s more complex at the beginning, but it’s more complete, and I think that in the future it will replace Google Analytics.
The Firebase interface, in terms of analysis, offers the following sections:
They start when a user performs an action in the application. They can be general or customized events for us.
These are important or metric events (our KPIs) of the application. The conversion settings will help us optimize marketing campaigns on Facebook, Google Adwords, etc.
It offers us information about the users (age, country, download store, brand, model, gender …) useful to filter or create personalized audiences.
With the events and properties of the users, we can generate specific audiences (public) that will help us segment our reports.
Conversion funnels or conversion funnels help us visualize the events we have previously defined. Unlike the traditional funnel, in this case it is not mandatory to complete the previous step to count in the next step. The least curious.
The user retention report offers information about the use of the application, we could talk about “fidelity” or “participation” of the application … We select a date and we can observe the retention by day, week or month.
VIEWS OF STEAM
It’s like Google Analytics’ “real time” report. It offers us a real-time view of what is happening in the application. We can see it by “events performed” or “active users”.
In summary, this application analysis tool is very complete, and especially the free version is more than enough for most applications. In addition, we must remember that it offers excellent integration with all Google products.