Crash Summary Data

The Crash Summary Data request comprises of elements that can be combined to query data related to crashes and other issues recorded by the Flurry SDK. The parameters that apply to this table:

https ://,activeDevices,deviceImpactRate&dateTime=2019-06-01/2019-08-01&filters=[…]&topN=[..]&sort=[..]&having=[..]&format=[..]

Crash Summary Metrics

Below are metrics that are available for reporting.




number of times users accessed the application where an issue occurred


total unique devices that accessed the application where an issue occurred


total number of issues that occurred


the ratio unique devices that experienced an issue to the unique devices that launched the app


the ratio sessions that experienced an issue to the number of time users accessed the app


1 minus the deviceImpactRate


1 minus the sessionImpactRate

Crash Summary Dimensions

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





Flurry company account

id, name (default)


Flurry app

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


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


Crash, Handled Exception, Logged Error

id, name (default)


OS Version running at time of issue

id, name (default)

Time Grain

  • day

  • week

  • month

  • all

Data Retention

The data in the Crash Report Summary table is retained for all time.

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 with Crash enabled;show=name,apiKey?metrics=...

In general, to see a value other than default name returned for the given dimension, add

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

after the dimension name;show=all/category?metrics=sessions,activeDevices&dateTime=2017-05-01/2017-05-02;show=iso/category?metrics=sessions,activeDevices&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



        "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:,activeDevices,newDevices&dateTime=2019-06-01/2019-08-01&filters=app|apiKey-in[3WD7Q8329867K7MY6RNS]

Request using App name:,activeDevices,newDevices&dateTime=2019-06-01/2019-08-01&filters=app|name-in[appname]