Analytics Report Guide for AEM Mobile

Apps are preconfigured to report analytics information to Adobe data centers. This information contains metrics related to the life cycle of the application including app-specific data. Apps all report the same information and cannot be customized at this time.

Supported app platforms are iOS 8.1 and later, Android 4.4 and later, Windows 8.1 and 10, and the two most recent versions of desktop web browsers for Desktop Web Viewer.

This document describes the reports, the data collected and the associated events. It also describes the app-specific reports and menu options configured in Adobe Analytics.

For information on configuring or setting up your project for analytics, please see Analytics for AEM Mobile.

The document uses the following terminology which represents the current status quo within our products. Please keep in mind that these terms have evolved over time.

Adobe Analytics — This is broad term encompassing all of Adobe’s Analytics offerings, but will be used herein to describe tools formerly associated with SiteCatalyst and officially branded as “Reports & Analytics”.

Adobe Analytics Essentials  — This is a component of Adobe Mobile Services which is part of the Adobe Marketing Cloud. This portal is specific to Mobile and can include other mobile components such as Adobe Target.

Data Center — Adobe maintains 5 active data centers where Analytics data is stored. These are roughly located in San Jose, Dallas, Oregon, London and Singapore. All analytics data for a specific master account will be stored in a single data center.

Apps are compiled with the Mobile Services SDK included for each platform. SDKs are updated as they become released. At the time, the SDK versions included are iOS: 4.6; Android: 4.6; and Windows: 4.0.

The Mobile Services SDK automatically reports a number of life cycle metrics. Apps augment this with  specific reports. All the data is transmitted within a JSON graph. These JSON variables have server processing rules applied to them when received and prior to the variables being stored for Analytics reporting.

After the data is stored in a data center, it can be visualized within 2 distinct tools: Adobe Analytics Essentials or Adobe Reports & Analytics.

Reports & Analytics is a paid subscription service, typically purchased as “Adobe Analytics – Standard,” “Adobe Analytics – Premium,” or "Mobile Analytics.” Customers who purchase Analytics have the best available tools for inspecting their app data.

For every project created, a report suite is automatically created that contains a customized Adobe Analytics menu. This menu contains standard Analytics visualizations and tools (such as Path, Dashboards, Favorites, App and Mobile metrics) and app-specific items (such as Articles, Collections, Banners).

If you want to further customize this menu, please contact your Analytics Administrator.

When you select a menu item, you can view the corresponding report.

Every AEM Mobile enterprise customer receives complimentary access to Adobe Analytics Essentials for Apps (Analytics Essentials). This is a part of the Mobile Marketing Core Services and provides a mobile specific view into your apps’ analytics. This portal is also the mobile-specific entry to other premium mobile products such as In-App Messaging, Acquisition Tracking, and Location and Target. Premium mobile products require an additional paid subscription.

Analytics Essentials provides an easy and highly visual insight into the life cycle metrics of your applications. It shows information about Usage, Technology, Pathing and Retention. Viewing this data allows immediate insight into how consumers are engaging with your app. Most importantly, it gives direct insight into your consumers’ engagement over time.

In addition to these standard mobile reports and tools, Analytics Essentials also contains a Digital Publishing menu containing specific reports on Articles, Banners and Sharing.

Analytics Essentials does not provide any reports on video.

Information about Analytics reports

Overview Report

Usage Report

Customizing the Reports

The following reports are available using the Reports & Analytics tool.

Use Article Title or Name to show engagement by article – organized by title or name.

Useful metrics for this report are: Article Impressions, Article Clicks, Article Views, Article Scroll, and Social Share. These metrics show the full life cycle of an article from its display on a browse page (Article Impression), consumer selection (Article Click), viewing and scrolling within the article, and finally sharing the article.

Use Collection Name or Title to show engagement within the browse page of a collection. Useful metrics for this report are Collection and Article Impressions, Collection Open, and Article Click. Both collection and article impression events are generated when more than 50% of their respective card becomes visible on the browse page.

This report will show the number of outbound shares from the device over time. It is useful for measuring how your consumer’s interest in sharing an article with their network.  

Use this report to visualize information on which articles were shared from the device and over which channel. By adding the Social Share Referral metric, you can see which articles and over which channel generated traffic to the social sharing landing page.

Use the Banner Title/Name report to see how often a banner was displayed (Banner Impression) or clicked (Banner Click).  

Only hyperlinks are tracked. Video is tracked via video specific variables.

The Overlay URL report will show which URL generated the most clicks from the device. A convenient breakdown is by Article Title. This shows The URL clicked from within the article it was contained.

All video reporting is done using the reserved video solution variables the SDK provides. The Video Engagement->Overview report is a powerful new visualization tool that aggregates all video playback by starts and completion rates. You can drill down into any of the data points to get specific playback information.

Likewise, the video engagement details report will provide quick tabulated numbers on enagement by video.  

Use these reports to display metrics on where your consumers are based and the type of technology they are using. For instance, you could generate a ranked report by city showing where the most active users are (Daily Unique Visitors), Overall Total Visitors (Unique Visitors), and repeat users (Visits).

Likewise, use the Technology > Operating Systems report to rank the operating systems of your consumers' devices.

This report provides a quick at-a-glance overview of the health of your application. See how many consumers have installed the application (App Install); how many are continuing to engage (App Launches); and, average session length per consumer.

Data is reported from all applications using a combination of Mobile Services SDK intrinsic reporting, context variables and events, and solution specific metrics (such as Video). Most app-specific reporting is provided via context variables and events which are mapped to specific events and evars via processing rules when received at the data center.

For a list of variables and events, see the "Analytics Event Variables" at the end of this document. The information below describes the individual events that are sent along with the context data that is updated with each event.

Web Viewer analytics tracking differs from tracking on mobile devices in a number of ways.

• Web Viewer supports only the “click” navigation gesture. It does not support "swipe" or other gestures.
• Viewer Type attribute of App Startup event is always “distribution-web”.
• All dps.ref.* properties in all events (Referrer type, name, title, and Navigation Gesture) are conditionally available in the Web Viewer. These properties are available when the action that causes the event is a link within the content of a browser, the browser's forward and back buttons, and other navigation buttons such as menu bar clicks and navigation bar buttons. These properties are not available in other cases such as when the link is pasted into the browser or when the link is modified by a user.
  
• All dps.col.* (Collection name, type, title, and layout name) properties exist only if the resource is being viewed within a collection.

Event: AppInstall

Mapping: event1

Schedule: Sent once the first time the application launches.

Variables:

Event: AppStartup

Mapping: event2

Schedule: Sent every time the application is started.

Variables:

Event: AppSentToBackground

Mapping: event3

Schedule: The Application focus is changed away from this application.

Variables: NONE

Platforms: iOS, Android, Windows

Event: CollectionView

Schedule: Sent when the browse page of a collection is viewed

Variables:

Event: CollectionScroll

Mapping: event5

Schedule: Sent when the browse page of a collection is scrolled. Specifically sent upon Scroll stop.

Variables:

Event: CollectionClick

Mapping: event6

Schedule: Sent whenever a card representing a collection is clicked (tapped) within a browse page.

Variables:

Event: Collection Open

Mapping: event7

Schedule: Sent the first time a collection’s browse page has been opened. It is only sent the first time that collection is opened and not when navigating amongst the members (children) of this collection.

Event: Collection Impression

Mapping: event31

Schedule: Sent upon scroll stop whenever the card for a collection becomes visible by more than 50%.

Event: Article View (Editorial)

Mapping: event9

Schedule: Sent whenever an article is displayed.

Variables:

Event: Article View (Advertisement)

Mapping: event9

Schedule: Sent whenever an article that has been marked as an Ad is displayed.

Variables:

Mapping: event10

Schedule: Sent whenever an article's card on a browse page is clicked.

Mapping: event10

Schedule: Sent whenever an article's card on a browse page is clicked. This graph is sent when the article is marked as an advertisement.

Mapping: event11

Schedule: Sent whenever an article’s card on a browse page is viewable.

Mapping: event11

Schedule: Sent whenever an Ad article’s card on a browse page is viewable.

Mapping: event12

Schedule: Sent whenever an article scrolls. Sent upon scroll stop.

Desktop Web Viewer does not support any navigation gesture other than “click”.

Mapping: event23

Schedule: Sent whenever a metered article is previewed in excess of the dwell time. The dwell time is longer on tablets than phones and is reported in this event. The triggers for dwell time are 25 seconds for a tablet and 15 seconds for a phone.

Event: URL Click (Editorial Content)

Mapping: event13

Schedule: Sent whenever a user clicks on a hyperlink, web view or button overlay within an Article (or Advertisement). tags in HTML articles are not currently tracked.

Event: Banner Impression

Mapping: event24

Schedule: Sent whenever a banner card is displayed

Variables:

Event: Banner Click

Mapping: event25

Schedule: Sent whenever a banner card is clicked or tapped.

Variables:

Event: Social Share

Mapping: event26

Schedule: Sent whenever an article is shared from an article view

Variables:

Event: Register Push

Mapping: event27

Schedule: Send when a device registers for push notifications

Variables:

Event: Text Notification

Mapping: event28

Schedule: Send when a device receives a text alert push notification

Variables:

Event: Text Notification

Mapping: event28

Schedule: Send when a device receives a text alert push notification

Variables:

Event: Collection Download Complete

Mapping: event21

Schedule: Sent upon the completion of downloading all articles within a collection. This can only be triggered via Push Notification or an explicit user gesture.

Variables:

Event: Collection Download Start

Mapping: event32

Schedule: Sent when a collection starts to download. Only applies to background downloads or explicit user downloads of a collection.

Variables:

Event: Collection Download Terminated

Mapping: event33

Schedule: Sent upon the user explicitly canceling the download through the cancel dialog.

Platforms: Android, Win, iOS

Variables:

Event: Search Execution

Mapping: event34

Schedule: Sent when the user executes the search. It contains the search term and the collection that the search was executed on.

Platforms: Android, iOS

Variables:

Event: Search Results View

Mapping: event35

Schedule: Sent when the Search Results are displayed to the user. It will be displayed when the results are empty and when the user is going back to a previous search..

Platforms: Android, iOS

Variables: