App Events Data

The API request comprises of elements that can be combined to query your the app events data. All paramters apply to this table:

https://api-metrics.flurry.com/public/v1/data/appEvent/day/app/appVersion/event?metrics=occurrences&dateTime=2016-07-01/2016-07-03&filters=[…]&topN=[..]&sort=[..]&having=[..]&format=[..]&timeZone=[..]

App Event Metrics

Below are metrics that are available for reporting.

Metric

Description

activeDevices

total unique devices that accessed the application

newDevices

new devices that installed and launched the application

eventDuration

duration of timed event (milliseconds)

averageEventDuration

average duration for timed event (milliseconds)

averageEventDurationPerDevice

average duration for timed event per active device (milliseconds)

occurrences

number of times an event occurred

App Event 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)

event

Availble for appEvent table only; Event id, name, app id, company id, deleted and filtered. Deleted and filtered are boolean (0 or 1) and reflect current status of an app event based on developer’s action on Flurry developer portal.

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

App Event 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/appEvent/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/appEvent/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/appEvent/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 gerneal information about this API

Example key app event metrics queries

For a specific app events, event occurrences broken by app version for 2 days:

Request:

https://api-metrics.flurry.com/public/v1/data/appEvent/day/app/appVersion/event?metrics=occurrences&dateTime=2016-07-01/2016-07-03&filters=app|name-in[foo],event|name-in[login,register]

Response:

{
        "rows": [{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "occurrences": 293
        },{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "register",
                "occurrences": 57
        },{
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "occurrences": 146
        },{
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "register",
                "occurrences": 31
        }]
}

For a specific app event, Active Devices and New Devices for Top 5 Countries sorted by Active Devices for 2 days:

Request:

https://api-metrics.flurry.com/public/v1/data/appEvent/day/app/country?metrics=activeDevices,newDevices&dateTime=2016-07-01/2016-07-03&filters=app|name-in[foo],event|name-in[login]&topN=5&sort=activeDevices|desc

Response:

{
        "rows": [{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "United States",
                "occurrences": 515
        },{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "United Kingdom",
                "occurrences": 210
        },{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "Canada",
                "occurrences": 165
        },{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "Germany",
                "occurrences": 87
        },{
                "dateTime": "2016-07-01 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "France",
                "occurrences": 46
        },{
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "United States",
                "occurrences": 435
        },{
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "United Kingdom",
                "occurrences": 190
        },{
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "Canada",
                "occurrences": 127
        },{
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "Germany",
                "occurrences": 76
        },{
                "dateTime": "2016-07-02 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "country|name": "France",
                "occurrences": 39
        }]
}

App Event Parameter Data

The API request comprises of elements that can be combined to query your the app events data. All paramters apply to this table:

https:// api-metrics.flurry.com/public/v1/data/eventParams/day/app;show=all/event/paramName/paramValue?metrics=count&filters=app|name-in[foo],event|name-in[level_complete]&dateTime=2016-11-07/2016-11-08

App Event Param Metrics

Below are metrics that are available for reporting.

Metric

Description

count

number of times specific value was recorded for an event param

App Event Param 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)

event

Availble for appEvent table only; Event id, name, app id, company id, deleted and filtered. Deleted and filtered are boolean (0 or 1) and reflect current status of an app event based on developer’s action on Flurry developer portal.

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

paramName

Name of event param. Available for eventParams table only; Param id, name

paramValue

Value of event param. Available for eventParams table only; Value id, name

App Event Param Time Grain

  • day

  • week

  • month

  • all

Example app event parameter metrics query

For a specific app event, provide event parameter values breakdown for 1 day:

Request:

https:// api-metrics.flurry.com/public/v1/data/eventParams/day/app;show=all/event/paramName/paramValue?metrics=count&filters=app|name-in[foo],event|name-in[level_complete]&dateTime=2016-11-07/2016-11-08

Response:

{
        "rows": [{
                "dateTime": "2016-11-07 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "level_complete",
                "paramName|name": "level",
                "paramValue|name": "1",
                "count": 32
        },{
                "dateTime": "2016-11-07 00:00:00.000-07:00",
                "app|name": "foo",
                "event|name": "login",
                "paramName|name": "level",
                "paramValue|name": "2",
                "count": 15
        }]
}