App Reporting

The App Reporting interface allows you to enable lifecycle dimensions and metrics that are dedicated for use in mobile application tracking.

Analytics > Admin > Report Suites > Edit Settings > App Management > App Reporting

Once any of these features are enabled, they cannot be disabled. Enabling a given feature makes its respective dimensions and metrics permanently available in Analysis Workspace.

App Reports

App Reports dimensions and metrics are used for the following purposes:

  • Acquisition: Track referring URLs for app download campaigns.
  • Lifecycle: Foundation level of reporting provided by measurement sent on each app launch.
  • App Actions: Reports and pathing based on in-app actions.
  • Lifetime Value: Understand how users accrue value over time using app KPIs (such as purchases, ad views, video completes, social shares, photo uploads).
  • Timed Events: Measure the amount of time that elapses (in-app & total time) between key app actions (such as time before first purchase).

When you enable App Reports, the following dimensions are available:

  • Action Name (with Entry and Exit dimensions)
  • App Id
  • Acquisition Content
  • Acquisition Medium
  • Acquisition Name
  • Acquisition Source
  • Acquisition Term
  • Day of Week (SDK)
  • Days Since First Use
  • Days Since Last Use
  • Device Name (SDK)
  • Hour of Day (SDK)
  • First Launch Date
  • Launch Number
  • Lifetime Value (evar)
  • Operating System Version (SDK)
  • Resolution (SDK)

The following metrics are available:

  • Action Time In App
  • Action Time Total
  • Crashes
  • First Launches
  • Launches
  • Lifetime Value (event)
  • Total Session Length
  • Upgrades

Location Tracking

Location Tracking dimensions are used for the following purposes:

  • Track latitude and longitude data
  • Identify, create, and visualize specific Points of interest. Points of interest must be defined in the mobile SDK configuration file.
  • Track bluetooth beacons (UUID, major, minor, and proximity).

When you enable Location Tracking, the following dimensions are available:

  • Beacon Major (with Entry and Exit dimensions)
  • Beacon Minor (with Entry and Exit dimensions)
  • Beacon Proximity (with Entry and Exit dimensions)
  • Beacon UUID (with Entry and Exit dimensions)
  • Location (down to 10 km)
  • Location (down to 100 m)
  • Location (down to 1 m)
  • Point of Interest Name
  • Distance to Point of Interest Center
  • Point of Interest ID

Voice and Chatbots

Voice and Chatbots dimensions and metrics allow you to measure voice assistants such as Alexa or Google Home. It also allows you to measure home-grown chat bots. Measurement properties include:

  • Lifecycle: Foundation level of reporting for any app, such as the number of launches and platform type.
  • Conversations: Measures intents, responses, and other metrics and dimensions related to the conversation.

When you enable Voice and Chatbots, the following dimensions are available:

  • Voice Device Capabilities (with Entry and Exit dimensions)
  • Voice Authentication
  • Voice Error Type
  • Voice Intent
  • Voice App Response
  • Voice Language

The following metrics are available:

  • Voice End Session
  • Voice Error
  • Voice Utterances

Legacy Reporting and Attribution for Background Hits

Legacy reporting means that hits generated when an app is in the background are treated as regular foreground hits. They show up in reports and affect attribution. This legacy configuration is typically desirable to maintain consistency with legacy implementations.

Adobe recommends disabling legacy reporting so that background hits are not visible. If you want to include background hits in your analysis, you can enable the Virtual report suite setting Include background hits.