Here are the metrics and dimensions that can be measured automatically by the mobile library, after lifecycle is implemented, and a link to troubleshoot Lifecycle data.
For more information, go to the Knowledge Base at 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 management. Analytics and Target use the same format, while audience management 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.
-
a.media.name
Triggered at the first run after installation or re-installation.
- Analytics context data/Target parameter:
a.InstallEvent
- Audience Manager signal:
c_a_InstallEvent
- Analytics context data/Target parameter:
-
Upgrades
Triggered at the first run after an upgrade or when the version number changes.
- Analytics context data/Target parameter:
a.UpgradeEvent
- Audience Manager signal:
c_a_UpgradeEvent
- Analytics context data/Target parameter:
-
Daily Engaged Users
Triggered when the application is used on a particular day.
Important: 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.
- Analytics context data/Target parameter:
a.DailyEngUserEvent
- Audience Manager signal:
c_a_DailyEngUserEvent
- Analytics context data/Target parameter:
-
Monthly Engaged Users
Triggered when the application is used during a particular month. >>>>
Important: 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.
- Analytics context data/Target parameter:
a.MonthlyEngUserEvent
- Audience Manager signal:
c_a_MonthlyEngUserEvent
- Analytics context data/Target parameter:
-
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.
- Analytics context data/Target parameter:
a.LaunchEvent
- Audience Manager signal:
c_a_LaunchEvent
- Analytics context data/Target parameter:
-
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.
- Analytics context data/Target parameter:
a.CrashEvent
- Audience Manager signal:
c_a_CrashEvent
- Analytics context data/Target parameter:
-
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.
- Analytics context data/Target parameter:
a.PrevSessionLength
- Audience Manager signal:
c_a_PrevSessionLength
- Analytics context data/Target parameter:
-
Install Date
Date of first launch after installation. The date format is
MM/DD/YYYY
.- Analytics context data/Target parameter:
a.InstallDate
- Audience Manager signal:
c_a_InstallDate
- Analytics context data/Target parameter:
-
App ID
Stores the application name and version in the following format:
[AppName] [BundleVersion]
.An example of this format is
myapp 1.1
.- Analytics context data/Target parameter:
a.AppID
- Audience Manager signal:
c_a_AppID
- Analytics context data/Target parameter:
-
Launch Number
Number of times the application was launched or brought out of the background.
- Analytics context data/Target parameter:
a.Launches
- Audience Manager signal:
c_a_Launches
- Analytics context data/Target parameter:
-
Days since first use
Number of days since the first run.
- Analytics context data/Target parameter:
a.DaysSinceFirstUse
- Audience Manager signal:
c_a_DaysSinceFirstUse
- Analytics context data/Target parameter:
-
Days since last use
Number of days since the last use.
- Analytics context data/Target parameter:
a.DaysSinceLastUse
- Audience Manager signal:
c_a_DaysSinceLastUse
- Analytics context data/Target parameter:
-
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.
- Analytics context data/Target parameter:
a.HourOfDay
- Audience Manager signal:
c_a_HourOfDay
- Analytics context data/Target parameter:
-
Day of Week
Number of the day in a week when the app was launched.
- Analytics context data/Target parameter:
a.DayOfWeek
- Audience Manager signal:
c_a_DayOfWeek
- Analytics context data/Target parameter:
-
Operating System Version
The version of the OS.
- Analytics context data/Target parameter:
a.OSVersion
- Audience Manager signal:
c_a_OSVersion
- Analytics context data/Target parameter:
-
Days since last upgrade
Number of days since the application version number has changed.
Important: 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.
- Analytics context data/Target parameter:
a.DaysSinceLastUpgrade
- Audience Manager signal:
c_a_DaysSinceLastUpgrade
- Analytics context data/Target parameter:
-
Launches since last upgrade
Number of launches since the application version number has changed.
Important: 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.
- Analytics context data/Target parameter:
a.LaunchesSinceUpgrade
- Audience Manager signal:
c_a_LaunchesSinceUpgrade
- Analytics context data/Target parameter:
-
Device Name
Stores the device name.
- Analytics context data/Target parameter:
a.DeviceName
- Audience Manager signal:
c_a_DeviceName
- Analytics context data/Target parameter:
-
Carrier Name
Stores the name of the mobile service provider as provided by the device.
Important: 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.
- Analytics context data/Target parameter:
a.CarrierName
- Audience Manager signal:
c_a_CarrierName
- Analytics context data/Target parameter:
-
Resolution
Width x Height in actual pixels.
- Analytics context data/Target parameter:
a.Resolution
- Audience Manager signal:
c_a_Resolution
- Analytics context data/Target parameter:
The following metrics and dimensions are captured in mobile solution variables by the listed method.
-
Location (down to 10 km)
Populated by
trackLocation
methods.-
Analytics context data/Target parameter:
a.loc.lat.a
a.loc.lon.a
-
Audience Management 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 Management 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 Management 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.-
Analytics context data/Target parameter:
a.loc.poi
-
Audience Management trait:
c_a_loc_poi
-
-
Distance to Point of Interest Center
Populated by
trackLocation
methods when device is within a defined POI.-
Analytics context data/Target parameter:
a.loc.dist
-
Audience Management trait:
c_a_loc_dist
-