App Usage Data

The App Usage Data request comprises of elements that can be combined to query your analytics data. The parameters that apply to this table:

https ://api-metrics.flurry.com/public/v1/data/appUsage/day/app/country?metrics=sessions,activeDevices,newDevices&dateTime=2017-06-01/2017-08-01&filters=[…]&topN=[..]&sort=[..]&having=[..]&format=[..]&timeZone=[..]

App Usage Metrics

Below are metrics that are available for reporting.

Metric

Description

sessions

number of times users accessed the application

activeDevices

total unique devices that accessed the application

activeUsers (*)

total unique users (based on app user id) that accessed the application

newDevices

new devices that installed and launched the application

timeSpent

time users spent (seconds) in the application

averageTimePerDevice

average time users spent (seconds) in the application per device

averageTimePerSession

average time users spent (seconds) in the application per session

medianTimePerSession

median time users spent (seconds) in the application per session

(*) requires app to use SDK API for setting app user id

App Usage Dimensions

Below are dimensions and dimension attributes that are available for reporting.

Dimension

Description

Value

company

Flurry company account

id, name (default)

app

Flurry app

id, name (default), company|id, apiKey, platform|id, platform|name

country

Per country dimension totals

id, name (default), iso

appVersion

App’s version id, name, company id, app id, deleted and filtered. Deleted and filtered are boolean (0 or 1) and reflect current status of an app version based on developer’s action on Flurry developer portal

id, name (default), company|id, app|id, deleted, filtered

language

Language id and name

id, name (default)

region

Region id and name

id, name (default)

category

App category id and name

id, name (default)

Time Grain

  • day

  • week

  • month

  • all

There are instances when you want to know the possible values for dimensions before running metric queries. For example: list names and api keys for all apps on your company account

https://api-metrics.flurry.com/public/v1/data/appUsage/day/company/app;show=name,apiKey?metrics=...

In general, to see a value other than defalut name returend for the given dimension, add

;show=all
or
;show=id  (any other value listed in the value column above for the given dimension

after the dimension name

https://api-metrics.flurry.com/public/v1/data/appUsage/day/company/country;show=all/category?metrics=sessions,activeDevices,newDevices,timeSpent&dateTime=2017-05-01/2017-05-02

https://api-metrics.flurry.com/public/v1/data/appUsage/day/company/country;show=iso/category?metrics=sessions,activeDevices,newDevices,timeSpent&dateTime=2017-05-01/2017-05-02

Refer to Analytics API for all the parameters, list of error codes and other general information about this API

Example key App Usage metrics queries

For all your apps, daily Sessions, daily Active Devices, New Devices for 2 days*: * note that since there is no app info included in the filter, results will include all apps for your company

Request:

https://api-metrics.flurry.com/public/v1/data/appUsage/day/app?metrics=sessions,activeDevices,newDevices&dateTime=2016-07-01/2016-07-03

Response:

{
        "rows": [{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "sessions": 372,
                "activeDevices": 123,
                "newDevices": 32},
        {
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "bar",
                "sessions": 1120,
                "activeDevices": 487,
                "newDevices": 34},
        {
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "sessions": 421,
                "activeDevices": 140,
                "newDevices": 12},
        {
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "bar",
                "sessions": 1164,
                "activeDevices": 453,
                "newDevices": 51}]
}

For a specific app, daily Sessions, Active Devices and New Devices for 2 months:

Request using Flurry API key:

https://api-metrics.flurry.com/public/v1/data/appUsage/day?metrics=sessions,activeDevices,newDevices&dateTime=2016-06-01/2016-08-01&filters=app|apiKey-in[3WD7Q8329867K7MY6RNS]

Request using App name:

https://api-metrics.flurry.com/public/v1/data/appUsage/day?metrics=sessions,activeDevices,newDevices&dateTime=2016-06-01/2016-08-01&filters=app|name-in[appname]

Response:

{
        "rows": [{
                "dateTime": "2016-06-01 00:00:00.000-07:00",
                "app|name": "foo",
                "sessions": 12744,
                "activeDevices": 6373,
                "newDevices": 6373
        },{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "sessions": 13805,
                "activeDevices": 6882,
                "newDevices": 6882
        }]
}