Mobile Analytics provides details about the performance of your mobile apps as experienced by your end users. The data collected includes information about the mobile app names and versions, network requests, performance times, locations, carrier and device data, errors, and any custom data that you configured in your Mobile RUM configuration.
This page describes the field names available for mobile requests Analytics data, along with the Events Service internal name. See Mobile RUM Metrics. When accessing the data using ADQL queries, you need to use the Events Service internal name in the query.
Event Type: mobile_snapshots
Key (event type identifier): appkey
UI Field Name | Events Service Internal Name |
---|---|
Mobile App Info Fields | |
agentid | agentid |
agentversion | agentversion |
appkey | appkey |
cguid | cguid |
Mobile App Name |
For example: "com.appdynamics.eum.test.apps.E2E-PictureSharingApp" |
Mobile App Version | mobileappversion |
Platform | platform |
Network Request Fields | |
Background | happenedinbackground |
Experience | networkrequestexperience |
HTTP Status Code | httpstatuscode |
Network Request Name | networkrequestname |
Network Request Type | networkrequesttype |
Request Content Length | requestContentLength |
Response Content Length | responseContentLength |
Performance Time Fields | |
Estimated BT Time | btdata.estimatedtime |
Network Request Time | networkrequesttime |
Location Fields | |
Country | geocountry |
Region | georegion |
Carrier and Device Data Fields | |
Carrier | carrier |
Connection Type |
For example: "wifi", "4g", "cell" |
Device / Manufacturer |
For example: "Samsung", "Apple" |
Model |
For example: "iPhone 5" "iPad 2 WIFI" |
OS Version |
For example: "iOS 6.0", "Android 4.2" |
Error Fields | |
Network Type Error | networkerror |
Custom User Data Fields | |
your_field_name | userdata.your_field_name userdataBoolean.your_field_name userdataDate.your_field_name userdataLong.your_field_name userdataDouble.your_field_name If your field name contains spaces or any reserved characters, the field name must be surrounded by backquotes. For example, if you define a custom field called "Item Purchased", the Events Service field name is |