Analytics/Overview/Lexicon
Quick Links
Analytics Dictionary
Dictionary
This page contains a description and definition of all of the metrics and features 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.
Active Users
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.
Flurry leverages its vast amount of data to provide useful benchmarks for its customers. See how your application performance compares against category benchmarks on select metrics.
Carriers
Flurry provides data on the number of sessions generated by your users by carrier. Note that this data is not available for all sessions or on all platforms.
Track how well you convert users from free-to-paid applications or cross-sell within your portfolio.
Keep track of your app's errors and crashes by app version, device, and firmware. Drill down to the stack trace level to understand what is causing a crash or error.
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.
Devices
Flurry provides data on the number of sessions generated by device type. Note that the data we receive comes from the manufacturer of the device and is not available on all device types.
Firmware Versions
Flurry provides data on the number of sessions generated by firmware. Note that the data is not available on all platforms.
Use the collective knowledge of Flurry to estimate your users' age and gender distribution.
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.
Total Sessions, Average Active Users Per Day, Total New Users, Median Session Length and Percent Users Retained broken down by geographic area of use.
Measure your end users' interests across your apps and against category interest indices.
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.
Group a set of users by date and measure their rolling retention rates.
New Users
A new user is a user who has just started using your application. Users are identified by their unique device IDs (which vary by platform). We recognize someone as a new user when they first launch your application. If a user has downloaded but not ever launched your app, they will not be counted. If a user deletes and re-installs your app to the same device or upgrades to a new version, they will not be re-counted. If a user obtains a new device and downloads your application to that device, they will be counted again as a new user.
Page Views
Page views allow you to see how many discrete sections of your app are being accessed. You decide how you want to define a page view. See our Technical Quick Start for documentation on how to implement page views in your app.
View summaries for your entire portfolio, analyzing your users by category, platform and device.
Create cohorts of users and analyze how they vary in usage and behavior. Identify your most engaged and valuable users.
Sessions
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.
Session Length
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.
Time of Day & Hourly Reporting
With time of day reporting you can view the usage of your app based on the user's local time. Hourly reporting provides a finer granularity allowing you to see usage on an hour by hour basis.
Flurry User Acquisition Analytics (UAA) is a channel tracking solution that can track all of the install campaigns you are running across different channels (e.g. ad networks, mobile web, email) and help you understand the quality of users being acquired.
User Paths
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.
User Retention
User retention is a measure of how long a given user remains an active user after they are a new user. More specifically, it is a measure of how many of your users are still considered retained users.
Track which versions of your applications are currently in use and how usage evolves over time as users upgrade.