Mobile metrics and dimensions reference
This information helps you understand more about the default mobile metrics and dimensions.
The dimension and metric permissions that are set in Adobe Analytics apply to Mobile Services. When you try to run a report without the proper permissions, an error occurs.
Here is the list of default mobile metrics:
- First LaunchesTriggered on the first run after an installation or a re-installation.
- UpgradesTriggered on the first run after an upgrade or when the version number changes.
- Daily Engaged UsersTriggered when the application is used on a particular day.The Daily Engaged Users event 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 UsersTriggered when the application is used during a month.The Monthly Engaged Users event is not automatically stored in an Analytics metric. You must create a processing rule that sets a custom event to capture this metric.
- LaunchesTriggered on a run that is not an install or an upgrade. This also triggers when the application is brought out of the background. By default, a new launch triggers when the application is in the background for five or more minutes. The amount of background time before triggering a new launch can be configured in SDK Analytics Options on the Manage App Settings page. For more information, see the Session Timeout (Seconds) row in Configure SDK Analytics Options .Because how visits in Adobe Analytics and mobile app launches in Adobe Mobile Services are calculated, you might see different results in reporting. For more information, see Compare Visits and Mobile App Launches .
- CrashesTriggered when the application does not correctly exit. This event is sent when the application starts after a crash.The application is considered to crash if quit is not called.
- Total Session LengthAggregated total session length.
Here is the list of default mobile dimensions:
- Install DateDate of the first launch after the installation. The date is in the MM/DD/YYYY format.
- App IDStores the Application name and version in the following format: [AppName] [BundleVersion] . For example, myapp 1.1 .
- Launch NumberNumber of times the application was launched or brought out of the background.
- Days Since First UseNumber of days since the first run.
- Days Since Last UseNumber of days since the last use.
- Hour of DayMeasures the hour in which the app was launched and uses the 24-hour numerical format. This dimension is also used for time parting to determine peak usage times.
- Day of WeekNumber of the week day the app was launched.
- Operating SystemOperating system of the device.
- Operating System VersionOperating system version.
- Days Since Last UpgradeNumber of days since the application version number has changed.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 UpgradeNumber of launches since the application version number has changed.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 NameStores the device name. In iOS, a comma-separated, two-digit string identifies the iOS device. The first number represents the device generation, and the second number versions different members of the device family. For a complete list of common device names, see iOS Device Versions .
- Carrier NameStores the name of the mobile service provider.
- ResolutionWidth and height in actual pixels.