Counting the number of users per process
Posted: Sun Jan 19, 2025 8:18 am
Based on the data on in-app behavior, we will count the number of users for each process in the funnel created in (2).
By comparing each number, if there is a process with montserrat email address a high dropout rate, you will know that this is the area that is causing the problem.
By implementing event tracking in FANSHIP provided by iRidge, it is possible to perform funnel analysis like the one above in reports.
(4) Setting KPIs for improvement
Once you have identified the issues in (3), you can begin making improvements right away. It is a good idea to start by setting KPIs for the areas that are issues.
KPI setting example)
Tutorial completion rate ◯%
・Member registration rate ◯%
・Return rate ◯% etc.
We then plan and implement measures to achieve the KPIs.
As with setting KPI values, try not to make your measures too difficult from the start.
You may not see results right away and you may lose motivation to improve.
It is more effective to start with something low-hurdle and work your way up little by little.
The method of identifying issues through funnel analysis, as explained here, is effective in a variety of situations in growth hacking.
If you feel that your app, service, or project isn't going well, be sure to try using this funnel analysis.
summary
This time, we used user activation as an example to explain how to discover issues through funnel analysis and the onboarding measures that should be implemented afterwards. What did you think?
By performing funnel analysis based on numerical data on user behavior within the app, you can identify the points at which users drop off and discover issues.
We hope that this, along with subsequent onboarding measures, will be helpful in growing your app.
In the next post, we’ll talk about app growth hacking from the perspective of qualitative data based on UX research.
By comparing each number, if there is a process with montserrat email address a high dropout rate, you will know that this is the area that is causing the problem.
By implementing event tracking in FANSHIP provided by iRidge, it is possible to perform funnel analysis like the one above in reports.
(4) Setting KPIs for improvement
Once you have identified the issues in (3), you can begin making improvements right away. It is a good idea to start by setting KPIs for the areas that are issues.
KPI setting example)
Tutorial completion rate ◯%
・Member registration rate ◯%
・Return rate ◯% etc.
We then plan and implement measures to achieve the KPIs.
As with setting KPI values, try not to make your measures too difficult from the start.
You may not see results right away and you may lose motivation to improve.
It is more effective to start with something low-hurdle and work your way up little by little.
The method of identifying issues through funnel analysis, as explained here, is effective in a variety of situations in growth hacking.
If you feel that your app, service, or project isn't going well, be sure to try using this funnel analysis.
summary
This time, we used user activation as an example to explain how to discover issues through funnel analysis and the onboarding measures that should be implemented afterwards. What did you think?
By performing funnel analysis based on numerical data on user behavior within the app, you can identify the points at which users drop off and discover issues.
We hope that this, along with subsequent onboarding measures, will be helpful in growing your app.
In the next post, we’ll talk about app growth hacking from the perspective of qualitative data based on UX research.