Lists the metrics and dimensions that can be measured automatically by the mobile library.
For more information, see Troubleshoot Lifecycle data.
When configured, lifecycle metrics are sent in context data parameters to Analytics, in parameters to Target with each mbox call, and as a signal to Audience Manager. Analytics and Target use the same format, and Audience Manager uses a different prefix for each metric.
For Analytics, the context data that is sent with each lifecycle tracking call is automatically captured in and reported on by using the metric or dimension listed below, and exceptions are noted.
First Launches
Triggered at the first run after installation or re-installation.
a.InstallEvent
c_a_InstallEvent
Upgrades
Triggered at the first run after an upgrade or when the version number changes.
a.UpgradeEvent
c_a_UpgradeEvent
Daily Engaged Users
Triggered when the application is used on a particular day.
This metric is not automatically stored in an Analytics metric. You must create a processing rule that sets a custom event to capture this metric.
a.DailyEngUserEvent
c_a_DailyEngUserEvent
Monthly Engaged Users
Triggered when the application is used during a particular month.
This metric is not automatically stored in an Analytics metric. You must create a processing rule that sets a custom event to capture this metric.
a.MonthlyEngUserEvent
c_a_MonthlyEngUserEvent
Launches
Triggered at every run, including crashes and installs. Also triggered on a resume from the background when the lifecycle session timeout has been exceeded.
a.LaunchEvent
c_a_LaunchEvent
Crashes
Triggered when the application is not backgrounded before being closed. The event is sent when the application is started after the crash. Adobe Mobile crash reporting does not implement a global uncaught exception handler.
a.CrashEvent
c_a_CrashEvent
Previous Session Length
Reports the number of seconds that a previous application session lasted, based on how long the application was open and in the foreground.
a.PrevSessionLength
c_a_PrevSessionLength
Install Date
Date of first launch after installation. The date format is MM/DD/YYYY
.
a.InstallDate
c_a_InstallDate
App ID
Stores the application name and version in the [AppName] [BundleVersion]
format. An example of this format is myapp 1.1
.
a.AppID
c_a_AppID
Launch Number
Number of times the application was launched or brought out of the background.
a.Launches
c_a_Launches
Days since first use
Number of days since the first run.
a.DaysSinceFirstUse
c_a_DaysSinceFirstUse
Days since last use
Number of days since the last use.
a.DaysSinceLastUse
c_a_DaysSinceLastUse
Hour of Day
Measures the hour that the app was launched. This metric uses the 24-hour numerical format and is used for time parting to determine peak usage times.
a.HourOfDay
c_a_HourOfDay
Day of Week
Number of the day in a week when the app was launched.
a.DayOfWeek
c_a_DayOfWeek
Operating System Version
The OS version.
a.OSVersion
c_a_OSVersion
Days since last upgrade
Number of days since the application version number has changed.
This metric is not automatically stored in an Analytics variable. You must create a processing rule to copy this value to an Analytics variable for reporting.
a.DaysSinceLastUpgrade
c_a_DaysSinceLastUpgrade
Launches since last upgrade
Number of launches since the application version number has changed.
This metric is not automatically stored in an Analytics variable. You must create a processing rule to copy this value to an Analytics variable for reporting.
a.LaunchesSinceUpgrade
c_a_LaunchesSinceUpgrade
Device Name
Stores the device name.
a.DeviceName
c_a_DeviceName
Carrier Name
Stores the name of the mobile service provider as provided by the device.
This metric is not automatically stored in an Analytics variable. You must create a processing rule to copy this value to an Analytics variable for reporting.
a.CarrierName
c_a_CarrierName
Resolution
Width x Height in actual pixels.
a.Resolution
c_a_Resolution
The following metrics and dimensions are captured in mobile solution variables by the methods listed in the description.
Action Time Total
Populated by trackTimedAction
methods.
a.action.time.total
c_a_action_time_total
Action Time In App
Populated by trackTimedAction
methods.
a.action.time.inapp
c_a_action_time_inapp
Lifetime Value (event)
Populated by trackLifetimeValue
methods.
a.ltv.amount
c_a_ltv_amount
Location (down to 10 km)
Populated by trackLocation
methods.
Analytics context data/Target parameter:
a.loc.lat.a
a.loc.lon.a
Audience Manager trait:
c_a_loc_lat_a
c_a_loc_lon_a
Location (down to 100 m)
Populated by trackLocation
methods.
Analytics context data/Target parameter:
a.loc.lat.b
a.loc.lon.b
Audience Manager trait:
c_a_loc_lat_b
c_a_loc_lon_b
Location (down to 1 m)
Populated by trackLocation
methods.
Analytics context data/Target parameter:
a.loc.lat.c
a.loc.lon.c
Audience Manager trait:
c_a_loc_lat_c
c_a_loc_lon_c
Point of Interest Name
Populated by trackLocation
methods when device is within a defined POI.
a.loc.poi
c_a_loc_poi
Distance to Point of Interest Center
Populated by trackLocation
methods when device is within a defined POI.
a.loc.dist
c_a_loc_dist
Lifetime Value (conversion variable)
Populated by trackLifetimeValue
methods.
a.ltv.amount
c_a_ltv_amount