Lifecycle Metrics

This worksheet lists the metrics and dimensions that are measured when automatic lifecycle tracking is enabled.

Lifecycle Metrics and Dimensions

When configured, lifecycle metrics are sent in context data parameters to Analytics, 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 using the metric or dimension listed in the first column, with the exceptions noted in the description column.

Metric Analytics Context Data/Target Parameter Audience Manager Signal Description

First Launces

a.InstallEvent

c_a_InstallEvent

Triggered on first run after installation (or re-installation).

Upgrades

a.UpgradeEvent

c_a_UpgradeEvent

Triggered on first run after upgrade (anytime the version number changes).

Daily Engaged Users

a.DailyEngUserEvent

c_a_DailyEngUserEvent

Triggered when the application is used on a particular day.

Note: Daily Engaged Users is not automatically stored in an Analytics metric. You must create a processing rule that sets a custom event to capture this metric.

Monthly Engaged Users

Monthly Engaged Users

a.MonthlyEngUserEvent

Triggered when the application is used during a particular month.

Note: Monthly Engaged Users is not automatically stored in an Analytics metric. You must create a processing rule that sets a custom event to capture this metric.
Note:

Launches

a.LaunchEvent

c_a_LaunchEvent

Triggered on every run, including crashes and installs. Also triggered on a resume from background when the lifecycle session timeout has been exceeded.

Crashes

a.CrashEvent

c_a_CrashEvent

Triggered when the application does not exit gracefully. Event is sent on application start after crash (the application is considered to crash if quit is not called).

Previous Session Length

a.PreviousSessionLength

Cc_a_PreviousSessionLength

Aggregated total Previous Session Length in seconds.

Dimensions

Metric Analytics Context Data/Target Parameter Audience Manager Signal Description

Install Date

a.InstallDate

c_a_InstallDate

Date of first launch after installation. MM/DD/YYYY

App ID

a.AppID

c_a_AppID

Stores the Application name and version in the following format:

[AppName] [BundleVersion]

For example, myapp 1.1

Days since first use

a.DaysSinceFirstUse

c_a_DaysSinceFirstUse

Number of days since first run.

Days since last use

a.DaysSinceLastUse

c_a_DaysSinceLastUse

Number of days since last use.

Day of Week

a.DayOfWeek

c_a_DayOfWeek

Number of the week day the app was launched.

Hour of Day

a.HourOfDay

c_a_HourOfDay

Measures the hour the app was launched. 24 hour numerical format. Used for time parting to determine peak usage times.

Day of Week

a.DayOfWeek

c_a_DayOfWeek

Number of the week day the app was launched.

Operating System Version

a.OSVersion

c_a_OSVersion

OS version.

Days since last upgrade

a.DaysSinceLastUpgrade

c_a_DaysSinceLastUpgrade

Number of days since the application version number has changed.

Note: Days since last upgrade is not automatically stored in an Analytics variable. You must create a processing rule to copy this value to an Analytics variable for reporting.

Launches since last upgrade

a.LaunchesSinceUpgrade

c_a_LaunchesSinceUpgrade

Number of launches since the application version number has changed.

Note: Launches since last upgrade is not automatically stored in an Analytics variable. You must create a processing rule to copy this value to an Analytics variable for reporting.

Device Name

a.DeviceName

c_a_DeviceName

Stores the device name.

iOS: Comma-separated 2 digit string that Identifies the iOS device. The first number typically represents the device generation, and the second number typically versions different members of the device family. See iOS Device Versions for a list of common device names.

Carrier Name

a.CarrierName

c_a_CarrierName

Stores the name of the mobile service provider as provided by the device.

Note: Carrier name is not automatically stored in an Analytics variable. You must create a processing rule to copy this value to an Analytics variable for reporting.

Resolution

a.Resolution

c_a_Resolution

Width x Height in actual pixels