Mobile SDK Statistics

Integrating the appropriate SDK with your Android and iOS apps not only lets you update translations with a single click, but also provides you with metrics to measure its usage. Our mobile SDK statistics give you valuable insights on your active app users and their app languages. Currently, you can access this set of statistics for each of your distributions. Your data gets updated with a delay of under 10 minutes. 

How to access your statistics

You can access the statistics for each distribution via the statistics button next to the settings.

Active users

This graph shows the active unique users you have had within the past 30 days. By clicking on the labels you can choose between displaying solely the number of users on iOS, Android or both combined.

Overall Requests

Choose to see the number of overall requests per platform or both combined. The data is provided on a daily basis and gives you an impression of your app usage over the past 30 days.

Requests per locale & platform

Every time one of your app users starts the app, our SDK automatically checks for updated translations in Phrase (and downloads them in the background). We count this as a request.
On the left hand side graph, you can see which locales are requested the most for your respective distribution (unique by user), giving you insights on the most requested languages.
On the right hand side graph, you see the app requests per platform (also unique by user). This might help you in deciding which languages and platforms to prioritize. Compared to the overall requests graph, this provides you with the total amount of requests for the past 30 days.

Locales not provided

This table shows you the most requested, but not provided locales, ranked by the total share of overall requests. You can learn which locales you might want to add to your project in order to increase your app's global adaptation and user experience. Simply click on Add Locale to add the respective language in no time. If you're using Autopilot, the translations for this locale would already be pre-filled automatically, using translation memory and machine translation.

Did this answer your question?