Non-gaming app

Basic metrics

The reports in the devtodev system are universal and suitable not only for games but also for detailed analysis of non-gaming applications. The system enables you to analyze both the main project metrics: DAU / MAU / WAU, retention, and monetization metrics like income, ARPU, ARPPU, as well as to conduct a more detailed analysis of user behavior. The Real-time dashboard shows key metrics of the current day compared to the previous day. It helps you to keep track of your app’s performance in real time. The report allows you to quickly track changes in the application audience: New users, Cumulative new users, Sessions, Cumulative sessions, Users online; it also allows you to compare today’s indicators of Gross, Cumulative gross, Top countries (by new users or by gross) with yesterday’s.

Thus, you can get live data reports and observe the performance of important project indicators. The information in the report is updated every five minutes. You can read more about Real-time dashboards in the documentation.

Acquisition reports

First of all, you can analyze the effectiveness of user acquisition. Acquisition reports answer the following questions: how many users each channel brought, which one is the most profitable, how many users keep using the application after a day, a week, two, etc. and when will this traffic pay off. You can integrate traffic attribution services such as Adjust, Appsflyer, Tune, Branch, Kochava, and Tenjin to get install information.

Monetization

The reports in the Monetization section give information about the key monetization metrics of your project. For example, you can monitor the dynamics of ARPU, Paying share, ARPPU, Gross. You can also find useful information about users’ repeated purchases and the time between purchases. You can find out on which day users make purchases in your application more often and use an offer to nudge them to buy on that day.

You can also study the structure of your paying audience and income from a perspective of the time that has passed since the installation.

Using the RFM analysis report, you can segment your paying audience by their purchasing patterns. This way you can improve retention and increase revenue by re-engaging inactive paying users.

In order to view the data in the Monetization Dashboard, Gross Structure, Conversion to Payments, RFM Analysis, Transactions Number, Transactions reports, you need to integrate Payment event transmission. You must send this event immediately after the platform confirms that the payment went through successfully. Learn more about the Payment event integration here.

Segmentation

User segmentation is an important and useful process in mobile application analysis. Sometimes, hypotheses based on information about all users can lead to incorrect conclusions. The larger the audience of your project, the less homogeneous it is. Therefore, using user segmentation, you can analyze the segments in comparison with each other. For example, you can compare the rates of authorization conversion funnels for different countries. There are two types of segments: static and dynamic. A static segment consists of a specific list of users who perform a specific number of events. A static segment can be created using the conversion funnels section, and the list of users will not be updated:

It is also possible to create a dynamic segment; this list of users will be updated every time new users perform an event specified in the segment parameters. You can create it by going to the Tuning tab, and then to the Segments section:

Once segments have been created, they can be used in reports and dashboards in the same way as filters. For example, you can compare the behavior and metrics of users who completed a tutorial with those who skipped it.

Engagement

The Engagement section enables you to analyze user behavior, retention, and engagement. Tutorial Analysis shows a tutorial steps funnel, as well as the number of users who successfully completed, did not complete, or skipped the tutorial. Using this report, you can identify bottlenecks in your tutorial.

In order to build a funnel of tutorial progression steps, you need to integrate the basic Tutorial step event. This event should be sent at the end of each tutorial step with the number of each completed step as a parameter. You can learn more about integration here.

The Retention report in the Engagement section shows you the percentage of users who opened your app on a selected day after the first launch. This way you can gauge the loyalty to your product and understand when users stop using it.

In the Audience structure report, you can analyze the structure of your audience divided into different groups according to the following parameters: App versions, Country, Devices, Paying capacity (free / minnows / dolphins / grand dolphins / whales / grand whales), Paying status (paying / free), Returning users (new users / returning users). You can also compare application versions - this is useful in the first days after the release of a new version of the application to make sure that in the updated version the main user action funnels have not been worsened or made more complex. You can compare the metrics of users going through the tutorial, their retention, and income across product versions.

Push notifications

One of the methods of re-engaging users and boosting retention in your application is sending them push notifications. You can use this functionality built in the system and compare the metrics of users who received a notification with those who did not. To implement the push notification service, you need to:

Integrate devtodev SDK and activate push notifications during integration execution.

Fill in the required information in the push notifications panel in the Integration section of the application settings. You can get more detailed information in the corresponding section of the documentation.

Custom events

In addition to analyzing data using the main reports, which are based on basic events, you can integrate custom events to track and analyze specific user actions. By using custom events, you can find out what users do in the application, what functions are most popular, how they use various filters, change settings, which buttons press, whether they communicate with other users, whether they share your application with friends, and much more. For example, an event that gives you information about the most preferred login methods used in your application: Event name authorization Parameters method, e.g., fb, method (string) - authorization method: social networks, email. You can analyze custom event data in the Custom events report. You can also build a funnel and analyze the conversion at each stage, for example, you send the steps of purchasing goods in your application. Based on these events, you can build a funnel and use the Conversion funnel report to see the conversion at each stage. This will allow you to find the stages where you are losing potential customers.

Cohorts

To assess the dynamics of product quality, you can use a cohort analysis report that allows you to compare the behavior of different user cohorts (segments with different registration dates): how they are converted into purchase for the same period, how their retention rates change, how much they pay.

Users

The report allows you to get information about users. For each user you can see: basic properties, custom properties that are sent to the system, and information about user actions performed in the application. For example, if you build a conversion funnel for user actions, you will see how users move through the selected stages, but you will not see interim optional steps. Users may not be able to find the right button at once. Thus, by eliminating needless steps, you can optimize and streamline the user's path to the desired action.

You can find more information about the Users section in the documentation.

Levels

Reports with grouping by levels or information about levels are rarely used for non-gaming applications, but still, you can divide user progress in your application into several levels by prioritizing the application functions, and send them to us. If your project has a virtual currency, by using the LevelUp event you can send information about the current amount of virtual currency in users’ possession. To track virtual currency consumption and item popularity, add an In-app purchases event transmission immediately after purchase. These events help you estimate the average amount of virtual currency that users have at a certain level. The event should be sent as soon as the user moves to the next level. You can learn more about the event in the Integration section. For example, if a user has registered, we send information that they got to the first level, then after they have used filters when choosing an item, they earn some activity points, but don’t get to a new level, but if the user made the first purchase, they are moved to another level, etc. ... This provides an opportunity to build reports and create new hypotheses to boost your metrics. Level transmission gives you access to the In-game Analysis Dashboard, Economy Balance, Virtual Goods & Purchases, and Game Structure reports (Player levels tab).