This page describes all the metrics and features available in Flurry Analytics, organized in alphabetical order. Many of the features listed below are quite comprehensive and may have a link to a separate page with further detail.
An active user is defined as a user that has had at least one session with your application during a given time period (days, weeks, months). If a user launches more than one session during a given period, they will only be counted once.
Receive alerts when the metrics you care about surpass thresholds that you set. This can be done on app usage metrics as well as crash metrics.
Learn more at Alerts.
Flurry provides various app usage metrics generated by your users by carrier. Note that this data is not available for all sessions or on all platforms.
Demographics: Age and Gender
See how your users break down along the lines of age and gender. If you provide this information to Flurry, we will report it back to you. If you don’t gather this information from your users, we have built smart algorithms to provide you estimates on these dimensions.
Learn more at Demographics.
Flurry provides data on the number of sessions generated by device model type. Note that the data we receive comes from the manufacturer of the device and is not available on all device types. We map devices on our end frequently, but for Android, the sheer number of devices available means that not all devices get mapped. These unmapped devices register as unknown in our system.
Events allow you to understand all of the specific in-app activities of your users - e.g. “Song Played”, “Article Read”, or “Level Completed”. Flurry provides information on how often an Event occurs, how many unique users trigger an Event, etc.
Learn more at Events.
The Event Summary table lists all the events that are set up in your app.
Learn more at Event Summary.
Frequency of Use
Frequency of use is a measure of how many sessions unique users had over a given period of time. Frequency is tracked on an individual user basis so aggregated metrics represent actual averages and not estimates.
Funnels track users as they execute a defined set of steps, allowing you to see how many of the users that started a given process completed it. For those that did not complete the process, funnels show you at which step they exited.
Learn more at Funnels.
Total Sessions, Average Active Users Per Day, Total New Users, Median Session Length and Percent Users Retained broken down by geographic area of use.
Learn more at Geographic Usage.
Language metrics allow you to view the number of new users, sessions, active users, and retained users by the languages your users’ devices are set to. Drill down further to understand which countries these users are from.
Learn more at Language Metrics.
A New Device is a device who has just started using your application. Devices are identified by their unique device IDs (which vary by platform). We recognize a device as new when it first launches your application. If a device has downloaded but not ever launched your app, it will not be counted. If an app is deleted from a device and then re-installed to the same device or is upgraded to a new version, it will not be re-counted. If an end user obtains a new device and downloads your application to that device, this will be counted as a new device.
Flurry provides data on the number of sessions generated by OS Version. Note that the data is not available on all platforms.
Page views, as they are traditionally used, are tracked in Flurry as Custom Events. This additional metric in the “Usage” menu allows you to define what a page view is and log the total number of page views logged in aggregate for your app.
Learn more at Page Views.
View summaries for your entire portfolio, analyzing your users by category, platform and device.
Recent Users looks at your users by cohort, based on when they first launched your application, and measures whether they are still “active.” For this metric, a “retained user” is a user that has had at least one session with your application in the past seven days (from today’s date).
A restricted version of Flurry’s Analytics product entails certain key differences from the complete version of the Analytics product. It restricts the use of device identifiers to only provide analytics for your particular application.
Learn more at Restricted Set.
Return Rate measures the percentage of your users who return to your app on a given day, week, or month post-install. We can look at this value by cohort group, that is, based on when users first started using your app.
The metric is calculated as the ratio of the number of users active during a particular day, week or month compared to the size of the cohort group.
Revenue Analytics within Flurry allows you to track your In App Purchase (IAP) Revenue from transactions that occur within your iOS or Android app in order to determine if your app is producing revenue from in app purchases at the levels you expect.
Learn more at Revenue Analytics.
Understand user churn from your application and identify key drop off points.
Learn more at Rolling Retention.
Create cohorts of users and analyze how they vary in usage and behavior. Identify your most engaged and valuable users.
Learn more at User Segments.
A session is one use of the application by an end user. This typically begins when the application is launched and ends when the application is terminated. Depending on the platform, the Flurry SDK may allow you to specify when a session starts and stops, in which case the definition can vary depending on your implementation. Note that the definition of session does not depend on how many screens are viewed in the application or how long the application is used.
If a user has a session with your application while they are offline, the data will be stored locally on the device and sent to Flurry the next time the user opens the app and is online, so you will not lose that data.
The session length is defined simply as the length of time between the start application event and the end application event which can vary by platform. There are some circumstances, including application crashes, where no end time can be recorded and hence the session length is unknown. Those instances are not included in our average and median session length calculation. The length of the session can vary based on how you integrate the SDK into your application if you do not follow the recommended practices.
See how users navigate through your app based on the custom Events they are triggering. This data is automatically calculated for you and can provide valuable insights as to whether there are any bottlenecks or unexpected pathways occurring in your application.
Learn more at User Paths.
Track which versions of your applications are currently in use and how usage evolves over time as users upgrade.
Learn more at Versions.