Adobe Mobile Services User Guide

•

Frequently Asked Questions - Mobile Services

•

Release Notes & Solution Help

•

What's New in Adobe Mobile Services

•

Release Notes - All Solutions

•

Marketing Cloud Help Home

Developer

•

Download Mobile SDKs and Tools

•

Analytics Developer

Core Services

•

Marketing Cloud Product Documentation

•

Dynamic tag management

Community Resources

•

Marketing Cloud Forum

•

Adobe Marketing Cloud Community

•

Idea Exchange

•

Adobe Training and Tutorials

•

Featured Solutions Center

Developer SDK Documentation

In addition to the user's guide, you can download the Software Development Kits (SDKs), which includes a customized package that includes a pre-populated version of the configuration file that you need to configure your app in Adobe Mobile.

Native libraries are provided for the following platforms:

•

Android SDK 4.x for Marketing Cloud Solutions

•

iOS SDK 4.x for Marketing Cloud Solutions

•

Unity Plug-in for iOS and Android 4.x SDK

•

Windows Visual Studio Extensions for Marketing Cloud Solutions 4.x SDK

•

Xamarin Components for Marketing Cloud Solutions 4.x SDK

•

Universal Windows Platform SDK 4.x for Marketing Cloud Solutions

•

Windows 8.1 Universal App Store

•

BlackBerry 10 SDK 4.x for Marketing Cloud Solutions

Getting Started with Adobe Mobile Webinar

Watch the Getting Started with Adobe Mobile webinar. (

Play

)

Adobe Mobile Services 7

What's New in Adobe Mobile Services

New release information for Adobe Mobile Services.

This section contains the following information:

•

Current Release Notes

•

Marketing Cloud Release Notes, Documentation Updates, and Historical Release Notes

Current Release Notes

The Mobile Services March 9, 2017 release includes the following changes:

Fixes

• Minor bug fixes.

Marketing Cloud Release Notes, Documentation Updates, and Historical Release Notes

In addition to the notes for each release, the following resources provide additional information:

Resource Description

Marketing Cloud Release Notes

View the latest release notes for the Adobe Marketing Cloud solutions.

Documentation Updates

View detailed information about updates to this guide that might not be included in these release notes.

View information about new features and enhancements in previous releases of Adobe Mobile.

Historical Release Notes

Developer SDK Documentation

View the latest release notes and info for our Software Development Kits (SDKs).

Getting Started

Information to help you get up and running with Adobe Mobile Services, including signing in and adding a new app.

Mobile app marketing is quickly maturing, and Adobe Mobile Services helps you take your app marketing to the next level with an app-centric user interface, seamless workflows between Adobe Marketing Cloud solutions, and one SDK. As you invest in your mobile applications, app analytics, A/B testing, push messaging, and optimization should be at the forefront of your strategy and development.

Roles and Permissions

In Adobe Analytics, you can manage roles on the Admin Tools Home page.

Overview

The following roles manage permissions in the Mobile Services UI:

Analytics Admin

An Analytics Admin manages user groups and assigns permissions, one of which is the Mobile App Admin. The Marketing

Cloud Admin links your Adobe ID to your Adobe Analytics and Adobe Target accounts, which allows you to log in to the Mobile

Services UI by using your Adobe ID and access Adobe Target. For more information about the Marketing Cloud Administrator, see

Administration - User Management and FAQ

Tip: An existing Analytics Admin has the ability to assign the Analytics Admin role to any user.

For more information about this role, see the following content:

•

Users

•

Frequently Asked Questions - Analytics Permission Changes

Mobile App Admin

This role is the Admin for the Mobile Services UI.

Important: For some features, such as push messaging, the Analytics Admin must select the Segment Creation check box in User Management.

Managing Access

Here is some additional information about accessing options in the Mobile Services UI:

Apps and Report Suites

All Mobile Service apps are tied to report suites. If users do not have access to a report suite, they will not have access to that report suite's associated app.

Mobile Services and Analytics Features

If your company does not have an Analytics contract to access a feature in the UI, such as Push Messaging, no user in your company will have access to that feature, regardless of permission level.

Adobe Target

Getting Started 10

Adobe Target provides everything you need to tailor and personalize your customers' experience to maximize revenue on your web and mobile sites, apps, social media, and other digital channels. If the Marketing Cloud Administrator linked your Adobe

ID to your Target account, Target appears as an option under Manage Apps in the Mobile Services UI. For more information about Target, see

Introduction to Target

The following permissions are available in Adobe Target for all users:

• Create/Update/Activate/Deactivate/Delete Target Activity

• Create/Update/Delete Target Audience

• Create/Update/Delete Target Offer

Roles and Permissions

Here are the roles in the Mobile Services UI, with their relevant permissions:

Analytics Admin

• All User & Mobile App Admin Permissions

• Create App with new report suite

• Delete App from Mobile Services

Important: Although the app has been deleted in the Mobile Services UI, the report suite still exists in Analytics.

• Manage App Settings

• Enable Lifecycle Reporting

• Enable Location Reporting

Mobile App Admin

• All User Permissions

• Create App with existing report suite

• Manage App Settings

• Configure App's Mobile SDK options

• Configure App's UI settings

• Configure linked App Store apps

• Configure App's Universal Link options

• Configure Push Services certs and API keys

• Create/Update/Activate/Deactivate/Duplicate/Archive/Delete Postbacks

• Create/Update/Archive/Delete Link Destinations

• Create/Update/Archive Marketing Links

• Create/Import/Update/Delete Legacy Acquisition Links

• Create/Import/Update/Delete Places (Points of Interest) configuration

• Create/Update/Send/Schedule/Cancel/Duplicate/Archive/Delete Push Messages

• Create/Update/Activate/Deactivate/Duplicate/Archive/Delete In-App Messages

Getting Started

For more information about groups and users, see:

•

Groups

•

Add a user to a group

Mobile Services User

This role has view-only permissions and can provide feedback in the Mobile Services UI.

• Provide Feedback on Mobile Services UI

• View Apps

Important: Users can only see the report suites for which they have access in Adobe Analytics.

• View App Settings

• Download App SDK configuration

• View all UI and SDK settings

• View Variables & Metrics configuration

• View Postbacks

• View Link Destinations

• View & Run Reports

• View Marketing Links

• View & Export Legacy Acquisition Links

• View & Export Places (Points of Interest) configuration

• View Push Messages

• View In-App Messages

Signing In

You can sign in to Adobe Mobile Services by using your web browser.

This section contains the following information:

•

Sign In to Adobe Mobile Services

•

Sign Out of Adobe Mobile Services

•

Reset Your Password

Sign In to Adobe Mobile Services

To sign into Adobe Mobile Services:

1. In a browser, enter

https://mobilemarketing.adobe.com

2. Sign in to the Mobile UI by using one of the following methods:

• Marketing Cloud

Getting Started 12

Important: Use your Adobe ID to sign into the Mobile Services UI.

This method assumes the following conditions have been met:

• Your company has been

provisioned

in the Adobe Marketing Cloud.

• You have

linked your Analytics account

Tip: If you are unsure, use your Adobe Analytics account.

In the Adobe Marketing Cloud method, your teams can access projects, collaborate, visualize, and socialize across solutions.

• Adobe Analytics

This legacy method provides your Analytics company, username, and password.

Sign Out of Adobe Mobile Services

To sign out of Adobe Mobile Services, click the icon in the top right-hand side of the page and click Sign Out.

Reset Your Password

Tip: Depending on how you signed in to the Adobe Mobile Services, the process to reset your password might vary.

Reset your password in one of the following ways:

• Adobe Marketing Cloud

If you use your Adobe ID:

1. Click Sign in with Adobe ID and click the Forgot password? link.

2. Enter the email account that is associated with your Adobe ID and click Send.

3. Follow the instructions to reset your password in the email you receive.

• Adobe Analytics

If you use your company, username, and password:

1. Click the Forgot password? link.

2. Enter your company name, your username, and click Continue.

3. Follow the instructions in the email you receive.

Mobile Services Features

Descriptions of the features provided by the Mobile service.

Feature Description

Responsive web user interface and improved visualizations

Adobe Mobile provides a new user interface that is designed around Mobile app measurement and optimization.

Getting Started 13

Feature Description

Mobile AppMeasurement SDKs The Marketing Cloud 4.x SDKs make implementations simpler, faster, and easier. These

SDKs provide Adobe Analytics, Adobe Target, and audience management support in your iOS or Android Mobile apps.

Here are some features in the 4.x SDKs:

• Geo-fencing and points-of-interest (POI)

• Lifetime value

• Timed events

• Opt-in/Opt-out management

• Performance enhancements

• Seamless workflow of lifecycle, POI, and lifetime value data between Analytics and Target

• Simplified implementation and many other improvements and enhancements

Streamlined SDK configuration Create your mobile report suite in Adobe Mobile. You can download a completely configured

SDK that is ready to send data and that requires no additional configuration.

Point of Interest and

Geo-location

Define points of interest by latitude and longitude with a defined radius for measurement and targeting. This feature provides better segmentation by location and provides precise location-based marketing for your mobile apps.

In-app messaging

App acquisition analytics

In-app messages are delivered to users in real-time, based on their actions and traits.

The following types of messages are supported:

• Custom

• Themed

• Full-screen

• Native alerts

• Local notifications

Messages are triggered from the Analytics data that is already being tracked by the SDK.

Create app store links that allow you to download applications from the Apple App Store and Google Play. The links that you create can attribute your success events to the downloads.

Integrated workflows between

Adobe Analytics and Adobe

Target

Create mobile optimization campaigns by selecting a dimension value from one of the app reports.

Target audiences based on mobile unique dimensions and app lifecycle data

Define audiences by using mobile-specific dimensions such as device type, operating system, or geo-location. Users can also select app lifecycle metrics, such as Upgrade, and dimensions to define a target audience for app experiences.

Experience testing (A/B) for apps

Create and edit A/B testing campaigns to quantify the effectiveness of multiple app experiences.

Getting Started 14

Feature Description

Google Play conversion tracking

Measure campaign information for Google Play app downloads. You can report campaign source, term, and other Google Play metrics in Adobe Mobile.

Lifetime Value Identify key activities that increase the value of an app user and measure and target based on value.

Timed Events Measure and report the total time that users take to complete key events, such as in-app time and total time.

App store and in-app combined report

Display imported app store data such as revenue, downloads, and rankings in the same reports as launches, upgrades, and user retention.

Add New App: Getting Started

One of the first tasks you need to complete is to create a new app and configure its key metrics.

Tip: These instructions provide a quick introduction to adding an app. For more detailed instructions, including information about configuring the SDK for Analytics, Target, Audience Manager, Acquisition, and Visitor ID Services, see

Add New

App .

After you create the app, the correct configuration is generated and is given to the developers who are implementing the Mobile

SDK for the app.

1. After

signing in

to Adobe Mobile Services the first time, complete one of the following tasks:

• Click Create New.

• Click Manage Apps, click Add.

Remember the following information:

• To modify an app, click Manage Apps, select the app, and click the right arrow icon at the end of the row.

• To delete an app, click Manage Apps, select the app and click Delete Selected.

2. Enter information in the following fields:

Setting Description

Report Suite

Select the report suite where reporting data will be collected and stored in Adobe Analytics.

Each app is connected to one Analytics report suite. If you are sending app data to multiple reports suites, add an app for each report suite.

If you have Analytics administrator privileges in Adobe Mobile, you can create a new report suite from Adobe Mobile.

Complete the following steps:

1. In Report Suite, select New Report Suite.

Getting Started 15

Setting

Icon

Name

Type

Description

2. Enter a Report Suite ID.

This ID is used to uniquely identify the report suite in Adobe Analytics. Your company prefix is automatically added to the beginning of the ID.

3. In Copy Settings From, select a template.

The variables, events, processing rules, and other settings are set up in the new report suite identical to how they are in this report suite.

A report suite created in Mobile Services is offline-enabled (or time stamped) only if the Copy

Settings From report suite that was used was the Mobile App Template or if you create a report suite that is offline enabled.

4. Select a time zone.

All reporting dates are in your current time zone. This setting attempts to use a time zone that is close to what your browser uses.

5. Select a currency.

Revenue is tracked and reported as the currency that you selected.

For more information about roles and permissions, see

Roles and Permissions

To browse to and select an optional icon for your app, click the A icon .

Enter a descriptive name for your app.

If you have many saved apps, a descriptive name helps you quickly locate the app. The name can also help you understand the app's purpose and settings.

Select an app type. The available reports that display in the left navigation menu vary depending on the type of app you select.

Tip: For most apps, leave default Standard option.

Here are the other app types:

• DPS is used only if your app was built using Adobe Digital Publishing Suite.

• Game is similar to Standard option, except that Game updates the terminology that is used in the reports to terms for games. For example, users is changed to players. Game-specific reports are automatically shown for game apps.

Enter an optional description for the app.

Description

3. Click Save.

4. In Key Metrics, select your most important app metrics.

For more information, see

Understanding Mobile Metrics

Key metrics are displayed on the landing page for a quick view of app performance:

Getting Started

5. (Optional) Download the App SDKs.

Important: You need to download the latest SDKs only when you are ready to upgrade to the 4.x SDKs, or if you are working on a new app.

To download the latest SDKs:

1. Configure the SDK Analytics Options.

2. Download the necessary SDKs and tools.

3. After the set up is complete, send the configuration file to your developers so that data can be collected.

Understanding Report Types

When customizing reports, the broad flexibility might create some questions as to the type of report that is best suited to get the data that you need.

Prerequisites: Before you can customize reports, you must understand the difference between a metric and a dimension.

Item

Metric

Description

A metric is used to measure your data.

Getting Started 17

Item

Dimension

Description

Metrics are values that can be counted and added together and are used to see how often specific actions occur in your app. Common metrics include installs, launches, revenue, lifetime value, and logins. For example, each time your app is launched, launches is increased by one.

A dimension is used to describe your data.

Dimensions are represented using a string, or a number that acts like a string (such as a postal code), and is used to organize and segment your data. Examples of common dimensions include OS version, campaign name, product name, and mobile carrier. Each dimension has a number of specific values that are associated with that dimension. For example, the OS version dimension has values such as "iOS 7" and "Android

4.1.2".

Here is the list of available reports:

•

Over-Time Report

•

Trended Report

•

Filtered Over-Time Reports

•

•

•

•

Over-Time Report

Over-time reports show how metrics are performing over a time range so you can quickly identify spikes and trends. Analysis often starts in an over-time report and moves into trended and ranked reports as you drill down to investigate the factors that might be contributing to a metric spike or trend.

For example, if you see a spike in launches, you might run a trended report that shows launches for the top 5 operating systems to see which operating systems are contributing most to the spike in launches:

Getting Started 18

To view dimension values with other metrics on an over-time report, you can use the instances metric and define a dimension filter.

Trended Report

Trended reports help you see how your most popular dimensions are performing against a metric. You can use this report to determine which values are contributing most to a change in a metric.

To view a trended report for a dimension, add a sticky filter (for example, Operating System = iOS 6.0.1) to an over-time report to view the same data. As a bonus, you can add five additional metrics to the filtered over-time report.

Getting Started

Filtered Over-Time Reports

If you have a specific dimension value that you want to view, you can add a sticky filter to an over-time report. The following report shows 30 days' worth of launches, upgrades, and crashes for a specific operating system version.

Ranked Reports

Ranked reports show you how often the top 50 dimension contribute to a metric. This report is useful to view total contribution for a date range across a large number of values.

Getting Started 20

Sunburst Report

Sunburst reports provide, for example, the base report along with breakdowns. The visualization uses height to show the metric and the performance differences between the metrics. Each concentric circle represents an audience segment in the category for that circle. You can take actions on an audience, such as applying a Sticky Filter, hiding a metric, and viewing metrics.

You can view the report an in-product tutorial that describes how to interact with a sunburst chart.

To start the tutorial:

1. in Manage App Settings, click Usage.

2. Click Technology > Technology Breakdown.

3. In the title bar of the report, click Customize, and click the information icon .

Pathing Report

A Pathing report is based on path analysis and displays a pathing chart that represents paths that are taken from one state in the app to another state.

Getting Started 21

Each node is shaped like a box and represents a state in the users' paths though an app. For example, in the illustration above, the top node represents the number of users that launched the app and selected a photo from the gallery.

Funnel Report

Funnel reports allow you to identify where customers abandon a marketing campaign or divert from a defined conversion path while interacting with your mobile app. You can also use the Funnel report to compare the actions of different segments.

The funnel visualization lets you see where customers fall out of the process. Gaining visibility into customer decisions at each step helps you understand where customers are being deterred, what path they tend to follow, and when they leave your app.

Getting Started 22

Understanding Mobile Metrics

You can measure different metrics by using Adobe Mobile and collect the metrics that you want to track for your app.

•

App Launches, Upgrades, Crashes

•

Usage and Retention

•

Revenue

•

App Events

•

App States

•

Location and Points of Interest

•

Lifetime Value

•

Time to Complete

•

Devices

App Launches, Upgrades, Crashes

These metrics provide a view into the general health and usage of your app. You can track the number of launches, number of users on each version of your app, crashes, and so on. These metrics, along with overall revenue (if you provide a paid app), are usually the starting point for mobile app measurement.

Getting Started 23

Usage and Retention

Usage metrics help you understand average session length, daily and monthly engaged users, upgrades, and other insights that let you know how and how often your app is being used. Retention reports quickly shows user retention levels the day after initial launch, 7 days, and 28 days.

On Android devices, you can use Google Play referrer tracking to measure how users are getting to the app store before they download your app.

Getting Started 24

Revenue

You can view revenue collected by app stores, and revenue measured directly using in-app purchase events. Other cart metrics are available by .

App Events

App events are the Key Performance Indicators (KPIs) that you define to measure the success of your app. Depending on the type of app you provide, KPIs will vary from articles read and levels completed to lifetime revenue.

App States

States are the different views that are provided by your app. States are viewed in a pathing report, so a good way to define states is to think about the paths through your app that you want to measure. For example, where do users most often navigate from the initial view?

Getting Started 25

Location and Points of Interest

If GeoReporting is enabled on your Analytics report suite, several location-based reports are available. On Wi-Fi, GeoReporting accuracy is similar to that of a desktop web browsers. On a data connection, accuracy varies based on the provider and how requests are routed.

For increased accuracy, you can also add location and point of interest tracking to your app. These options allow you to report detailed latitude and longitude location data and use geo-fencing to determine when a user is in a radius of a pre-defined point of interest.

Lifetime Value

Lifetime value allows you to measure a value that persists as long as a user has your app installed. You can assign different in-app actions, positive or negative values, or increment lifetime value with the amount of each purchase.

Time to Complete

With the KPIs you measure, you can use time to complete to measure time in session and the total time (cross-session) it takes for an action to be completed. For example, you might measure how much time elapses between installation and the initial in-app purchase.

Getting Started 26

Devices

Device reports allows you see the different device types, operating systems, and mobile carriers where your app is being used.

This information is useful to plan support for the next version or to segment reports and target content.

Mobile Metrics and Dimensions Reference

Reference information for the default mobile metrics and dimensions.

The following sections contain more information:

•

Metrics

•

Dimensions

Tip: The dimension and metric permissions that are set in Adobe Analytics apply to Mobile Services. If you attempt to run a report without proper permissions, you will receive an error.

Metrics

Event

First Launches

Upgrades

Daily Engaged Users

Configuration

Triggered on the first run after an installation or a re-installation.

Triggered on the first run after an upgrade or when the version number changes.

Triggered when the application is used on a particular day.

Tip: 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.

Getting Started

Event

Monthly Engaged Users

Launches

Crashes

Previous Session Length

Dimensions

Dimension

Install Date

App ID

Launch Number

Days Since First Use

Days Since Last Use

Configuration

Triggered when the application is used during a month.

Tip: 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.

Triggered 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 Manage App Settings. For more information, see the Session Timeout (Seconds) row in

Configure SDK Analytics Options

Important: 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 .

Triggered when the application does not correctly exit. This event is sent when the application starts after a crash.

Tip: The application is considered to crash if quit is not called.

Aggregated total Previous Session Length.

Description

Date of the first launch after the installation. The date is in the

MM/DD/YYYY

format.

Stores the Application name and version in the following format:

[AppName] [BundleVersion]

For example, myapp 1.1

Number of times the application was launched or brought out of the background.

Number of days since the first run.

Number of days since the last use.

Getting Started

Dimension

Hour of Day

Day of Week

Operating System

Operating System Version

Days Since Last Upgrade

Launches Since Last Upgrade

Device Name

Carrier Name

Resolution

Description

Measures 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.

Number of the week day the app was launched.

Operating system of the device.

Operating system version.

Number of days since the application version number has changed.

Number of launches since the application version number has changed.

Stores the device name.

iOS: Comma-separated, two-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. For a complete list of common device names, see

iOS Device Versions

Stores the name of the mobile service provider.

Width and height in actual pixels.

Overview 29

Overview

You can display the key performance metrics of the apps that you most recently viewed. By default, you can view up to 12 apps.

You can change the date range and create filters to segment the data and edit any app on the Overview page.

Here is how the apps are displayed on the Overview page:

The metrics that display for each app reflect the key metrics that you selected when you created the app. For more information, see

Add New App: Getting Started

If the app you want to view is not displayed, search for it by entering the app's name or by clicking the drop-down list in All

Apps .

In Overview, you can perform the following tasks:

•

Change Date Range

•

Filter Data

•

Drill Down to View Key Performance Indicators

•

Edit an App's Settings

Overview 30

Change Date Range

The previous 30 days of data displays for key metrics. You can change this by clicking the calendar icon in the top right-hand side. You can select a date range or a pre-determined time frame from the drop-down list.

Filter Data

You can user filters to segment the data for each app.

For example you can filter the data by App Version and by Device Type.

To create a filter:

1. Click the Filter icon to display the Sticky Filter dialog box.

2. Click Add Rule, select an option from the drop-down list, and enter any necessary information.

For example, you might select App Version and enter 4.5 for the version. You could select Device Type and enter Android.

Tip: You can create complex filters by using AND and OR statements.

3. Click Update.

Tip: A blue bubble displays next to the Filter icon to indicate the number of active filters.

To cancel filters, click the Filter icon, and click Cancel.

Drill Down to View Key Performance Indicators

Click the name of the app to display details about the key performance indicators:

Overview

The key performance indicators page might look similar to the following example:

Overview

The lines on the chart are color coded, and you can mouse over the data point to display the statistics for specific dates.

To drill down, click the > icon next to Key Performance Indicators.

The lines on the chart are color coded, and you can mouse over any data point to see statistics for specific dates. Click a column header in the table to sort the data in ascending or descending order.

Edit an App's Settings

1. Click the gear icon in any app's tile to open the App Information page.

2. Edit the app's settings.

For more information about each setting, see

Configure Options on the App Information Page

3. Click Save.

Manage Apps 33

Manage Apps

You can create, manage, and delete apps in the Manage Appspage.

Add New App

You can use this information to create a new app and configure its key metrics; configure the SDK options for Analytics, Target, and Audience Management; configure acquisition and Visitor ID Service options; and download the configuration file, SDKs, and developer and tester tools.

These instructions will help you add a new app and configure Adobe Analytics, Adobe Target, and Adobe Audience Manager

integrations. For brief, step-by-step instructions, see

Add New App: Getting Started

Before you can configure your app, you must add it in the Adobe Mobile Services user interface. After you create the app, the correct configuration is generated, and you can provide this configuration to the developers who are implementing the Mobile

SDK for the app.

Sign in

to Adobe Mobile Services and complete one of the following tasks:

• Click Create New to create an app.

• To add additional apps, click Manage Apps in the left navigation menu, then click Add.

Tip: To manage existing apps, click Manage Apps in the left navigation menu and click the app that you want to modify.

You can make changes on the App Information page.

2. Enter information in the following fields:

Setting Description

Report Suite

Specify the report suite in which reporting data will be collected and stored in Adobe Analytics.

Each app is connected to one Analytics report suite. If you are sending app data to multiple reports suites, add a new app for each report suite.

If you have been given Analytics administrator privileges in Adobe Mobile, you can create a new report suite in Adobe Mobile.

To create a new report suite, select New Report Suite enter information into the following fields:

• Report Suite ID: This ID is used to uniquely identify the report suite in Adobe Analytics. Your company prefix is automatically added to the beginning of the ID.

• Copy Settings From: The variables, events, processing rules, and other settings are set up in the new report suite exactly like they are in this report suite. A report suite created in Mobile Services is offline-enabled (or time stamped) only if the Copy Settings From report suite used was the

Mobile App Template, or if you create a report suite that is offline enabled.

• Timezone: All reporting dates are in this time zone. This setting attempts to use a time zone close to what your browser uses.

• Currency: Revenue is both tracked and reported as this type of currency.

Icon

(Optional) To browse to and select an icon for your app, click the A icon.

Manage Apps

Setting

Name

Type

Description

(Optional) Enter a descriptive name for the app.

A descriptive name helps you quickly locate an app. A meaningful name can help you quickly understand the app's purpose and settings.

Select a type from the drop-down list. The available reports that display in the left navigation menu vary depending on the type of app you select.

Here are the available types:

• Standard

You can leave the Standard option selected for most apps.

• Publication:

You can select this option if your app was built using Adobe Digital Publishing Suite.

• Game

This option is similar to the Standard option, except that Game updates the terminology used in the reports to terms for games. For example, users is changed to players. Game-specific reports are automatically shown for game apps.

Description

(Optional) Enter a description for the app.

3. Click Save to add the new app.

After the app has been added, you can check the App Information page about configuring additional options. For more information, see

Configure Options on the App Information Page

Add App from Apple App Store or Google Play

You can add an app from the Apple App Store or from Google Play.

1. Complete one of the following tasks:

•

Sign in

to Adobe Mobile Services and click Create New.

• To add additional apps, click Manage Apps in the left navigation menu and click Add.

2. Click Add App Store App.

3. Enter information in the following fields:

Setting Description

App Store

Select an app store:

• Apple App Store

• Google Play

Search by Name

Search for the app store by name and select the app. Preview information about the selected app helps you determine whether you selected the correct app.

Manage Apps

Setting

App ID

4. Click Add.

Description

Enter the App ID.

Delete Apps

You can delete an app from Adobe Mobile.

1. Click Manage Apps.

2. Select the check box next to app(s) that you want to delete.

Important: Deleting an app from Adobe Mobile removes the app from the Adobe Mobile UI, but the app is not removed from the Apple App Store or Google Play. The report suite and data will still be available in Adobe Analytics, but you cannot manage it in Adobe Mobile.

3. Click Delete Selected.

4. Click Delete to confirm the deletion.

Manage App Settings

Managing your apps involves configuring an App and managing a variety of variables and metrics.

Important: To edit this page, you must be a member of the Mobile App Admin group. To determine whether you are a member of this group, click Admin Tools > User Management > Groups > Mobile App Admin.

To configure and manage your app see the following information:

Configuring your App

On the Manage App Settings page, you can make the following types of changes:

• App Information

This section includes information about the app, including the name of the app, the type of app, key metrics, and lifecycle and location reports.

• Lifecycle Reports

Tip: If you created the report suite in Adobe Analytics, you must enable lifecycle reports. If you created the report suite in Adobe Mobile, this option is enabled by default.

This report allows you to measure the following metrics:

• Acquisition

Track referring URLs for app-download campaigns. For more information, see

Prerequisite: Before you download the SDKs and tools, you must Configure the SDK Analytics Options .

• Lifecycle

Track the metrics and dimensions that can be measured automatically by the mobile library after lifecycle is implemented.

For more information, see the following sections:

•

iOS SDK Lifecycle Metrics

•

Android Lifecycle Metrics

•

Windows Lifecycle Metrics

•

BlackBerry Lifecycle Metrics

• App Actions

Enable reports and pathing based on in-app actions.

• Lifetime Value

Understand how users accrue value over time by using app KPIs, such as purchases, ad views, video completes, social shares, photo uploads, and more.

• Timed Events

Measure the amount of time that elapses (in-app and total time) between key app actions, such as time before first purchase.

• Location Reports

Manage App Settings 37

This option lets you enable reports to track latitude and longitude and identify specific Points of Interest (POIs). You can also track bluetooth beacons (UUID, major, minor, and proximity).

• App SDKs and Developer Tester Tools

When you are ready to upgrade to the 4.x SDKs, or if you are working on a new app, download the latest SDKs and development tools from the bottom of the Manage App Settings page.

After set up is complete, you can send the configuration file to your developers so that data can be collected properly. If you are not ready to download SDKs and tools now, click Manage App Settings and click the app to display the App Information page at any time.

For more information about configuring the options, see the following content:

Configure SDK Analytics Options

You can configure the SDK Analytics options on the Manage App Settings page while creating a new app or editing an existing app.

Enter information in the following fields under SDK Analytics Options:

Setting Description

Use HTTPS

Enable HTTPS for added security.

Backdate Session Hits

Enable/disable the ability for the Adobe SDK to backdate session info hits. Session info hits currently consist of crashes and session length.

When enabled, the Adobe SDK will backdate the session info hit to 1 second after the last hit of the previous session. This means that crashes and session data will correlate with the correct date in which they happened. One hit will be backdated on every new launch of the application.

When disabled, the Adobe SDK will attach the session info to the current lifecycle.

Privacy

Select a privacy option:

• Send Data Until Opt-Out

• Hold Data Until Opt-In

Session Timeout

(Seconds)

Batch Limit

Specify the session timeout value. The default is 300 seconds.

Specifies the length of time, in seconds, that must elapse between app launches before the launch is considered a new session. This timeout also applies when your application is sent to the background and reactivated. The time that your app spends in the background is not included in the session length.

Specify how many hits you want to queue before sending data. Set to 0 to send hits immediately.

The batch limit represents the threshold for number of hits to be sent in consecutive calls. For example, if this option is set to 10, each hit prior to the 10th hit will be stored in the queue. When the 10th hit comes in, all 10 hits are sent consecutively.

Manage App Settings

Setting

More Details

Description

Click the More Details link to view the report suite ID and tracking server, enable or disable offline tracking, and view the character encoding model being used (such as UTF-8).

When offline tracking is enabled, data generated by the device while offline is timestamped and sent later. If this option is disabled, offline data is discarded.

Download Mobile SDKs and Tools

Information to help you download Mobile Services SDKs and tools to help you with your Mobile Services implementation.

Settings > About [App Name].

App SDK Downloads

You can download an

ADBMobileConfig.json

file that is customized with the app settings you have selected. For example, the configuration file is pre-populated with your report suite ID, tracking server, and the HTTPS, default privacy setting, and session timeout you selected on this screen.

If you download the mobile SDK, the customized

ADBMobileConfig.json

file is included automatically.

Native Libraries

Configure your app in Adobe Mobile services so you can download a customized package that includes a pre-populated version of the configuration file.

iOS instructions

Android instructions

Native libraries are provided for iOS, Android, Windows Phone 8, Blackberry, Symbian, and others:

•

Unity Plug-in for iOS and Android 4.x SDK

•

Windows Visual Studio Extensions for Marketing Cloud Solutions 4.x SDK

•

Xamarin Components for Marketing Cloud Solutions 4.x SDK

•

iOS SDK 4.x for Marketing Cloud Solutions

•

Android SDK 4.x for Marketing Cloud Solutions

•

Universal Windows Platform SDK 4.x for Marketing Cloud Solutions

•

Windows 8.1 Universal App Store

•

BlackBerry 10 SDK 4.x for Marketing Cloud Solutions

Configure SDK Target Options

You can configure the SDK Target Options on the Manage App Settings page while creating a new app or editing an existing app.

While

adding a new app

or editing an existing app, enter information in the fields under SDK Target Options:

Setting Description

Client Code

Specify the Target identifier for your app. If you are not using Adobe Target leave this field blank.

Request Timeout

(Seconds)

Specify the request timeout value. The default is 5 seconds.

If the response from Target does not return to the browser in 5 seconds, the visitor times out, default content is shown, and a cookie is set to exclude that visitor for 30 minutes.

Manage App Settings

Setting Description

Tip: The response from Target can be modified.

Configure Audience Manager Options

You can configure the SDK Audience Manager options on the Manage App Settings page while creating a new app or editing an existing app.

While

adding a new app

or editing an existing app, enter information in the fields under SDK Audience Manager Options:

Setting Description

Subdomain Enter the subdomain of the Audience Manager server that your app uses. For example, you can enter client.demdex.net

If you are not using Adobe Audience Manager, leave this field blank.

Configure SDK Acquisition Options

You can configure the SDK Acquisition options on the Manage App Settings page while creating a new app or editing an existing app.

Enter information in the following fields under SDK Acquisition Options:

Setting Description

Enable

Create app store links that allow you to download applications directly from the Apple App Store and Google Play. The links you create help you attribute your success events to the downloads.

Create or Edit Marketing Links

Referrer Timeout

(Seconds)

More Details

Specify the referrer timeout value. The default is 5 seconds.

This value specifies the number of seconds to wait for acquisition information before sending the

First Launch hit.

Click the More Details link to view the app's Tracking ID.

Universal Links and App Links

Starting in iOS 9.2, deep linking is no longer supported. You must use Universal Links (iOS) and App Links (Android) for deep linking into your app or website.

Manage App Settings 40

Universal Links and App Links

A Universal Link is a link that can be handled by an iOS application or the browser. This experience is known as deeplinking.

However,

starting in iOS 9.2, deeplinking is no longer supported

. For more information about Universal Links, see the

Apple documentation on Universal Links

An App Link is the Android version of the Universal Link. Although deeplinking might currently still work on all Android operating systems, Adobe Mobile Services supports App Links because a marketing link should be consistent across all platforms.

For more information about App Links, see the

Android documentation on App Links

Setting up site-association documents in Adobe Mobile Services

1. In the Mobile Services home page, select the app for which you want to set up Universal Links or App Links.

2. Click Manage App Settings.

3. Ensure the iOS or Android app that handles UL/AL is added to the Add App Store Apps section.

Tip: If this section does not display, click the Add App Store App link.

4. Scroll to Universal Links and App Links Options at the bottom of the App Information page.

5. Complete one of the following tasks:

• For iOS, select an iOS app and enter the App ID.

• For Android, select an Android app and enter a SHA-256 certificate fingerprint.

6. Click Save.

You must provide at least the iOS App ID or one Android App selection and SHA-256 certificate or you will receive an error.

Important: You can update the documents by clicking Update from the Universal Links and App Links Options section.

However, when you click Update, a warning notifies you that all Universal Links / App Links you have created in the past will be affected.

Create a Universal / App Link

For more information, see

1. Select the app from the Mobile Services home page, expand Acquisition, and click Marketing Link Builder.

2. Click Create New.

3. Under Marketing Link Options, select Use Universal Links or App Links.

If you configured the site-association documents from the steps above, this option is selected by default. If not, Use Universal

Links or App Links is disabled and Use Interstitials is selected by default.

If Use Universal Links or App Links is selected, an additional field titled Custom Path is displayed. This allows users to define the URL path after the domain with any query parameter. For example, if you enter my/universal/link?os=9.2

, your full marketing link URL becomes https://[marketing link domain]/my/universal/link?[AMS default query parameters]&os=9.2

4. Click the Decisions tab.

5. Configure your decision tree.

Manage App Settings 41

If the iOS or Android app is installed, the app will handle the deeplink with its logic, and the final destination serves only as the fallback case. (The app is not installed.) Therefore, it can only be a web link or store link.

6. Click Save.

Tip: Once a marketing link is saved, the Marketing Links Options cannot be altered. This is because you do not want to change the behavior of the marketing links that may have already been distributed.

Configure SDK Visitor ID Service Options

You can configure the Visitor ID Service options on the Manage App Settings page while creating a new app or editing an existing app.

Enter information in the following fields under Visitor ID Services Options:

Setting Description

Enable

Enable this option to use the Adobe Visitor ID Service.

For more information, see the

Marketing Cloud Visitor ID Service Users Guide

Organization

Select your organization from the drop-down list.

A Marketing Cloud organization is the entity that enables an administrator to configure groups and users, and to control single sign-on in the Marketing Cloud. The organization functions like a log-in company that spans all the Marketing Cloud products and solutions. Typically, the organization is your company's name, but a company might have many organizations.

For more information, see

Accounts and Organizations

in the

Marketing Cloud Visitor ID Service

Users Guide

Configure Postbacks

Postbacks let you send data collected by Adobe Mobile to a separate third-party server. By leveraging the same triggers and traits that you use to display an in-app message, you can configure Mobile Services to send customized data to a third-party destination.

Restriction: To use postbacks, you must install the 4.6 SDK or later. For more information, see Android - Postbacks or iOS

- Postbacks .

1. Click the name of the desired app to go to its Manage App Settings page and click the Manage Postbacks link at the top right side.

2. Click Create Postback.

3. Enter the following information in the fields:

Option Description

Postback Type

Choose Custom.

Templates will be available in the future.

Manage App Settings 42

Option

Name

URL

Context Variable

Add Post Body

Timeout (in seconds)

Trigger(s)

Trait(s)

Description

Specify a descriptive name for the postback.

Specify a valid endpoint URL (along with appropriate query parameters as needed for GET requests).

You obtain this URL from the party you are sending the data to (ad server or your own endpoint).

For example: http://my.server.com/?user=bob&zip=90210&c16=4.6.0-iOS&c27=cln,132

Highlight portions of the URL and select the desired context variable from the drop-down list.

You can also simply insert context variables into the URL.

The URL will replace all template variables with values from the hit.

Specify any additional post body content, for example on a post request.

Content Type: If you specify post body text, specify the content type for the post body.

For example: application/json

Specify the time (in seconds) to wait for the postback.

Specify one or more data tags and conditions that trigger the postback. For example, you could choose Crashed as the trigger and Exists as the condition to trigger the postback when the app crashes.

You can also specify which metrics activate the postback. For example, you can select

Device Name as the trigger, Equals, and iPhone 6 Plus as conditions to activate the postback when the app crashes on iPhone 6 Plus devices.

Specify who can see the message when it is triggered. Options include Session Length,

First Launch Date, and App ID.

4. Click Save to create the postback and add it to the Manage Postbacks list.

To activate the postback in the future, do one of the following:

• Select the checkbox next to the postback in the Manage Postbacks list and click Activate Selected.

• Click Save & Activate to save your changes and immediately activate the postback.

Manage App Settings 43

Configure Push Messaging

You can use this information to help you configure the Push Services options on the Manage App Settings page while creating a new app or editing an existing app.

Before you configure push messaging, review the following information:

• You must perform several prerequisite tasks. For more information about these tasks, see

For more information about obtaining the SSL certificate and private key, see

• Report Suite Considerations

You can configure one app store app for Apple and one for Google in each report suite. If you need additional apps, for example, one for a production environment and one for a dev environment, set up a new app store app and a new report suite for each environment.

1. Enter information in the following fields under Push Services:

Setting Description

Apple Private Key

Browse to and select your valid private key (

.p12

.key

, or

.pen

Important: If the file you select for the Private Key input also contains a certificate, you do not need to specify the certificate.

Certificate

Specify a valid certificate. This option is required only when the Private Key input does not contain a certificate.

Configure App to use

APNS or GCM

Google API Key

Specify a valid API key.

For more information about obtaining the API key, see

Configure App to use APNS or GCM

For more information, see the following topics:

• Android:

Push Messaging

in the Android SDK 4.x for Marketing Cloud Solutions guide.

• iOS:

Push Messaging

in the iOS SDK 4.x for Marketing Cloud Solutions guide.

2. Click Save.

Prerequisites to Enable Push Messaging

You must complete these tasks before configuring Push Messaging in applications.

Manage App Settings 44

Task Instructions

Enable the Marketing

Cloud for Your

Company.

Your Adobe Analytics Company must be Marketing Cloud enabled. You can verify this with your

Adobe account executive.

Install and Configure the

Mobile SDK.

1. Install the Mobile SDK

The Push Messaging feature requires that you download and install the appropriate 4.6 (or later)

Mobile SDK.

For more information, see the following content:

•

Android SDK 4.x for Marketing Cloud Solutions

•

iOS SDK 4.x for Marketing Cloud Solutions

2. Configure Push Services

You must configure push services in the Mobile SDK.

For more information, see the following content:

•

Android: Push Messaging

•

iOS: Push Messaging

Core Service using your

Adobe ID.

Important: To use the Push Services functionality users must log in to the Mobile Core Service by using their Adobe ID and their Analytics account must be linked to their Adobe IDs. Push

Services functionality is not available if users log in using their existing Adobe Analytics accounts.

If users do not have Adobe IDs, complete the following steps:

1. Marketing Cloud Administrator invites users to the Marketing Cloud.

For more information, see

Access the Marketing Cloud

2. Users create a personal Adobe ID using the instructions received from the Marketing Cloud administrator.

An email message is automatically sent to each user after the administrator completes the previous step.

3. Users log in to Mobile using their Adobe ID.

For more information, see

Sign in to the Adobe Marketing Cloud

Link Users' Accounts in the Marketing Cloud.

Each user must link the Analytics solution account from the Marketing Cloud organization.

1. To sign in to the Marketing Cloud with an Adobe ID, enter

https://marketing.adobe.com

in a browser.

2. In the upper right corner, select the Analytics company name.

3. Click Add Organization and select Adobe SiteCatalyst/Adobe Social from the drop-down list.

4. Enter company name, your legacy credentials for the specified company, and click Link Account.

Manage App Settings 45

Task Instructions

The Adobe ID is now linked to your Analytics account, company, and log-in credentials.

For more information, see

Troubleshooting Account Linking

Configure Push Services and the SDK Visitor ID

Service in the Mobile

User Interface

Before you enable the Visitor ID Service for your app, the Push Services section is disabled. But,

after you

enable the Visitor ID Service

, the Push Services section is enabled.

Remember: You must click Save to save your changes and refresh the Push Services.

Important: You can configure one app store app for Apple and one for Google in each report suite. If you need additional apps, for example, one for a production environment and one for a dev environment, set up a new app store app and a new report suite for each environment.

• For Apple, drag and drop your private key and/or certificate. If your private key is password-encrypted, enter its password.

• For the Private Key, drag and drop your private-key file into the box. You can also click Browse to select the file.

This file contains the private key. The certificate might also be included in this file (

.p12

, pkcs12

.pfx

.key

.pem

• For the Private Key Password, if your private-key file is encrypted, enter the password.

(Conditional) For the Certificate, drag and drop your certificate file into the box. You can also click Browse to select the file.

This field is not required if the private-key file also contains the certificate (

.cert

.cer

.crt

.pem

• For Google, specify the API key for the app.

Click Test to validate that the app and Mobile Services are configured correctly. This option is useful for debugging and troubleshooting.

Enter the device's push tokens that you want to send the message. You can send the message to multiple devices by specifying tokens in a comma-separated list.

Manage App Settings

Task Instructions

Configure App to use APNS or GCM

You can configure your app to use Apple Push Notification Service (APNS) or Google Cloud Messaging (GCM).

This section contains the following platform-specific information:

•

Android Apps

•

iOS Apps

Android Apps

If GCM is not enabled in your app

To configure your Android app to use GCM, if GCM is not enabled in your app:

1. Go to

https://developers.google.com/mobile/add

and log in with your

Google Dev credentials

2. Click Pick a Platform and select Android App.

3. Select the app and the app package name.

4. Complete the process to enable Google services for your Android app.

5. Click Choose and Configure Services.

6. Add Cloud Messaging by clicking the + button on its icon.

7. Click Generate Configuration Files.

8. Copy the Server API key and Sender ID for later use.

For example:

- API Key = AIzaSyC6FNgsCOpBL5eXhDvwf8979mWba6x7Roo

- Sender ID = 835015092250

Manage App Settings

If GCM is enabled in your app

To configure your Android app to use GCM (Google Cloud Messaging) when GCM is enabled in your app:

1. Go to

https://console.developers.google.com/project

2. Select your app that is GCM enabled.

3. Note the Project number in the Overview section. This is the GCM Sender ID for the app.

For example:

- Project Number = 835015092250

4. Under the APIs & Auth header, select Credentials.

5. Copy the API Key under the Public API access section for use later.

For example:

- API Key = AIzaSyC6FNgsCOpBL5eXhDvwf8979mWba6x7Roo

iOS Apps

To configure your iOS app to use APNS:

1. Go to

https://developer.apple.com/account

and log in to your

Apple Developer account

2. Under iOS Apps, select Identifiers.

3. If you already have an App ID set up for push, skip to Step 11.

4. Press the + button to create a new App ID.

5. Enter an App ID Description.

6. Enter an App ID Suffix.

Important: To support push, you must use an Explicit App ID that does not use a wild card (for example,

com.tester.pushSample

7. Under App Services, select the Push Notifications check box.

8. Click Continue.

9. Click Submit.

10. Click Done.

11. Select your App ID that is set up to use push messaging from the list and click Edit.

12. If you already have a Push Certificate created, skip to Step 15.

13. Scroll down to Push Notifications and click the correct Create Certificate... button (depending on if you're creating a certificate for Development or Production).

14. Follow the steps outlined on the Apple website to create your CSR, upload it, and generate your certificate.

15. Scroll down to the Push Notifications section and download the SSL certificate you just created.

16. Double-click the certificate you downloaded to add it to your keychain.

SSL Certificate and Private Key

To get your SSL Certificate and Private Key (APNS)

Manage App Settings

1. Open Keychain Access.

2. Click My Certificates and find the appropriate Push iOS Push Services Certificate for your app and environment.

You can identify the correct certificate by matching the bundle ID and whether it is Development or Production.

3. Expand the certificate and verify that it contains a private key.

4. Right-click the private key and select Export "<name of key>.

5. Go through the dialog and save your new

.p12

file.

You do not have to enter a password.

6. In the Private Key, enter the

.p12

file.

Managing your App

You can track and manage the data that you receive from the app by configuring a variety of variables and metrics.

Manage Variables and Metrics

• Standard Variables & Metrics

Each app includes variables and metrics for tracking shopping cart and purchase activities. Some purchase information cannot be handled with processing rules, so the SDK exposes the special "&&products" context data. For example, you can have variables such as cart additions, cart removals, check outs, orders, and so on. The context data has to be mapped to data in

Adobe Analytics. If this variable is populated with a simple mapping from context data, this is the key that maps to it. Leave blank if the variable is populated by more complex rules in Analytics Admin Tools.

For more information about these variables and metrics, see the following:

• Android:

Product Variables

• iOS:

Product Variables

• Custom Variables

The Custom Variables page displays all of the custom Analytics variables that are configured for the report suite that contains your app data. On this page you can enable additional variables and map context data to Analytics variables.

This section contains the following information:

•

Map Context Data to Analytics Variables

•

Additional Analytics Variables

Mapping Context Data to Analytics Variables

Click Manage App Settings > Manage Variables & Metrics > Custom Variables.

These mappings will call the same API that is used in

processing rules

Manage App Settings 49

Here is a list of the custom variables that you can configure:

• The Custom Properties (or props) answer the question "which one?" Props can be set to a text value that will be associated with other variables and metrics sent in the same hit. The values can be used to filter reports or can be listed in rank order by an associated metric.

When a value is set for a property in a tracking call (or hit), it applies only to that call.

• The Custom Variables (or evars) also answer the question "which one?" However, an evar value can apply not only to the hit it is sent in, but also to variables and metrics sent in subsequent hits until the value expires or a new value is set.

• The Custom List Variables(or Multi-Value Variables) behave the same as variables except they allow you to capture multiple values on one hit. For more information, see

List Variables in the Adobe Analytics Implementation Guide

These mappings display in Analytics as being created in Mobile Services.

Element Description

Name

The friendly name of the data collection variable.

Manage App Settings 50

Element

Context Data

Description

If this variable is populated with a simple mapping from context data, this is the key that maps to it. Leave this field blank if the variable is populated by more complex rules in Analytics Admin

Tools.

Click in the context data column and select the context data variable that you would like mapped.

The drop-down list contains variables received in the past 30 days, so if the context data you want to map is not in the list you can type it.

Persistence

(Custom Variables and

Custom List Variables)

Persistence determines the point at which a Custom Variable (eVar) value will expire or will no longer be associated with additional hits. If an eVar has expired when a hit fires, the None value will be associated with that hit for that eVar. This means that no eVar value was active when the hit fired.

You can select one of the following options:

• Session

The eVar value will persist for the length of the Analytics visit.

• Tracking Call

The eVar value will persist only for the tracking call or hit it in which it was included.

• Never Expire

The eVar value will persist for all subsequent tracking calls.

• Advanced

Adobe Analytics has a more advanced UI for setting persistence for eVars. If a persistence value is set for the eVar that is not supported in Mobile Services, this value is shown in the Mobile

Services UI.

To manage eVars, click Adobe Analytics Report Suite Manager > Conversion Variables UI.

List Support

(Custom Properties)

Enables passing multiple values to be associated with the property in a single tracking call. The delimiter must be a single character and cannot be a zero or a space.

Delimiter

(Custom List Variables)

The delimiter must be a single character and cannot be a zero or a space.

Additional Analytics Variables

You can enable additional variables using the drop-down list at the bottom of each variable section.

Manage App Settings 51

Select an unused variable number and enter a name. You can optionally provide the context data variable that you would like stored and any additional information.

• Custom Metrics

Metrics (or events) answer the questions "how much?" or "how many?" Events can increment each time the user takes an action or hold numeric values such as a price. Custom metrics include events such as an app was created, the PDF or CSV file was downloaded or exported, a campaign was saved, the SDK was downloaded, a report was run, a link to the App Store was added, an in-app message was activated, and so on.

You can select one of the following types of custom metric types:

• Whole number

• Decimal number

• Currency

Manage Points of Interest

Points of Interest allow you to define geographical locations that you can use for correlation purposes, target with in-app messages, and so on. When a hit is sent in a point of interest, the point of interest is attached to the hit. For more information

about points of interest, see

Manage Points of Interest

Manage Link Destinations

You can create, edit, archive/unarchive, and delete link destinations. These destinations can then be called inline when building

marketing links, push notifications, or in-app messages. For more information about link destinations, see

Manage Link

Destinations

Manage App Settings 52

Manage Postbacks

Postbacks let you send data collected by Adobe Mobile to a separate third-party server. Leveraging the same triggers and traits you use to display an in-app message, you can configure Mobile to send customized data to a third-party destination. For more information about postbacks, see

Configure Postbacks

Usage 53

Usage

Usage reports display average session length, daily and monthly engaged users, upgrades, and other insights that help you understand how and how often your app is being used. Retention reports quickly shows user retention levels 1 day, 7 days, and

28 days after the initial launch.

Overview

The Overview report provides a snapshot of your key metrics.

Here is an example of this report:

Usage 54

You can change the date range for the report by clicking the calendar icon on the top right side. You can also create a

sticky filter

that spans different reports to see how a segment is performing across all mobile reports.

Tip: You configure the key metrics for this report while creating the app. For more information, see Configure Options on the App Information Page .

Users and Sessions

The Users and Sessions report displays metrics for unique visitors during the selected time frame.

You can configure the following options for this report:

Option Description

Time Period

Click the Calendar icon to select a custom period or to select a preset time period from the drop-down list.

Customize

Customize your reports by changing the Show By options, adding metrics and filters, and adding additional series (metrics), and more

Filter

Click Filter to create a filter that spans different reports to see how a segment is performing across all mobile reports. A sticky filter allows you to define a filter that is applied to all non-pathing reports.

Usage

Option

Download

Description

When you open the Funnel report, you must create a custom funnel. For more information, see

Click PDF or CSV to download or open documents and share with users who do not have access to Mobile Services or to use it in presentations.

Retention

The Retention report (formerly known as First Launch Cohorts) is a cohort report that displays how many unique users launched your app for the first time and then launched the app again at least once in the subsequent months.

By default, this report shows the retention of groups of users based on when the users first launched the app. You can also customize this report to use a metric other than First Launch and add additional actions.

A cohort is a group of people who share a common characteristic or experience in a defined period. The Retention report takes the common characteristic of users who installed the app on a specific day, week, or month and charts how many of those users launched the app over the next X days, weeks, or months. The report displays how well the visitors were retained as active or engaged.

Here is an example of this report:

In the MO column, the total number of people who launched the app for the first time in November 2014 is displayed. In the

M1 column, the number of people who launched the app again in December 2014, and so on, is displayed.

To change the date range or to edit the report's rules, click Edit.

Usage 56

The report can be populated by any variable or metric, such as Lifecycle metrics but not calculated metrics.

Funnel

The Funnel report identifies where customers abandoned a marketing campaign or diverted from a defined conversion path while interacting with your mobile app. You can also use the Funnel report to compare the actions of different segments.

Gaining visibility into customer decisions at each step helps you understand where they are being deterred, what path they tend to follow, and when customers leave your app.

Tip: To save your custom funnel, save the URL after you configure its settings and run the report. You can share the URL or save it in a document.

Here is an example of this report:

To demonstrate a simple funnel, here are the settings for a configuration that uses three funnel steps and two funnel comparisons.

We assume that a demo app allows users add an item, such as photo, and then share it:

Usage 57

The first step indicates that the user launched the app. The second step indicates that the user added a photo from a gallery in the app. The third step indicates that the user shared one or more photos from the app on social media, text message, email, and so forth. The funnel comparisons allows you to compare the levels of adding and sharing photos between users of the iOS app and the Android app.

To generate the report, click Run.

Here is an example of a generated report:

Usage 58

The first series shows that 100 percent of users launched the app. The second series shows that a higher percentage of Android users added a photo from the gallery. The third series shows that almost half of iOS users shared the photo, but none of the

Android users shared the photo. This might indicate a problem with the app that needs to be investigated.

To display additional information, mouse over any bar in the chart:

Usage 59

You can configure the following options for this report:

Option Description

Time Period

Click the Calendar icon to select a custom period or to select a preset time period from the drop-down list.

Customize

Filter

Download

Customize your reports by changing the Show By option, adding metrics and filters, and adding additional series (metrics), and more

Click Filter to create a filter that spans different reports to see how a particular segment is performing across all mobile reports. A sticky filter allows you to define a filter that is applied to all non-pathing reports.

actions (events, such as clicks, selections, resizing, and so on) that users perform in your app. You can use a funnel report

Click PDF or CSV to download or open documents and share with users who do not have access to Mobile Services or to use it in presentations.

Usage 60

View Paths

The View Paths report, which is based on path analysis, displays a pathing chart that represents the paths that were taken between states in the app.

Tip: The View Paths and View Action reports are similar because both are pathing reports. The View Paths report allows you to see how users navigate in your app from one screen to the next. The View Actions report displays the sequence of

to combine navigation and actions in one report.

Usage 61

Each node, shaped like a box, represents a state in the users' paths though an app. For example, in the illustration above, the top node represents the number of users that launched the app and navigated to the main view.

When you click a node to provide the additional options to modify the chart, additional options such as Focus or Expand appear.

For example, when you click the MainView state in the top node, the Focus and Expand icons appear.

Usage 62

To expand the view, click the + icon to display the additional paths that come in to or going from the node. In the illustration below, state 1 is launching the app, state 2 is viewing the main page of the app, and state 3 includes the following paths that users took: Expanding a state is similar to a funnel.

• Navigating to the camera roll

• navigating to the item selector

• navigating to the camera

• navigating to the item info page

Usage 63

Click to isolate the node and to show the paths that are coming into and going out of the selected node. In the illustration below, the following paths preceded users who were viewing the main view of the app:

• item info

• item selector

Usage

• Camera roll

• Camera

You can focus or expand multiple nodes for a detailed view of the paths that users take in your app. For example:

Usage 65

You can configure the following options for this report:

Usage

Option

Time Period

Customize

Filter

Download

Description

Click the Calendar icon to select a custom period or to select a preset time period from the drop-down list.

Customize your reports by changing the Show By options, adding metrics and filters, and adding additional series (metrics), and more

For more information, see

For more information, see

funnel report to combine navigation and actions in one report.

Click PDF or CSV to download or open documents and share with users who do not have access to

Mobile Services or to use it in presentations.

Action Paths

The Action Paths report is based on path analysis and displays a pathing chart that represents the paths that are taken from one state to another state in the app.

Both the View Paths and Action Paths reports are pathing reports. The View Paths report shows you how users navigate in your app from one screen to the next. The View Actions report shows you the sequence of actions and events, such as clicks, selections, resizing, and so on, that users perform in your app.

Tip: You can use a

Usage 67

Each node, shaped like a box, represents a state in the users' paths though an app. For example, in the graphic above, the top node represents the number of users who launched the app and then picked a photo from the gallery.

To display the options to modify the chart, click a node and click Focus or Expand. For example, if you click the PhotoPicked state in the top node, the Focus and Expand icons display.

Usage 68

To expand, click the + icon. This option displays the additional paths that come into, or go out of, the node. In the graphic below, state 1 is launching the app, state 2 is picking a photo (the item you previously expanded), and state 3 includes the different paths users took:

• Selecting an item

• Adding an item

• Dragging an item

• Scaling an item

Expanding a state is similar to a funnel.

Usage 69

To isolate the node and show paths that come into, and go out of the selected node, click the icon. In the graphic below, the following paths were completed before users selected a photo:

• Rotating an item

• Scaling an item

• Dragging an item

Usage

• Removing an item

Of the users who selected a photo, the following paths were completed after the photo was selected:

• Selecting an item

• Adding an item

• Dragging an item

• Scaling an item

Usage 71

You can focus or expand multiple nodes to get a detailed view of paths users take in your app. For example:

Usage 72

You can configure the following options for this report:

Usage

Option

Time Period

Customize

Filter

Download

Description

Click the Calendar icon to select a custom period or to select a preset time period from the drop-down list.

Customize your reports by changing the Show By options, adding metrics and filters, and adding additional series (metrics), and more

For more information, see

For more information, see

Add Breakdowns and Metrics

Click PDF or CSV to download or open documents and share with users who do not have access to Mobile Services or to use it in presentations.

Versions

The Versions report is an over-time report that displays information about the different versions of your app that are running on a users' device.

Here is an example of this report:

Usage 74

Technology

The Technology report allows you to see the different device types, operating systems, operating system versions, and mobile carriers on which your app is being used.

This report provides a sunburst visualization for your existing data, and you can use the report to discover audience segments

(collections of visitors) for targeting. Creating and managing audiences is similar to creating and using segments, except that you can make the audiences available in the Marketing Cloud.

This section contains the following information:

•

Navigation and Usage

•

•

•

Create Sticky Filter

•

Share Reports

Usage 75

Navigation and Usage

This visualization provides, for example, the base report and breakdowns, uses height to show the metric in focus, and the performance differences between the metrics. Each ring represents an audience segment in the ring's category. You can take actions on an audience, such as applying a sticky filter, hiding a metric, and viewing metrics.

Tip: In addition to this information, you can view an in-product tutorial that describes how to interact with the sunburst chart. To start the tutorial, click Technology Breakdown in the title bar of the report, click Customize, and click the i icon.

Usage 76

This sunburst chart is interactive, so you can change the time period by clicking the Calendar icon. You can mouse over the any part of the chart to display more information. In the following example, you can see the total number and the percentage of users who use your app on an iPhone 6.

Usage

Use the Categories buttons in the upper right corner to toggle between viewing information about Device Type and Device.

In the following example, users are broken down by Device Type:

In the following example, users are broken down by Device:

Usage 78

Click a slice in the ring to select the audience on which you can perform actions, such as zooming in, hiding audiences, creating a Target activity, in-app message or a sticky filter.

Click a secondary metric on the right side to add it to the visualization. You can show the secondary metric using color, height, or both.

Usage

The following table describes the standard reports and how they are populated in Mobile Services:

Report

Device

Operating Systems

Operating System Version

Carriers

Population Method

Lifecycle metrics.

Automatic.

Lifecycle metrics.

Automatic.

Description

Common metrics broken down by device type.

Common metrics broken down by operating system.

Common metrics broken down by operating system version.

Common metrics broken down by carriers.

Tip: Wi-Fi users are reported as

(none)

on this report.

Add Breakdowns and Metrics

You can add breakdowns and secondary metrics, which change the height of each audience relative to the other audiences in the chart.

Important: The more rings you add to the sunburst, the longer it takes to process.

To add breakdowns and secondary metrics, click Technology Breakdown in the title bar of the report and click Customize.

Usage 80

When you click Add Breakdown or Add Metric, a new item displays with the same name as the previous item in the list. Click the newly created breakdown or metric to access a drop-down list from which you can select a new item.

Create a Target Activity

Click a slice in the ring to select the audience for which you want to create a Target activity and click Target. The Target activity is pre-populated with the report data. For more information about creating a Target activity, see

Create Sticky Filter

Click a slice in the ring to select the audience for which you want to create a sticky filter and click Sticky Filter. This filter allows you apply the current filters and run a new report based on the filters.

Share Reports

After you create a report, your settings are used to create a custom URL that you can copy and share.

Crashes

The Crashes report provides a snapshot of your app's crashes. You can see the number of crashes and the crash rate and log in to the Apteligent user interface.

Important: To display the Crash report in the left navigation, you must first integrate your app with Apteligent.

Usage 81

The Average Crash Rate graph displays the crash rate by date. You can hover over any date to view the crash rate for that day.

The Crash History chart displays information about each app crash, including the crash ID, crash type, number or crashes, and the crash date. To log in to Apteligent to view more details about a crash, click the link in the Crash ID column.

You can configure the following options for this report:

Option Description

Time Period

Click the Calendar icon to select a custom period or to select a preset time period from the drop-down list.

Filter

For more information, see

Acquisition 82

Acquisition

Marketers can create tracking links to promote and drive traffic to their apps. These tracking links can drive users to app stores, app deep links, and interstitials, which can be correlated to in-app behavior. A marketer can create one link to route users to iOS, Android, or other platforms as appropriate.

You can create, edit, manage, and view reports on trackable mobile app marketing links.

Tip: This functionality requires the Adobe Analytics - Mobile Apps or the Adobe Analytics Premium SKU.

The following Acquisition reports provide insight into how your marketing links are performing:

•

•

Link Report

Overview

This report displays the top campaigns that drove users to your app with information about how the campaigns performed across other tracking metadata such as acquisition source, medium, term, and content.

Acquisition 83

Link Report

This report provides a ranked view into your marketing links performance. In addition to seeing your link names with key performance metrics, this report is also customizable. For more information, see

The latest marketing link tracking functionality requires SDK version 4.9 or later. For more information, see

Remember the following information:

• You can click the arrow icons in the column headers to sort the data in ascending or descending order.

• To export the data to a PDF document, you can click Download.

Acquisition 84

Getting Started with Acquisition

You can use this information to use acquisition in Mobile Services, including information about configuring acquisition tracking, prerequisites, and creating destinations.

Acquisition Prerequisites

Complete the following prerequisites before you can use acquisition links.

To track marketing links, ensure that you meet the following prerequisites:

1. Mobile App Report Suite

You must create a new mobile app report suite or have an existing report suite that can collect, track, and report on data that is collected from your marketing links. For more information on creating a new mobile app report suite, see

Add New App

2. SDK Version

What's New in

Adobe Mobile Services

SDK Version

4.1 to 4.5

4.6 to 4.9

4.9 or later

Supported Functionality

Legacy Acquisition Builder

Yes

Manual Links Building

Yes

Marketing Links Builder

Yes

Acquisition 85

3. Enable SDK Acquisition Options

Tracking must be enabled in the SDK configuration before links can be tracked and reported on. For more information, see

Configure Acquisition

4. Add App Store Apps

You must add the app from the Apple App Store or from Google Play. For more information, see

Add App from Apple App

Store or Google Play

Configure Acquisition

Acquisition tracking must be enabled in the SDK configuration before you can track and report on marketing links.

1. On the Manage App Settings page for the app, scroll to the SDK Acquisition Options section.

2. Complete the following tasks:

Field Description

Enable

To enable acquisition, select the check box.

When you select this check box, the Referrer Timeout value changes from 0 to 5 seconds.

Referrer Timeout (seconds)

(Optional) This field is optional if you have already enabled the Enable check box.

You can change the timeout value, which is specified in seconds. This setting specifies the time to wait for acquisition information before sending the First Launch hit. We recommend that you use the five-second default value.

Important: This value must be a non-zero value. If you enable acquisition but leave the value s zero, the acquisition links will not function.

3. Download and use the new SDK configuration file in your app.

You have successfully configured Acquisition on iOS.

4. To enable Acquisition on Android, complete the steps in the How to Track section in

Mobile App Acquisition

Destinations

Marketers can create, save, and edit link destinations, such as web, deep, or other links, that can be used while building trackable marketing links.

For instructions about creating different types of link destinations, see

Create and Manage Link Destinations

You can create the following types of link destinations:

Type Description

App Deep Link App deep link destinations are URI schema deep links that direct users to a deep link in your app.

For example, you can direct users to a specific product line in an online retailer's mobile app.

Web Link Web link destinations direct users to a specific URL. For example, you can direct users to a specific product line on an online retailer's website.

Acquisition 86

Type

Hybrid Link

Description

Hybrid links support iOS Universal Links or Android App Links.

For more information about how to create each type of link, see

Create New Link Destination

Create and Manage Link Destinations

In the Manage Link Destinations page, you can create, edit, archive/unarchive, and delete link destinations. These destinations can be called inline when building marketing links, push notifications, or in-app messages.

To display the Manage Link Destinations page:

1. From the left navigation menu, click Manage Apps.

2. Click the name of the app to display its App Information page.

3. In the top right side, click Manage Link Destinations.

The Link Destinations page displays all of your existing link destinations and provides options to create, archive, unarchive, edit, and delete link destinations.

For example:

Create New Link Destination

You can create a new link destination that directs users to a web or a deep link in your app.

1. In the Mobile Services UI, click Manage Apps.

2. Click the name of the app to display its App Information page.

3. Click Manage Link Destinations.

4. Click Create New.

5. Enter information in the following fields:

Field Description

Title

Enter a descriptive name for your app link destination.

The title displays only on the Manage Link Destinations page in the Adobe Mobile Services

UI.

A descriptive name helps you or others in your organization quickly find a specific link destination and can provide insight into its purpose.

Acquisition

Field

Link Type

App

Link type

Description

Select the desired link type:

• App Deep Link

Provide a URI schema deep link (for example, yourapp://section

App deep link destinations are URI schema deep links that direct users to a deep link in your app. For example, you can direct users to a specific product line in an online retailer's mobile app.

• Web Link

Enter a web HTTP or HTTPS URL (example http://adobe.com

Web link destinations direct users to a URL. For example, you can direct users to a product line on an online retailer's website.

• Hybrid Link

Enter an iOS Universal Link or an Android App Link (for example, https://yourwebsite.com

). Hybrid links support iOS Universal Links or Android

App Links.

Select the app that is associated with the link you are going to provide.

Tip: This information is required only if you selected an App Deep Link or a Hybrid Link in Link Type.

If the app does not appear in the selection list, click Add New App to reference a new app from an app store.

Enter the actual URL for the deep, web, or hybrid link.

Tip: The label of this field varies depending on the type of link you selected.

Notes

Enter optional notes for your destination.

Additional notes display only on the Manage Link Destinations page in the Adobe Mobile

Services UI.

Additional notes can help you or others in your organization quickly find a specific link destination and can provide insight into its purpose, the campaign to which it is tied, or anything else that you feel is important.

6. Click Save.

Manage Link Destinations

You can use the Link Destinations page to edit, archive, unarchive, or delete existing destination.

Acquisition

To display the Manage Link Destinations page:

1. In the Mobile Services UI, click Manage Apps.

2. Click the name of the app to display its App Information page.

3. Click Manage Link Destinations.

4. (Conditional) Complete the appropriate tasks:

• Edit

To edit an existing link destination, click its name in the list, and edit the relevant fields. For more information, see

Create

New Link Destination

• Archive

You can archive existing link destinations that you want to retain for future use but want to remove from theLink

Destinations list.

To archive existing link destinations, select one or more check boxes next to the desired items and click Archive Selected.

Because your link destination is archived and can be unarchived at any time, you do not need to confirm your action.

• Unarchive

You can unarchive previously archived link destinations that you want to display again in the Link Destinations list.

To unarchive a link destination, click View Archive, select one or more check boxes next to the desired items, click Unarchive

Selected. The View Archive option only displays if you previously archived link destinations.

• Delete

To delete a link destination, select one or more check boxes next to the desired items, click Delete Selected and click Delete to confirm your action.

Important: Deleting a link destination is a permanent action. If you are unsure whether you want to delete a link destination, use the archive option.

Marketing Links Builder

The builder helps you build marketing links that can route users to app stores and app or web link destinations. Marketers can choose destinations based on rules, such as device type or operating system of the user’s device.

The marketing links can be tracked and reported on, allowing marketers to attribute downloads, app relaunches, and other in-app events to these links.

Acquisition 89

Create or Edit Marketing Links

You can create or edit marketing links to provide deep linking into your mobile app or your website.

For more information about universal links and app links, see

1. In your app, in the left navigation pane, expand Acquisition and click Marketing Link Builder.

2. Complete one of the following tasks:

• To create a new marketing link, click Create New.

• To edit a link, click the link's name in the Title column.

3. Enter information in the following fields:

• Marketing Link Name:

(Required) Specify a descriptive name for your marketing link. The name displays only on the Marketing Links page in the Adobe Mobile Services UI. A descriptive name helps you or others in your organization quickly find a specific link and can provide insight into its purpose.

• Unique Tracking Code:

(Required) Specify the desired tracking code or click to create a new tracking code. You can view reports that detail use of the tracking code.

• Add Tracking Context Data:

(Optional) Click the + icon and enter the relevant information to track your campaign using context data. In the Custom

Context Data drop-down list, select a preset tag or one of your own tags. Context data is used for reporting when the marketing link is deployed.

The following preset tags are available:

Tag Option Description

Custom Context Data

Specify the key and value.

If you add custom context data, you must create a processing rule. For more information, see

Processing Rules

in Analytics Help.

Source

Medium

Specify the original referrer, such as "newsletter" or "homepage."

Specify the marketing medium, such as "banner" or "email."

Content

Term

Specify the name or ID of the ad with the link.

Specify paid terms or other search terms for the ad.

4. Click Save.

5. Enter information in the following fields:

• (Required) In Fallback URL, Specify the URL that users are directed to when a destination cannot be matched (for example, if the user is on a desktop or another platform that does not match a destination rule).

Acquisition 90

• In Marketing Link Options, select Interstitials or Universal and App Links.

For more information, see

any query parameter. For more information, see

• (Conditional) If Universal or App Links is selected, in Custom Path, users can define the URL path after the domain with

6. Click Edit Deep Link Interstitial and configure the link.

(Optional) When there are multiple destinations, users can be routed depending on whether they have a mobile app installed.

If the app is installed, an interstitial landing page is displayed.

For more information, see

7. Click Save and click Next.

8. In the Destination page, configure the link.

Click the Decision icon ( ) and select one of the following decision locations:

• Add Decision

• Add Path b) If you selected Add Decision, select one of the following decision types:

• Operating Decision

Supported operating systems include iOS, Android, AMX, and so on.

• Device Type

Device types include devices such as desktops, eReaders, game consoles, mobile phones, set top boxes, and so on.

c) Click the Destination icon ( ) and select one of the following destination types:

• App Store

• Web Link

• App Deep Link

• Hybrid Link

Tip: When you use the Web Link destination type with a link to the app store, acquisition is not tracked. To track acquisitions, use the App Store destination type.

Create New Link Destination

9. To save the marketing link, click > Save.

Interstitials

You can route users to a destination depending on whether they have the app installed (an app deep link) or not installed (to a website or an app store).

The choice of routing is best left to users. Marketers can provide user choices by configuring an interstitial page that shows users the available landing destinations.

To configure an interstitial when

creating a new marketing link

Acquisition

1. Click Edit Deep Link Interstitial.

2. Enter information in the following fields:

Field Description

Custom HTML

Select your custom interstitial HTML page. Custom interstitials is the ability for marketers to customize interstitial landing pages with custom HTML/CSS/JS, which allows you to brand your pages.

Here are the requirements for the HTML page:

• Must be an HTML file.

• Must contain the

%%DEST%%

and

%%FALLBACK%%

placeholders.

• The uploaded HTML will be served in an

You must ensure that your link targets are pointing to a parent window. You may include

<head>

or specify a target property for each

<a/> individually.

Tip: If you upload custom HTML, the other four options in this table will not be used unless you remove the uploaded file.

Image URL

Body Text

Specify the URL to an image asset.

Specify the body text for the interstitial.

Acquisition 92

Field

Confirm Text

Fallback Text

Description

Specify the text for the text button.

Specify the fallback text to display.

This field updates the text button if a deep link fails. Users are directed to try the deep link before allowing them to fall back to another option.

For example, a fallback could be to an app store to download and install the app or take users to the company's website. The fallback text lets users know that there is another option available if the deep link fails.

3. (Optional) Click the icons above the image to see how the interstitial looks rotated and on different devices.

You can change or edit the image outside Mobile Services to ensure that the image displays properly in different situations.

4. Click Save.

Use Legacy Acquisition Links

This information helps you use the legacy acquisition link functionality.

Tip: This feature requires SDK version 4.1 or later with acquisition enabled. For more information, see

Configure Acquisition .

You must also specify who has Mobile App Admin rights, because these rights enables access to acquisition links and in-app messages. For more information, see Mobile App Administrator .

The Legacy Acquisition builder lets you create app store links that allow users to download applications directly from the Apple

App Store and Google Play. The links you create enable you to attribute your success events to the downloads.

Create an Acquisition Link

You can create app store links that let you download applications directly from the Apple App Store and Google Play. The links you create let you attribute your success events to the downloads.

1. Click Acquisition > Manage Acquisition Links > Create New.

2. Enter the following information in the Link Information section:

Field Description

Name (Required) Specify a descriptive name for the app link.

Tracking Code

Source

Medium

Content

Term

Specify the desired tracking code or click Generate to create a new tracking code.

(Required) Specify the original referrer, such as "newsletter" or "homepage."

Specify the marketing medium, such as "banner" or "email."

Specify the name or ID of the ad with the link.

Specify paid terms or other search terms for the ad.

Acquisition 93

Important: The values in the above fields cannot be changed after the acquisition link is created.

3. Enter information in the fields in the Add App Store Link section.

Field Description

App Store Select the desired app store:

• Apple App Store

• Google Play

The options for each app store vary, as described below.

Browser Region (Apple App

Store only)

Specify a specific regional app store for desktop browsers. This setting lets you define the region-specific app store that you want an acquisition link to direct to when a user clicks the link from a desktop browser.

Mobile devices auto-redirect based on device settings.

Browser Language (Google

Play only)

Select a language from the drop-down list. This setting lets you define a specific language to display in the Google Play Store for desktop browsers.

Mobile devices show language based on device settings.

Search by Name For the Apple App Store, if you do not already know the App ID, you can search for the app by its name. You can limit your search by selecting an optional region from the In Region drop-down list.

For Google Play, if you do not already know the Package Name, you can search for the app name by its name.

App ID (Apple App Store only)

If you searched for the app, this field is completed automatically. You can enter the App ID value directly, rather than searching for the app.

Package Name (Google Play only)

If you searched for the app, this field is completed automatically. You can enter the Package

Name Namevalue directly, rather than searching for the app.

4. To save your configuration and to generate the link, click Add > Save.

The newly created link displays in the App Store Links section.

Acquisition 94

Click to copy the tracked link to you clipboard.

You can now paste the link into your social media posts, ads, email messages, and so forth.

Manage Acquisition Links

After acquisition links are created, these links can be deleted, imported, or exported.

Delete Acquisition Links

You can delete one or more acquisition links when they are no longer needed.

1. Click Acquisition > Manage Acquisition Links.

2. Complete one of the following tasks:

• Select the check box next to one or more acquisition links.

• Select the check box in the header to select all of your acquisition links.

3. Click Delete Selected and confirm the deletion.

Tip: The Delete Selection option does not display until you select one or more acquisition links.

Import or Export Acquisition Links

Import or export acquisition links if you would rather work with the links using a .csv file instead of using the Adobe Mobile

Services user interface.

1. Click Acquisition > Manage Acquisition Links.

2. Click Import and complete one of the following tasks:

• Browse to and select the desired file to upload into Mobile Services.

• Click Export and open or save the file.

Manage Marketing Links

You can use the Marketing Links page to create, use, and archive marketing links.

Prerequisite: To create and use marketing links, you must first create link destinations. For more information, see

Create or Edit Marketing Links .

Acquisition 95

On the Marketing Links page, you can complete the following tasks:

• Display marketing links

To display the list of marketing links, in the Mobile Services home page, click Acquisition > Marketing Links Builder.

The Clicks column displays the number of users who have clicked on the marketing link. The First Launches column displays the number of first launches for the app. This value reflects the number of users who chose to install the app and launch it after clicking on the marketing link.

• Archive or Unarchive marketing links

• To archive a marketing link, select the check box next to a link and click Archive Selected.

• To unarchive a marketing clink, click View Archive, select at least one link and click Unarchive Selected. Only previously archived marketing links will display in the View Archive page.

Create Acquisition Link Manually

You can create marketing links to acquire new mobile app users on-the-fly by manually configuring the URL parameters.

Important: This feature requires SDK version 4.6 or later. For more information, see Acquisition Prerequisites

The following diagram illustrates the components of a manually built tracking link and displays the different URL parameters that you must configure properly when manually creating acquisition links.

This link is configured to perform a platform-specific redirect to the Google Play store or the Apple App Store for a mobile app.

If the destination cannot be determined, the default store has been set to the Apple App Store. After the app has been installed, the my.custom.key:test

custom context key is attached to the Analytics Install Hit.

To manually create links, use the following URL format: http(s)://c00.adobe.com/v3/ {mobile-services-app-hash}/start? {parameters}

For iOS, ensure that you use the correct protocol:

Tip: The version of Android SDK you are using has no impact on this process.

• Use HTTP if you are using the iOS SDK older than version 4.7.0, or if you are using iOS SDK 4.7.0 or later and Use HTTPS is not selected on the Manage App Settings page.

• Use HTTPS if you are using iOS SDK 4.7.0 or later and Use HTTPS is selected on the Manage App Settings page

Where the following conditions have been met:

•

{mobile-services-app-hash}

matches the application identifier in the configuration file

(acquisition:appid

You can locate

{mobile-services-app-has}

in the Manage App Settings page under Acquisition SDK Options in the

Tracking ID field.

Acquisition

•

{parameters}

is a list of standard specifically named URL query parameters

Here is the list of parameters:

URL Parameter Description

a_g_id Google Play Store App Identifier a_g_lo a_i_id a_i_lo

Google Play Store Locale Override iTunes App Identifier iTunes Locale Override a_dd a_cid ctx* ctxa.referrer.campaign.name

Example Value

com.adobe.beardcons

835196493 jp

Default Store for Auto Redirect i | g

Custom ID Override (generally IDFA for iOS or ADID for Android)

Any String < 255 characters

(UTF-8 encoded)

Keys prefixed with ctx will end up in Context Data of the resulting launch hit ctxmy.custom.key=myValue

Acquisition Campaign Name

Although optional, is critical for reporting if you want to compare the performance of different acquisition links.

2015 Summit Conference ctxa.referrer.campaign.trackingcode

Tracking Code

Although optional, is critical for reporting if you want to compare the performance of different acquisition links.

lexsxouj ctxa.referrer.campaign.source

ctxa.referrer.campaign.medium

ctxa.referrer.campaign.content

Source

Medium

Content

Ad Network

Image # 325689

Acquisition

URL Parameter

ctxa.referrer.campaign.term

Description

Term

Example Value

hiking+boots

Remember the following information when you manually create acquisition links:

• All parameters that do not match parameters in the table are passed on as part of the app store redirect.

• All parameters are technically optional, although the link will be nonfunctional if at least one store ID is specified.

An example of a store ID is a_g_id

/ a_i_id

• If the destination store cannot be automatically determined, and no default is provided, an 404 error is returned.

Location

You can define geographical locations that you can use for correlation purposes in reports, target with in-app messages, and more.

Overview (Location)

The Location Overview report lets you see the different countries, regions, and Points of Interest where your app is being used.

This report provides a sunburst visualization for your existing data, and you can use the report to discover audience segments

(collections of visitors) for targeting. Creating and managing audiences is similar to creating and using segments, except that you can make the audiences available in the Marketing Cloud.

This section contains the following information:

•

Navigation and Usage

•

Add Breakdowns and Metrics

•

activity is pre-populated with the report data. For more information about creating a Target activity, see

•

Create a Sticky Filter

•

Share Reports

Navigation and Usage

This visualization provides, for example, the base report with breakdowns. The visualization uses height to show the metric in focus, and the performance differences between the metrics. Each ring represents an audience segment in the ring's category.

You can take actions on an audience, such as applying a Sticky Filter, hiding a metric, and viewing metrics.

Tip: In addition to this information, you can view an in-product tutorial that describes how to interact with the sunburst chart. To launch the tutorial, click Location Breakdown in the title bar of the report and click the i icon.

Location 99

This sunburst chart is interactive. You can change the time period by clicking the Calendar icon in the top right side. Mouse over any part of the chart to display more information. For example, in the following illustration, you can see the total number and the percentage of users using your app in the United States.

Location 100

In this illustration, the Categories buttons in the upper right corner allow you to toggle between viewing information about the top ten countries, regions, and the top three Points of Interest.

Here is the visualization when you select Country:

Here is the visualization when you select Points of Interest:

Location 101

You can click a slice in the ring to select the audience on which you can perform actions, such as zooming in, hiding audiences, and creating a Target activity, in-app message, or a Sticky Filter.

You can click a secondary metric on the right side to add it to the visualization and display this metric by using color, height, or both.

Location 102

Add Breakdowns and Metrics

You can add breakdowns and secondary metrics, which change the height of each audience relative to the other audiences in the chart.

Tip: The more rings you add to the sunburst, the longer it takes to process.

To add breakdowns and secondary metrics, click Location Breakdown in the title bar of the report and click Customize to open the right rail.

Location 103

When you click Add Breakdown or Add Metric, a new item displays with the same name as the previous item in the respective list. Click the newly created breakdown or metric to access a drop-down list from which you can select a new item.

Create a Target Activity

You can click a slice in the ring to select the audience on which you want to create a Target activity and click Target. The Target

Create a Sticky Filter

Click a slice in the ring to select the audience for which you want to create a sticky filter and click Sticky Filter. This sticky filter lets you apply the current filters and run a new report based on the filters.

Share Reports

After you create a report, your settings are used to create a custom URL, which you can copy and share.

Location

Map

You can view an interactive map that displays your Points of Interest and other data markers.

104

Here is some important information about the map:

• You can enlarge or shrink the map.

This feature is useful, for example, if you have two points of interest that are close together. Enlarging the map lets you view it in greater detail.

• Your points of interest display in blue.

Other data markers, such as Launches, display in black. Click a marker to view more information.

Click to select the following options:

Option Description

Map

Display a simple map.

Satellite

Display the map in satellite mode.

Data Markers

Choose whether to display black data markers.

Location 105

Option

Heat Map

Description

Choose whether to display heat-map markers. The greater the intensity of the color, the more frequently the condition (Launches, for example) is met.

Points of Interest

Choose whether to display your points of interest.

You can configure the following options for this report:

Option Description

Time Period

Click the Calendar icon to select a custom period or to select a preset time period from the drop-down list.

Customize

Filter

Customize your reports by changing the Show By options, adding metrics and filters, and adding additional series (metrics), and more

Select an icon that will display on the

Download

Click PDF or CSV to download or open documents and share with users who do not have access to Mobile Services or to use it in presentations.

Manage Points of Interest

You can create and manage points of interest, which allow you to define geographical locations that you can use for correlation purposes, target with in-app messages, and so on. When a hit is sent in a point of interest, the point of interest is attached to the hit.

To use Location features, you must do the following:

• You must have Analytics—Mobile Apps or Analytics Premium.

• You must enable Location Reports for the app.

For more information, see

Configure Options on the App Information Page

• If you are using a version of the iOS SDK or Android SDK before 4.2, after adding new Points of Interest, you must download a new configuration file and give it to your app developers.

If you are using the

iOS SDK

Android SDK

versions 4.2 or later, you do not need to submit an app update to the store to update your Points of Interest. On the Manage Points of Interest page, clicking Save packages changes to the Points of

Interest list and updates the configuration file for the live app. Saving also updates the list of points in your app on the user devices, as long as the app uses the updated SDK and configuration with a remote points-of-interest URL.

On the user's device, for a hit to be assigned to a Points of Interest, location must be enabled for the app.

Location

1. Click the name of the app to go to its Manage App Settings page.

2. Click Location > Manage Points of Interest.

106

Enter information in to each of the fields:

Option Description

Point Name

Enter the Point of Location name. This could be the name of a city, county, or region. You can also create a Point of Location around specific locations, such as sports stadiums or businesses.

Latitude

Enter the latitude of the Point of Location. You can find this information from other sources, including the Internet.

Location

Option

Longitude

Radius (Meters)

Description

Enter the longitude of the Point of Location. You can find this information from other sources, including the Internet.

Enter the radius (in meters) around the Point of Location that you want to include.

For example, if you create a point of interest, for Denver, Colorado, you could specify a radius large enough to include the city of Denver and the surrounding areas but exclude

Colorado Springs.

Before you can configure Push Messaging, see

and

Map

reports.

Map Icon

3. Add additional points of interest, as needed.

We recommend that you add no more than 5,000 points of interest. If you add more than 5,000, you can save the points, but you will receive a warning message informing you that best practices dictate having fewer than 5,000 points.

4. Click Save.

To delete one or more point of interest, select the desired check boxes, and click Remove Selected.

Click Import or Export to work with the data by using a

.csv

file instead of using the Adobe Mobile user interface.

107

Messaging 108

Messaging

Create, manage, and report on in-app and push messages.

This section contains the following information:

•

In-App Messages

•

Push Messages

•

SDK Documentation

In-App Messages

In-app messages are delivered to users in real-time, based on their actions and traits. The messages are triggered from Analytics data already tracked by the SDK.

The following message types are supported:

• Custom and themed

• Full screen

• Native alerts

• Local notifications

Here is how in-app messaging works:

• Requires SDK v4.2 or later.

• You must specify who has Mobile App Admin rights, which enables access to acquisition links and in-app messages.

For more information, see

Mobile App Administrator

• After a message is approved, the message is published automatically to the application.

• The SDK presents the message to users when the message parameters, such as traits, trigger, and schedule, are met.

• Messages can contain custom HTML or an image, using an online URL.

A backup or alternative image from the app bundle can also be specified for messages that are triggered while offline.

• Active and completed messages will provide reports on total views, click-through rates, and so on.

• Templates are available for custom messages, which allows you to easily build your own in-app message.

Push Messages

Push messages are sent to users who have opted in to receive notifications. You can target these push messages to users in

Analytics segments or custom segments. You can use push messages to re-engage passive users or to convey time-specific and location-specific information because the messages appear outside your app.

. After you perform these tasks, you must

configure push messaging in your app's settings. For more information, see

Configure Push Messaging

SDK Documentation

• For more information about the iOS SDK, see

iOS

• For more information about the Android SDK, see

Android

Manage Messages

View a list of your in-app and push messages with details about when each message was last updated and whether the messages are live or deactivated.

Messaging 109

You can duplicate, activate/deactivate, and archive/unarchive messages. You can also view a report that displays the number of users who have viewed the message and the number of users who have clicked through the message.

To manage messages, click <app name> > Messaging > Manage Messages.

Here is additional information about the tasks you can complete on messages:

•

Search and Filter Messages

•

Duplicate Messages

•

Deactivate or Activate Messages

•

Archive Messages

•

View Archived Messages

Search and Filter Messages

Use the Search box at the top of the list to search for and filter messages. Anything you type in the search box displays matching messages from the list. The search works across all table columns. For example, you can type

Draft

to display only messages with that status. You can also type a user's name to display only messages updated by that user.

In addition to the Search box, you can also click any column header to sort the list in ascending or descending order by the contents of that column.

For example, if you sort the Message Type column in ascending order, all of your in-app messages display before your push messages. If you sort the Last Updated column in descending order, the list displays your most recently updated messages at the top of the list.

Messaging 110

Duplicate Messages

1. Select the check box next to one or more messages and click Duplicate Selected.

2. Select the app for which you want to make a duplicate message.

3. Enter a name for the message.

To duplicate a message for the same app, enter a new name for the message. If you keep the same name to overwrite the original message. If you are duplicating a message for a different app, you can keep the same name without overwriting the original message.

4. Click Duplicate or Overwrite, as necessary.

Deactivate or Activate Messages

To deactivate a message, select the checkbox next to at least one active message and click Deactivate Selected.

To activate a dectivated message, select the checkbox next to at least one deactivated message and click Activate Selected.

Archive Messages

You can archive messages and clean up your message list.

Prerequisite: Before you can archive a message, you must deactivate it.

1. Select the checkbox next to at least one deactivated messages and click Archive Selected.

View Archived Messages

1. Click View Archive.

2. Select the checkbox next to at least one archived message and click Unarchive Selected.

View Message Reports

You can view message reports for in-app and push messages.

1. Click

in the Report column for a message.

2. (Optional) Create a

Sticky Filter

for the report or change the time period by clicking the Calendar icon.

Tip: Depending on the type of message you are viewing, the report might vary

In-App Messages

If you are viewing reports for an in-app message, the report looks similar to the following illustration:

Messaging 111

Available Metrics

Metric

Impression

Click throughs

Cancels

Engagement Rate

Payload

Description

When a message is triggered.

When a user presses the Click Through button on an alert or full-screen message and when a user opens the app from a local notification.

When a user presses the Cancel button on an alert or a full-screen message.

This is a calculated metric from Adobe Analytics and is the result of the number of click throughs divided by the number of impressions.

Provide a custom push payload in JSON to be sent to the app through a push or a local notification.

Messaging

Metric

112

Description

Important: The limit for Android is 4KB and for iOS it is 2KB.

Push Messages

If you are viewing reports for a push message, the report looks similar to the following illustration:

The chart at the top displays the number of users who opened the message.

Available Metrics

Column Description

Time

The time the message was pushed to devices from Mobile Services.

Status

The status of the message.

Messaging

Column

Published

Failed

Blacklisted

113

Description

The available statuses are

Cancelled

Scheduled

Executing

Executed

, or

Failed

The number of device tokens that are successfully sent to Apple Push Notification Service/Google

Cloud Messaging (APNS/GCM) to send the message to the users devices.

Here are some of the reasons that the number of device tokens that were not successfully sent to

APNS/GCM:

• An invalid pushID

• The push platform (APNS, GCM, and so on) that was given to push to does not exist for the job's application.

For example, the platform might collect iOS push tokens but does not have APNS service configured.

The message might have failed because the push service was not configured correctly or the Mobile

Services system is down.

Important: If you have an unusually large number of failures, check your push services configuration. If push services appears to be configured correctly, contact Adobe Customer

Care.

The number of device tokens that are no longer valid to be sent to APNS or GCM. This usually means the app has been uninstalled from the device or the user changed his or her opt-in settings to receive messages.

Android and iOS differ about when tokens are counted as blacklisted. Android tokens are immediately shown in the blacklisted count. iOS tokens are initially displayed as published, but based on feedback from APNS, are shown as blacklisted on subsequent messages.

Create a push message

You can send push messages to Analytics segments from the Mobile Services UI to leverage your robust Analytics data while engaging with users.

Prerequisite: Before you create a push message, see

1. Go to the Audience page for a

Push messages appear to users who opted in to receive notifications when they are not actively using your app. These notifications alert users about new updates, offers, and reminders. With this capability, you can create, test, manage, and report on push messages in one streamlined workflow.

Push messages are sent server-side by the app stores rather than from Mobile, as illustrated below:

Messaging 114

To create a push message:

1. Click <app name> > Messaging > Manage Messages > Create Message > Create Push.

2. Configure

Audience options

Configure the Audience options for a Push Message

You can configure audience options for push messages, including date range options, Analytics segments, and custom segments.

new push message

Important: As you configure the audience options, remember the following information:

• The Estimated Opt-In Audience is the number of devices that match the Adobe Analytics segment and the number of opted-in devices.

You can view an estimate of the number of users in your selected segment(s) that have opted in to receive messages and will receive the push message. The total number of app users displays below the estimate, regardless of opt-in status.

• The Total is the number of devices that match the Adobe Analytics segment.

• Push messages will be sent to the devices that are part of a defined Adobe Analytics segment and that have opted-in for push messages.

This means that the SDK has sent a value of

True

for the Push Message Opt-In evar.

• Even though the device has a valid device token, unless Adobe Analytics has set the opted-in flag, the message will not get pushed to the device.

• For more information about troubleshooting push messaging, see the following:

• iOS: Push Messaging

• Android: Push Messaging

2. Enter information in the following fields:

Messaging 115

Field

During The

Description

Enter the time frame to use for the estimated audience.

From the During The drop-down list, select an option:

• Last lets you select a relative time frame (for example, the last 7 days, last 30 days, or last 60 days) from the time the message is scheduled to push.

As an example, if you select the last 30 days and schedule the message to push on October

31, the estimated audience would be the number of users who have opted-in to receive push messages the 30 days before October 31.

• Static Range lets you select a static range by picking the beginning and end dates for the estimated audience range.

Using the previous example, if you select a date range beginning October 1 and ending October

15 but schedule the message to push on October 31, the estimated audience would be the number of users who have opted-in to receive push messages in the static date range that you specified (October 1 to October 15).

Analytics Segments

Custom Segments

Select one or more existing Adobe Analytics segment from the drop-down list.

For more information, see

Building Segments

in the Analytics Segmentation guide.

Select a metric or variable from the drop-down list (for example, Days Since Last Use or Point

of Interest) and configure the filter as desired.

For example, the following custom segment targets users who have a mobile phone running iOS and are in the California (United States) region.

3. Click Next to configure

Experience options

Experience: Push Message

You can configure experience options for push messages, including name, message text, and destination options. You can also configure advanced options, including payload options and custom options for iOS devices.

1. On the Audience page for a

new push message

, click Experience.

Messaging 116

2. Enter a name for this message.

3. Enter information in the following fields in the Message section:

Element Description

Content

Specify the text of your message. You can specify up to a maximum of 140 characters.

Destination

Select a specific destination, such as a web, deep, or hybrid link, to send users when they click-through the message.

into the space provided by the template in

Destinations

4. (Optional) Click the Show Advanced Options link to configure additional options:

Messaging 117

Element

Payload: Data

Description

Provide a custom push payload in JSON that will be sent to the app through a push or a local notification.

The limit for Android is 4KB, and the limit for iOS is 2KB.

Apple Options: Category

Provide a category for push and local notifications.

For more information, see

Managing Your App’s Notification Support

in the iOS Developer

Library.

Apple Options: Sound

Provide the name of the sound file in your app bundle to play. A default alert sound plays if not set.

For more information, see

Managing Your App's Notificaton Support

in the iOS Developer

Library.

Apple Options: Content

Available

Select this option so that when the message arrives, iOS wakes up your app in the background and allows your app to execute code based on the message payload.

For more information, see

Apple Push Notification Service

in the iOS Developer Library

5. (Optional) Preview the layout of your message by clicking following icons:

Icon Description

x Summary

Hide the preview pane. Click to redisplay the preview pane.

Click to change the orientation of the preview from portrait to landscape mode. For watches, the orientation changes from a round watch face to a square watch face.

Click to preview your message as it will appear on users's watches.

Click to preview your message as it will appear on users's mobile phones.

Click to preview your message as it will appear on users's tablets.

At the bottom of the preview pane, you can view a description of the audience that you selected in the previous step.

6. (Optional) Click Test to push your message to specified devices for testing purposes.

7. Select the service and enter the push tokens for at least one device to which you want to push the message.

Specify the tokens in a comma-separated list to push the message to more than one device.

Messaging

8. Configure

Schedule options

Schedule: Push Message

Configure schedule options for push messages.

1. On the Audience page for a

new push message

, click Schedule.

118

2. Fill in the fields:

Field

Now

Description

Push the message immediately (unless you subsequently click Save as Draft as explained in the next step).

Messaging 119

Field

At Time

Description

Specify the date and time you want to push the message.

3. Click Save as Draft to save the message in draft format.

You can choose this option to save an unfinished message or to save the message so that someone else can edit and approve the message before activating it. If you selected Now in the previous step, the draft message is sent immediately upon activation. If you selected a date and time to push the message, the message is pushed according to schedule. ,

To push the draft message later, complete one of the following tasks:

• Click Manage Messages, select the check box next to the message, then click Activate Selected.

• Click Save & Send to save the message and send it.

If you selected Now in the previous step, the message is immediately pushed. If you selected a date and time to push the message, the message is pushed according to schedule.

Troubleshooting Push Messaging

This information can help you troubleshoot push messaging.

Situation or issue Description

Why are there sometimes delays sending push messages?

The following types of delays might be associated with push messages for Mobile

Services:

• Waiting for Analytics Hits

Every report suite has a setting to determine when to process incoming Analytics hits.

The default is every 1 hour.

The actual processing of Analytics hits might take up to 30 minutes, but is typically

15-20 minutes. For example, a report suite processes hits every hour. When you factor the required processing time of 30 minutes max, it can take up to 90 minutes for an incoming hit to be available for a push message. If a user launched the app at 9:01

AM, the hit would appear in the Mobile Services UI as a new unique user between

10:15 to 10:30 AM.

• Waiting for the Push Service

The Push Service (APNS or GCM) might not immediately send out the message.

Although uncommon, there have been occurrences of wait times up to 5-10 minute.

You can verify that the push message has been sent to the Push Service by looking in the Report view of the Push Message, finding the message in the Message History table, and looking at the Published count.

Tip: This count is the number of successful sends to the Push Service(s).

The Push Services do not guarantee that a message will be sent. For more information about the reliability of service, see the following content:

Messaging

Situation or issue

120

Description

• APNS:

Quality of Service

on the iOS Developer Library site.

• GCM:

Lifetime of a Message

on the Google Developers site.

Why is my Android GCM API key invalid?

Invalid API key

Your API key might be invalid for the following reasons:

• The API key that you provided is not a server key with the correct GCM API key value.

• The server key has whitelisted the IPs and is blocking Adobe's servers from sending a push message.

Determine the validity of the API key

To determine the validity of your API key, run the following command:

Android

# api_key=YOUR_API_KEY

# curl --header "Authorization: key=$api_key" \

--header Content-Type:"application/json" \

https://gcm-http.googleapis.com/gcm/send \

-d "{\"registration_ids\":[\"ABC\"]}"

A returned 401 HTTP status code means that your API key is invalid. Otherwise, you will see something similar to this:

{"multicast_id":6782339717028231855,"success":0,"failure":1,

"canonical_ids":0,"results":[{"error":"InvalidRegistration"}]}

You can also check the validity of a registration token by replacing

"ABC"

with the token.

Why is my APNS cert not working?

Invalid Certificate

Your APNS certificate might be invalid for the following reasons:

• You might be using a sandbox certificate instead of the production certificate.

• You are using a new production/sandbox certificate that is not supported.

• You are using .p8 file instead of a .p12 file.

Create an in-app message

You can create an in-app message for delivery to mobile users. When creating the message, you configure the message type, audience, experience, and schedule.

Tip: To create in-app messages, customers must have Analytics—Mobile Apps or Analytics Premium.

1. In your app, click Messaging > Manage Messages > Create Message > Create In-App.

2. Configure the

Audience options

Messaging 121

Audience: In-App Message

You can configure audience options for in-app messages, including view, trigger, and trait options.

1. In your app, click Messaging > Manage Messages > Create Message > Create In-App.

2. On the Audience page, enter information in the following fields:

Field Description

View

Select the option that triggers a message to display:

• Always

This option means that the message is displayed each time the trigger occurs.

• Once

This option means that the message is displayed only the first time the trigger occurs.

• Until Click-Through

This option means that means that the message is displayed each time the trigger occurs until the user clicks through. This trigger applies only to full screen and alert messages.

Most messages need to redirect or use a resource from the internet and will not display if offline.

To always show the message regardless of network connectivity, select the Show Offline check box.

Trigger

Select an option from the drop-down list and select a condition.

For example, you could select Launched from the first drop-down list and Exists from the second drop-down list.

You can also specify custom context data that needs to be in the triggering hit to display the message.

Important: If you select multiple triggers, for the message to display, all triggers must occur on the same hit.

Traits

You can determine who should see the in-app message when it is triggered and filter (segment) the audience to hits that have specified data.

For example, you can define a rule in which Points of Interest contain Denver. This filter allows you to show the message to customers that are in one of your points of interest with Denver in the name, at the trigger time.

Experience: In-App Message

Configure experience options for in-app messages, including type (full screen, alert, or notification) and display, text, and button options.

1. In your app, click Messaging > Manage Messages > Create Message > Create In-App.

Messaging

2. On the Experience page, enter a name for the message.

3. Complete the fields in the Type section:

Field Description

Type

Select the message type for your in-app message campaign:

• Full Screen

• Alert

• Local Notification

Template

Customize a themed responsive message template for your content.

Tip: This option is displayed only when you select the Full Screen message type.

122

Custom

Load your custom HTML content (full screen only). You must provide a click-through link and a cancel link.

1. Click Browse and download an HTML file or drag an HTML document to the window.

2. Click Download Example to view sample custom HTML content.

Tip: This option is displayed only when you select the Full Screen message type.

4. Complete the fields in the Display section:

Field Description

Theme

Select a theme for your message.

Layout

Image URL

Select the app layout on the device screen.

The URL for an image.

If you have sizing issues when using the full-screen template, see My image does not fit exactly

Troubleshooting In-App Messaging

Bundled Image

Path to an image in your app code bundle. This option is used when there is no image. or the image is unavailable. The imagine might not be available if, for example, the device is offline.

If you have sizing issues when using the full-screen template, see My image does not fit exactly

into the space provided by the template in

Troubleshooting In-App Messaging

5. Complete the fields in the Text section:

Field Description

Header

Enter the text for the message's header.

Messaging 123

Field

Content

Description

Enter the text for the message's content.

6. Complete the fields in the Buttons section:

Field Description

Click-Through Button

Label for the Click-Through button. Tapping this button will count as a successful click-through.

The user will be redirected to the destination.

Destination

Cancel Button

Select a specific destination, such as a web, deep, or hybrid link, to send users when they click-through the message.

The redirect URL for a successful click-through. This URL might contain the following information:

•

{userId}

, which is replaced with the user identifier or is blank when the user identifier is not set.

•

{trackingId}

, which is replaced with the aid (correlates with s_vi cookie).

•

{messageId}

, which is replaced with the unique ID for the in-app message.

•

{lifetimeValue}

, which is replaced with the lifetime value or 0 if no lifetime value exists.

Here is an example of tracking the user ID: http://www.mysite.com?uid={userId}

If the click-through URL uses http://

or https://

, the URL will open in the device browser outside the app. Otherwise, each platform supports schemes that allow you to open or reference your app if the app has been developed to support the custom scheme.

App Store Average Rating

Destinations

Label for the Cancel button. Tapping this button closes the message.

7. (Optional) Preview the layout of your message by clicking following icons:

Icon Description

x Summary

Hide the preview pane. Click to redisplay the preview pane.

Click to change the orientation of the preview from portrait to landscape mode. For watches, the orientation changes from a round watch face to a square watch face.

Click to preview your message as it will appear on users's watches.

Messaging

Icon Description

Click to preview your message as it will appear on users's mobile phones.

Click to preview your message as it will appear on users's tablets.

You can also view a description of the audience you selected in the previous step at the bottom of the preview pane.

8. Configure

Schedule options

Schedule: In-App Message

You can configure schedule options for in-app messages, including duration, days of the week, and time of the day options.

Tip: Date ranges are defined by your time zone. Specific days and time ranges are relative to the user's device.

1. In your app, click Messaging > Manage Messages > Create Message > Create In-App.

2. Click Schedule.

3. Complete the following fields in the Duration section:

Field Description

Every Day

Display your message to users every day.

Start and End Use the Calendar icons to select a start and end date for your message.

4. Complete the following fields in the Days of the Week section:

Field Description

Every Day

Display your message to users every day of the week.

Days of the Week

Click on the days of the week to select the days on which you want to display your message.

5. Complete the following fields in the Time of Day section:

Field Description

All Day

Display your message during all hours of the day.

Time Slider

Adjust the slider to specify the hours of the day to display your message.

6. Click Save or Save & Activate.

124

Messaging 125

Troubleshooting In-App Messaging

This information can help you troubleshoot your in-app messaging issues.

If you completed all the requirements for In-App Messaging, but messages do not show up, verify the following items:

Situation or Issue Suggestion

Are you putting the new configuration and new SDK in the app?

Verify that the SDK is version 4.2 or higher and is correctly configured. For a screen shot showing the SDK version, see

View Hits

in the Bloodhound documentation.

Important: As of April 30, 2017, Adobe Bloodhound has been sunset. Starting on

May 1, 2017, no additional enhancements and no additional Engineering or Adobe

Expert Care support will be provided.

Ensure that you have a

Messages

section in your configuration (the downloaded JSON file) or have a Messages remote endpoint, so that it can be retrieved from dynamic tag management.

My full screen message in Android is not showing up. I am using the correct SDK, configuration, and my triggers are being met.

Did you update your manifest file to define the full screen activity?

My local notification message in

Android isn't working.

Verify that the local notification broadcast receiver is declared in your manifest.

For more information, see step #1 in the

How to Enable

section in

In-App Messaging

Is the message live?

Double check the traits/trigger sections.

Check the list view in the Status column on the Manage In-App Message page and verify whether the message is live.

Verify assumptions in data for traits/trigger in bloodhound.

Validate the hits in bloodhound. For a screen shot showing the SDK version, see

View

Hits

in the Bloodhound documentation.

Important: As of April 30, 2017, Adobe Bloodhound has been sunset. Starting on

May 1, 2017, no additional enhancements and no additional Engineering or Adobe

Expert Care support will be provided.

Look at show once, show always,

show offline settings on the

Audience page.

Verify that these settings are correct. On the Audience page, review the options on the

Trigger tab, where you can specify how often the message is displayed.

If using launch event as trigger...

Launch only fires on a new session. For information on when a session begins, see

lifecycleTimeout in the

JSON Config

file.

Messaging 126

Situation or Issue Suggestion

I updated my message remotely but my app is still showing the old message.

Complete one of the following tasks:

• Dynamic tag management might take a few minutes to update its endpoint with your new definition.

Give it some time and try again.

• The config will only update on a new launch.

If the app was restarted in the life cycle session timeout, your new config might not have been downloaded.

My image does not fit exactly into the space provided by the template.

The In-App Message full-screen template supports showing an image from a remote server (Image URL) or from the app bundle (Bundled Image). The image should be in a standard image format, for example, JPG, GIF, or PNG.

Due to device screens having many different dimensions, the image probably not fit exactly into the space provided by the template. The template always focuses on showing the center of the image and crops (portrait) or fades (landscape) the sides if the image does not fit.

Here is the exact placement and sizing rules for each orientation:

• Portrait, where the image is scaled to height of 195px for phone, 529px for tablet, centered if image width is smaller than device width, and cropped if image width is greater than device width.

• Landscape, where the image is scaled to 100% of height of device, width is 75% of the device, and with a fade out on the right.

If you have issues with the full-screen template, you can download and use the Custom

HTML template. The Custom HTML template provides greater flexibility for images and allows full control of the template.

My messages are not reflecting changes/updates I have made in the

UI.

The SDK fetches new/updated messages at the time of a lifecycle launch. This is only when the application is closed/backgrounded for greater than the lifecycle timeout value and then re-opened.

Complete the following steps:

1. Curl your messages URL in your config file to verify the remote message is updated

(for example, curl

"https://assets.adobedtm.com/b213090c5204bf94318f4ef0539a38b487d10368/scripts/satellite-542c62859662383b1a0008f4.json"

)

2. Close the application.

3. Wait for a time period that is longer than the lifecycleTimeout in the config file.

4. Open the app, navigate to where the message should be displayed, and verify that it has been updated.

App Store 127

App Store

The appFigures data connector integration combines the power of the appFigures integrated mobile app store analytics and the direct app tracking of Adobe Analytics to create powerful analytics and optimization opportunities for your organization.

Tip: In the Mobile Services UI, the App Store menu item and associated reports display in the left navigation menu after you configure the integration.

appFigures Data Connector for Adobe Analytics

contains the following information:

• To help you understand the key benefits and features of the integration

• To consider before implementing the integration, including the following:

• Adobe Analytics requirements

• appFigures requirements

• Pricing

• Analytics integration variables

• To help you configure the integration

• About the metrics and dimensions included in the integration

• To help you segment app data

App Store Overview

The App Store Overview report gives you a snapshot of your app store metrics, including the number of downloads, in-app purchases, app store average rating, download revenue, in-app revenue, downloads by country, downloads by app store, and in-app purchases by name.

Tip: In the Mobile Services UI, the App Store menu item and Overview report appear in the left navigation menu after you configure the integration.

The Overview report contains an over-time graph that displays information about the number of app-store downloads, in-app purchases made using your app, and your app's average rating.

App Store 128

You can click any metric to hide or display its corresponding line. To view the data for a day, hover over that day.

The following information displays below the graph:

•

•

Download Revenue

•

In-App Revenue

•

Downloads by Country

•

Downloads by App Store

•

In-App Purchases by Name

Note: In addition to changing the report's date range by clicking the calendar icon in the top right, you can customize some of the drill-down reports, add filters and series (metrics), add sticky filters, and download the report in PDF or CSV format.

For more information, see

Customize Reports .

App Store Average Rating

This report displays the average rating users gave your app using app-store functionality.

App Store 129

You can click anywhere on the App Store Average Rating widget to display a graph and chart that displays the average rating by date. To view the data for a day, hover over that day.

Download Revenue

This report displays the amount of revenue that is generated by downloading your app.

In-App Revenue

This report displays the amount of revenue from in-app purchases that were made using your app.

Downloads by Country

This report displays the number of downloads for your app grouped by country.

App Store 130

To display a graph and chart that displays the number of downloads per country by date, click Downloads by Country. You can hover over a date to view the data for a day.

Downloads by App Store

This report displays the number of downloads for your app grouped by app store.

App Store 131

To display a graph and chart that displays the number of downloads per app store grouped by date, click Downloads by App

Store. You can hover over a date to view the data for that day.

In-App Purchases by Name

This report displays all in-app purchases by name.

Target 132

Target

You can create Target activities to perform A/B tests and target content in Mobile Services.

Prerequisite: Before you can deliver dynamic content in your app, you must link your Adobe Target account to your Adobe

ID.

Target activities in Adobe Mobile provide a subset of the complete Adobe Target capabilities and should be created and edited in Adobe Mobile.

Create a Target Audience

This section illustrates how to create a Target audience that can be used to run targeted and personalized activities using the same target location. Some commonly used audiences are pre-built so that they can be easily added to an audience in one click.

For more information about Target audiences, see

Audiences

1. Click Target > Audiences > Create New.

2. For Rule #1, select the attribute type.

When you click on a type, additional drop-down lists appear from which you can select additional options.

Element Description

Geo

The geographical location of the user.

Network

The ISP or connection speed of the user.

Mobile Lifecycle

Custom

Visitor Profile

Select from a variety of different mobile lifecycle parameters.

Create your own parameter.

Custom parameters are valid only during the session. Profile parameters are stored on the user's profile and are valid cross sessions and channels.

Select from new or returning visitors.

3. (Optional) Click Add Rule to add additional rules for your audience.

For example, to create an audience that includes users visiting for the first time that are also located in Utah, you would add a second rule and select the attribute type Visitor Profile, and select New Visitor in the drop-down box.

4. Click Next

5. Enter an audience name and click Save.

Create a Target Activity

This section illustrates how you can create an A/B test or Experience Targeting (XT) activity to show Experience A to one set of users and Experience B to a second set of users. The goal is to see how these two experiences impact registration.

Target 133

Attention: The screenshots in this section are from the Adobe Mobile Services UI. The same activity can also be created in the Target UI using the

Form-based experience composer

. For more information about Target activities, see Activities .

1. Click Target > Activities > Create New.

2. Enter an activity name.

3. Move the Active slider to On.

4. Select today's date as the start date and select a date in the future as your end date.

5. Select your Audience and Content Location.

6. Click Test Experience to set your control.

7. Enter an experience by clicking Select Offer to select an offer from your content library.

Important: Toggling between and allows you to switch the activity from an A/B test to Experience Targeting

(XT). With XT, you can select a specific segment or audience that you created. For more information, see Create a Target

Audience and

Experience Targeting .

8. Click Save.

9. On the Information page, click Add Experience and repeat step 7.

You have added two experiences, and you are allocating 50% traffic to each experience.

10. In Success Location, enter a location.

This field is case sensitive and the information that you entered should be identical to what you tagged in xcode

11. Click Save.

Your activity should now look like the image below. For more information about Target reports, see

Reports

To open Target Standard/Premium and view reports on the activity:

1. click Target > Activities.

2. Select an activity.

3. At the bottom of the page, click View Reports.

Target 134

Create Target Content

This section illustrates how to create Target content that can be used to run targeted and personalized activities using the same target location.

For more information about Target content, see

Content

1. Click Target > Content > Create New.

2. Enter a content name.

For example, you might want to create an offer for 10% or for free shipping.

3. Enter a content description.

4. Click Save.

DPS (Digital Publishing Solution) 135

DPS (Digital Publishing Solution)

You can view reports that are available to Digital Publishing Solution (DPS) customers.

DPS reports allow you to track the user data of your custom viewer app from Mobile Services. When you subscribe to the Adobe

Digital Publishing Suite with a Professional or Enterprise account, you get access to base-level analytics for all your apps.

Apps that are created from DPS have access to the Adobe Mobile core service user interface through Analytics Essentials – DPS.

For more information, see

DPS Analytics in the Digital Publishing Solution Help

Top 10 Articles

The Top 10 Articles report displays a sunburst visualization for your data. This report is available only to Digital Publishing

Solutions (DPS) customers.

DPS (Digital Publishing Solution) 136

By default, this report shows the article title, the number of readers, percentage of total readers, and the article title instances and percentage.

This report is similar to the Technology report. For information about how to navigate and use sunburst reports; add breakdowns

and metrics; create target activities; create sticky filters, and share reports, see

. The information in the topic can be

used to customize the Top 10 Articles report.

Top 50 Articles

The Top 50 Articles report displays a bar chart and ranked report showing the most-read articles displayed using the app. This report is available only to Digital Publishing Solutions (DPS) customers.

Although the default report displays data for the last 30 days by number of readers, you can customize the report as desired.

DPS (Digital Publishing Solution) 137

By default, this report shows article title and the number readers.

You can configure the following options for this report:

Option Description

Time Period

Click the Calendar icon to select a custom period or to select a preset time period from the drop-down list.

Customize

Filter

Download

Customize your reports by changing the Show By options, adding metrics and filters, and adding additional series (metrics), and more

and metrics; create target activities; create sticky filters, and share reports, see

Click PDF or CSV to download or open documents and share with users who do not have access to Mobile Services or to use it in presentations.

DPS (Digital Publishing Solution) 138

Social Sharing

The Social Sharing report displays a sunburst visualization for your existing data. This report is available to Digital Publishing

Solutions (DPS) customers only.

By default, this report shows the number of readers who shared articles in different channels, such as email, message, and so on.

This report is similar to the Technology report. For information about how to navigate and use sunburst reports; add breakdowns

. The information in the Technology

topic can be used to customize the Social Sharing report.

DPS (Digital Publishing Solution)

Banner Metrics

The Banner Metrics report displays a sunburst visualization for your existing data. This report is only available to Digital

Publishing Solutions (DPS) customers.

139

By default, this report displays the following metrics:

• Banner Name, which is the name of the banner.

• Readers, which is the number of app users.

• Banner Name Instances, which is the number of times the banner was referenced (clicks and impressions).

• Banner Click, which is the number of times users clicked the banner.

• Banner Impressions, which is the number of times a banner was viewed (or was visible) on a browser page.

This report is similar to the Technology report. For information about how to navigate and use sunburst reports; add breakdowns

and metrics; create target activities; create sticky filters, and share reports, see

. The information in this topic can be

used to customize the Banner Metrics report.

Reference

You can review the reference material to help you get the most out of Adobe Mobile.

140

Customize Reports

This information helps you understand and customize the built-in reports.

You can customize your reports by changing the date range, the Show By options (display graph and table data by time periods or by dimensions), add metrics and filters, add additional series (metrics), and more.

To display the Customize rail, click the name of the app to go to its Overview page, and click Customize.

The following example shows the Users & Sessions report with the open Customize rail. This example displays data for the last

30 days, shown by days, with four active series:

• Users

• Launches

• First Launches

• App Store Downloads

Reference 141

The following information describes each area of the report and the Customize rail:

Reference 142

Number Description

1 In Date Ranges, the drop-down list lets you select various date ranges for your report. All data in the chart (9) and corresponding table (10) respects the selected date range.

In Show By, the drop-down list lets you select a time-based or dimension-based display for your report.

For example, in the illustration, you can see that Days is selected. If you look at the dates below the chart (7) and the rows in the table (8), data is categorized by date in an over-time report. A maximum of six metrics can be reported on over-time reports by adding additional series to the report.

If you select a Lifecycle dimension, you can view the top 50 values in a ranked list, the top 5 values trended by day or week, or a top 5 or 10 values breakdown.

Series represents individual metrics, such as Users, Launches, First Launches, and App Store Downloads in the above example. Each series is color coded with data in the chart (7) and table (8).

You can add additional series (metrics) and even different apps in different report suites to compare data.

For more information, see

Add Series (Metrics) to Reports

With Add Filter, you can customize the built-in reports by adding additional filters (segments).

For more information, see

Add Filters to Reports

With Add Series, you can customize the built-in reports by adding additional series (metrics) or apps in different report suites to compare data.

For more information, see

Add Series (Metrics) to Reports

With Sticky Filter, you can create a filter that spans different reports. For example, you might want to see how a particular segment is performing across all mobile reports. A sticky filter lets you define a filter that is applied to all non-pathing reports.

For more information, see

implementation. For further detail on our updates, see our

The Data Chart displays data in an appropriate chart based on the selected metrics. Chart types include line charts, bar charts, donut charts, etc.

The Data Table displays data in tabular form. You can click a column header to sort the data in ascending or descending order.

Add Filters to Reports

This information helps you customize the built-in reports by adding additional filters (segments).

Important: Mobile app metrics are also available in marketing reports & analytics, ad hoc analysis, data warehouse, and other Analytics reporting interfaces. If a breakdown or report type is not available in Adobe Mobile, it can be generated by using a different reporting interface.

Reference

In this example, we will customize the Users & Sessions report, but the instructions apply to any report.

1. Open your app and click Usage > Users & Sessions.

143

This report provides a complete overtime view of our app users. However, metrics for both the iOS and Android versions of this app are collected in the same report suite. We can segment users by mobile OS by adding a custom filter to the Users metric.

2. Click Customize.

Reference

3. Under Users, click Add Filterand click Add Rule,

4. Select Operating Systems, and from the drop-down list, and select iOS.

144

We need to repeat this step to add Android as a filter.

5. Click And, select Operating Systems from the drop-down list, and select Android.

Your filters should now look like the following example:

6. Click Update.

7. To regenerate the report, click Run.

Reference 145

This report now shows users broken down by operating system. The report title was changed to match the filters that were applied to the report.

We can customize this report more. With the recent launch of iOS 8.3, we can add the First Launches metric with an iOS

8.3 operating system version filter to see how many customers with iOS 8.3 upgraded their apps and performed a first launch.

8. Under First Launches, click Add Filter, click Add Rule, select Operating Systems from the drop-down list, and select iOS.

9. Click And, select Operating System Versions from the drop-down list, and select iOS 8.3.

Your filters should now look like this example:

Reference

10. Click Update and Run.

This report now shows users with iOS 8.3 who have launched the app for the first time.

146

Reference 147

Take some time to test the different options on the report customization menu, and ensure that you bookmark your favorites.

Report URLs in Adobe Mobile are fully functional bookmarks that can be emailed or added to your favorites.

Add Series (Metrics) to Reports

This information helps you customize the built-in reports by adding additional series (metrics) or apps in different report suites to compare data.

In this example, we will customize the Users & Sessions report, but the instructions apply to any report.

1. Open your app and click Usage > Users & Sessions.

Reference 148

This report provides a complete overtime view of our app users. However, we want to add a series to report on app crashes.

2. Click Customize.

3. Scroll down and click Add Series.

The name of the series is populated with the same name as the last series in your list. In the previous illustration, the latest series is App Store Downloads, so a new series is added and is also titled App Store Downloads.

4. Complete one of the following tasks:

Reference

• To add a new series (metric), click the name of the series you just created and select a new Lifecycle metric from the drop-down list.

149

• To add a new app (in a different report suite) so that you can compare data across apps, click the app name in the newly created series and select the desired app.

Reference

5. (Conditional) Add filters to the new series.

For more information, see

Add Filters to Reports

6. Click Update and Run.

150

Add Sticky Filter

Create a filter that spans different reports to see how a particular segment is performing across all mobile reports. A sticky filter lets you define a filter that is applied to all non-pathing reports.

The following example adds sticky filters for iOS and Android operating systems to the Users & Sessions report, but the instructions apply to any report or metric.

1. Click the Filter icon at the top of any report in Adobe Mobile to access the Sticky Filter dialog box.

2. Click Add Rule, select Operating Systems, and from the drop-down list, select iOS.

We need to repeat this step to add Android as a filter.

3. Click And, select Operating Systems, and from the drop-down list, select Android.

Reference

Your filters should now look like the following example:

4. Click Update and Run.

151

Frequently Asked Questions - Mobile Services 152

Frequently Asked Questions - Mobile Services

Frequently asked questions and answers for Adobe Mobile Services, and a general description of features.

•

•

•

•

•

Adobe Mobile SDK

Question Answer

Do you make frequent updates with the SDK?

Yes, we are constantly making updates in effort to get you the most feature rich, standard-compliant, and secure SDKs. We typically release a new version every month.

These SDK updates are drop-in replacements (for version 4x) to aid in ease of

What SDK version should I be on?

Our current SDKs are on version 4.11. For further detail, please see our

created a new app report suite

Where can I download the SDKs?

SDKs for individual mobile platforms may be downloaded by visiting the

Manage App

Settings

section.

How do I configure the SDKs?

After you have

, navigate to Manage App Settings and

configure

all of the required options on the app information page. After you save your configuration, download the required SDKs from the bottom of the Manage App Settings page. The SDK will come pre-configured with the options you have saved and can be found in the ADBMobileConfig.json file within the SDK package. If you change any

SDK settings on the Manage App Settings page, make sure you re-download the SDK files or update your ADBMobileConfig.json file with the necessary changes.

Do the Adobe Mobile SDKs support

IPv6 for iOS?

The Adobe Mobile SDKs use the standard iOS and Android network stacks. For iOS, the SDK uses NSURLSession (iOS versions 7+) and NSURLConnection (iOS versions

<7) which are fully compliant with IPv6. Developers who have built or use their own networking stack may want to review if there are other mitigating considerations.

Further information from

Apple:

"If you're writing a client-side app using high-level networking APIs such as NSURLSession and the CFNetwork frameworks and you connect by name, you should not need to change anything for your app to work with IPv6 addresses".

Frequently Asked Questions - Mobile Services 153

Adobe Analytics

Question

What are Lifecycle Metrics?

Answer

Lifecycle Metrics are "out-of-the-box" metrics that are automatically collected when the

SDK is first implemented in your app. Please see

Lifecycle Metrics

documentation for more detail.

How can I troubleshoot processing rules?

Please consult the

processing rules tips & tricks guide

for more detail.

Can I send my analytics data to multiple report suites?

Yes. The SDKs provide the ability to send data to multiple Adobe Analytics report suites.

To capture data into multiple report suites using a single image request, set the mutiple

RSIDs (report suite IDs) into the "rsids" field (under "anayltics" section) in the

ADBMobileConfig.json file delimited by commas (with no spaces in-between). For further detail, please review

(see rsids variable).

How are Mobile visits different from launches?

A launch is measured by the SDK when a user opens the app for the first time or returns to the app after having been out of the app for longer than a specified timeout value. The typical timeout is 5 minutes (300 seconds in lifecycleTimeout field found in the

ADBMobileConfig.json file).

A visit is a server-side calculation by Adobe Analytics based on the first and last data hits sent in by the SDK without exceeding a visit timeout. Typically, session timeouts are set at 30 minutes for a report suite. Although visits come from traditional web analytics, they still provide valuable insights into how users bounce in and out of your app.

Messaging

Question Answer

Are there size or other limitations on push notifications?

Push notification messages have a 140 character limit. There are no limits on how many notifications might be sent or scheduled or how often notifications are sent.

Do you support custom payloads for push notifications?

Yes, we provide for a custom push payload that may coded in JSON. Android and iOS payloads are restricted to 4KB and 2KB respectively. These payloads are sent to the app via a push or a local notification. Please see our

for more detail.

Are there size limitations on in-app messages?

Published and active in-app messages created in Adobe Mobile Services are hosted on a server with a 15MB size restriction per app report suite. While this restriction applies to message content and resources hosted with Adobe, there are no restrictions on what resources the in-app message may refer to on other hosts or those within the app.

Can I use my own HTML for in-app messages?

Yes, we support custom HTML for your in-app messages. Please see our

message to display. Please consult our

for more detail.

Frequently Asked Questions - Mobile Services 154

Question Answer

What triggers can I use to send push notifications or in-app messages?

Marketers may choose any Analytics data or event that is being sent as a trigger to display in-app messages. In-app messages use triggers that happen locally on the device. If multiple triggers are chosen, all triggers must occur in the same hit in order for the

for more detail.

Push messages are sent using pre-existing Adobe Analytics segments or custom segments that may be created on historic Analytics data already collected. Please consult our

conversions. Please see our

for more detail.

Location

Question Answer

Is there a limit on how many Points of Interest (POIs) I can have?

While there isn't a specific restriction, for ideal performance and due to memory restrictions on the user's device, we recommend creating or uploading no more than

5000 Points of Interest.

Acquisition

Question Answer

Can I attribute campaigns to in-app activities?

Yes. Adobe Mobile Services can help you build marketing tricks that help promote and drive traffic to your apps and tie acquisition campaigns to in-app analytics and

documentation for more detail.

How can I set up links to acquire and track new app users?

You can create marketing links that route users to download applications from the Apple

App Store and Google Play. The links you create enable you to attribute your success events to the downloads. Please see documentation on building

marketing links

for more

detail.

Documentation Updates 155

Documentation Updates

All updates (additions, deletions, and corrections) to the Adobe Mobile User Guide, by date.

This section contains detailed information about updates to this guide that might not be included in the Release Notes. Consult

the

for information about new features and bug fixes.

Date and Topic Description

02/07/2017

Create or Edit Marketing Links

Added information on custom interstitials.

11/10/2016

Universal Links and App

Updated Marketing Links documentation and added new topic:

Links

10/20/2016

Target

Added 3 new topics for accessing and creating Target content Adobe Mobile Services.

9/1/2016 Added information about GCM API key validation.

Troubleshooting Push Messaging

Added information on how to read message reports.

View Message Reports

6/2/2016

Experience: Push Message

Revised topic.

5/5/2016

Specified the size limit for a custom push payload in JSON (Android: 4KB; iOS: 2KB).

4/21/2016

4/21/2016

Getting Started with Acquisition

Edited and reorganized entire section.

New topics and their subtopics include the following:

•

•

Create and Manage Link Destinations

•

Marketing Links Builder

2/4/2016

Updated syntax about creating an acquisition link manually and added "Important" note.

2/18/2016 New topic.

Documentation Updates 156

Date and Topic

Crashes

2/18/2016

App Store Overview

1/21/2016

Use Legacy Acquisition Links

Description

The user interface for the App Store Overview report has been updated for apps that have been integrated with appFigures.

Edited page to reflect new functionality that displays your most recently viewed apps on the

Overview page.

1/21/2016

Custom Data Content

12/01/2015

Added information about custom list variables.

Moved topics for the legacy acquisition link functionality under this new topic.

10/15/2015 New topics:

DPS (Digital Publishing Solution)

•

DPS (Digital Publishing Solution)

•

•

•

•

10/15/2015

Mobile Metrics and Dimensions

Reference

Added additional information to the Launches row.

09/25/2015

Create an in-app message

Manage Points of Interest

Added information to each topic that customers must have Analytics—Mobile Apps or

Analytics Premium in order to use the following functionality:

• In-app messaging

• Acquisition campaign tracking

• Points of Interest analytics

09/17/2015

Configure Postbacks

09/17/2015

Configure Push Messaging

New topic.

06/23/2015

Configure App to use APNS or

New topic.

Documentation Updates

Date and Topic

09/17/2015

GCM

Description

New topic.

9/17/2015

Prerequisites to Enable Push

Frequently Asked Questions -

New topic.

Configure App to use APNS or

GCM

New topic.

09/17/2015

Create a push message

New topic.

09/17/2015

Manage Messages

09/17/2015

View Message Reports

09/01/2105

App Store

New topic.

New topics:

•

App Store

•

App Store Overview

06/18/2105

Mobile Services

06/01/2015

Troubleshooting In-App

Create an in-app message

05/29/2015

05/21/2015

Added information to explain the difference between mobile app visits and launches.

Added the following row to the table:

"My image does not fit exactly into the space provided by the template."

Added the following paragraph to the Click-Through URL section:

If the click-through URL uses http://

or https://

, the URL will open in the device browser outside of the app. Otherwise, each platform supports schemes that allow you to open or reference your app if the app has been developed to support the custom scheme.

Added information about the Browser Region option for the Apple App Store.

157

Documentation Updates

Date and Topic

Create an Acquisition Link

05/05/2015

Documentation Updates

05/05/2015

Historical Release Notes

Description

158

New topic.

Contains detailed information about updates to this guide that might not be included in the

Release Notes. Consult the

you to brand your pages. See

for information about new features and bug fixes.

New topic.

Contains historical release notes for Adobe Mobile, listed by release date in descending order.

Historical Release Notes 159

Historical Release Notes

Historical release notes for Adobe Mobile, listed by release date in descending order.

February 16th, 2017

The Mobile Services February 16, 2017 release includes the following changes:

Feature Description

Custom Interstitials

Marketers can now customize interstitial landing pages with custom HTML/CSS/JS, allowing

for more information.

Fixes

• Localization - Minor bug fixes.

January 19th, 2017

The Mobile Services January 19, 2017 release includes the following changes:

Improvements

Resource Description

Localization Italian localization is now supported.

Retention

Retention report performance has been improved.

Technology Breakdown PDF will now reflect secondary metric, hidden, selected, and zoomed audiences.

Updated Usage and Technology Overviews to show the Operating System Type dimension rather than the deprecated Mobile Operating System dimension.

November 10, 2016

Important: Accessing Target functionality within Mobile Services now requires that users be logged in with an Adobe ID that is provisioned for their Target company. Logging in with a Target username and password has been removed.

The Mobile Services November 10, 2016 release includes the following changes:

Improvements

Resource Description

Create and Manage Link Destinations

Marketing links now support Universal Links (iOS) and App Links (Android) as destinations.

This new feature provides for seamless routing between deep links (if an app is installed) and app stores or other fallback destinations (if an app is not installed).

Historical Release Notes 160

October 20, 2016

The Mobile Services October 20, 2016 release includes the following changes:

Improvements

Resource Description

Target Mobile audiences, activities, and content are now accessible across Target and Mobile Services regardless of where they were created.

Postbacks

Push Messaging

Added a new postback type: PII

The PII postback type enables the user to send data tagged with CollectPII calls to 3 rd

party endpoints. More information on this postback type coming soon.

Push certificate expiration management allows you to see the expiration date of your push certificates and also receive reminders to update the certificate before it expires. For more information, see

Troubleshooting Push Messaging

Analytics Reporting

SDK

Dimension and metric permissions set in Adobe Analytics now apply to Mobile Services.

For more information, see

Administrative Product Changes Coming in October 2016

Xamarin, Unity, and PhoneGap plugins are updated to work with iOS and Android SDKs version 4.13.1.

Mobile App Admin In order to modify settings in Mobile Services, users were previously required to be added to a group called Mobile App Admin in Adobe Analytics. This has changed and users now only need to be a part of a group that has Mobile App Admin selected in the Tools section of the group's settings. Because of this change, all Analytics Admins are now Mobile App

Admins.

August 18, 2016

The Mobile Services August 18, 2016 release includes the following changes:

Improvement

Resource Description

Marketing Links Builder Marketing Links Builder now includes the QR code creation interface.

Historical Release Notes 161

July 21, 2016

The Mobile Services July 21, 2016 release includes the following changes:

Improvement

Resource Description

New permission requirement for

Manage App Settings

Changing configuration settings in Manage App Settings now requires Mobile App Admin access from Admin > Groups > Mobile App Admin.

June 16, 2016

The Mobile Services June 16, 2016 release includes the following changes:

Improvement

Resource Description

Messages You can now sort and filter the Messages list.

See

Manage Messages

May 19, 2016

The Mobile Services May 19, 2016 release includes the following enhancement:

Enhancement

• Added Impressions / Engagement Rate for in-app message reporting. Requires version 4.9.0 of the Android or iOS SDK.

The Mobile Services May 5, 2016 release includes the following changes:

New Features

Resource Description

Acquisition tracking enhancements

Create marketing links that send users to download apps from the appropriate app store and to in-app deep links. Marketers can attribute downloads, app relaunches, and other in-app events to these links to understand how to optimize acquisition channels.

Enhancements Include:

Historical Release Notes 162

Resource

Messaging enhancements

Description

• Link Manager: A new interface in the app settings section lets users manage web, app deep, and other link destinations. These destinations can be called in workflows relating to acquisition tracking links and to in-app or push messages.

See

• Marketing Links Builder: A new graphical and intuitive user interface helps users build tracking links. Marketers can choose decisions and destinations that best serve their users.

• Tracking links are created and saved in the UI. Marketers can change link destinations or tracking meta data even after the links are deployed.

• Links can device-detect on OS, OS version, and form-factor.

• Marketers can choose a destination for tracking links that routes users to a fallback destination to preserve the integrity of the landing experience.

• Links can contain token-replaceable parameters.

• Tracking links can contain Adobe-hosted and configurable interstitials.

See

Marketing Links Builder

To see how these features work together, see

Getting Started with Acquisition

Destinations for In-App and Push Messaging

To enhance authoring convenience, marketers can choose a “destination” URL to call a saved web or app deep link from links saved in the Link Manager or they can provide a link in-line.

• Manually enter a custom web link or deep link.

• Choose a stored web or deep link stored in Link Manager.

Push Notifications:

• Custom Push Payload: Marketers can provide a custom push payload in JSON (4KB limit) to be sent to the app via a push or a local notification.

• Category & Sound (iOS only):

Marketers can provide a category and a sound resource for push and local notifications.

See

Experience: Push Message

Marketing Cloud navigation and menu changes

As part of the Adobe Marketing Cloud Spring 2016 release, a new-top level navigation menu displays at the top of all solution interfaces. The new interface lets you:

• Single-click navigation between solutions: Choose your own default landing page or take advantage of the solution-switcher widget.

• Improved notifications: Get notified about events (like posts, mentions, assets shared, system updates) happening across your organization navigation widget.

• Updated Feed: We reimagined the Feed page to become a better platform for cross-channel collaboration between marketers.

Historical Release Notes

Resource

163

Description

See

What's New in the Adobe Marketing Cloud - Spring 2016

in the Marketing Cloud and

Core Services Product Documentation.

February 18, 2016

The Mobile Services February 18, 2016 release includes the following changes:

New Features

Resource Description

Apteligent Integration: Crashes

report

You can view a Crashes report for apps that have been integrated with Apteligent.

See

Crashes

appFigures integration: App

Store Overview report

The user interface for the App Store Overview report has been updated for apps that have been integrated with appFigures.

See

App Store Overview

January 21, 2016

The Mobile Services January 21, 2016 release includes the following changes:

New Features

Resource

Description

The Overview page now displays each user's most recently viewed apps instead of every app for your Analytics company.

See

DPS (Digital Publishing Solution)

Custom Data Content

List variable management and reporting are now supported in Mobile Services.

See

Custom Data Content

October 15, 2015

The Mobile Services October 15, 2015 release includes the following changes:

New Features

Resource Description

Digital Publishing Solution

(DPS) support

Apps created from the Digital Publishing Solution (DPS) have access to the Mobile core service user interface through Analytics Essentials – DPS.

Updated DPS reports for Digital Publishing apps.

See

Historical Release Notes 164

Fixes

• Many fixes around the push messaging feature.

Mobile Services - September 17, 2015

The Mobile Services September 17, 2015 release includes the following changes:

Resource Description

Push Messaging to Analytics

Segments

Sending push messages to Analytics segments from the Mobile Services UI allows you to leverage your robust Analytics data while engaging with users.

See the following topics:

•

Configure Push Messaging

•

Configure App to use APNS or GCM

•

•

Create a push message

Acquisition Tracking

Enhancements

Postbacks

Backdate Session Hits

Create app store links or QR codes that send users to download applications directly from the Apple App Store and Google Play store. The links you create let you attribute downloads and other success events to the acquisition campaign.

Enhancements include:

• Dynamic URLs. Create acquisition links outside of the Mobile Services UI on the fly or create them in the UI with the Acquisition Builder.

• Create one link for Apple app store and Google Play, we’ll do the platform detection and route appropriately.

• Append data to the end of the URL, such as affiliate traffic. You can add data to the URL and we’ll pass it in as context data for you to save off and report on.

• IDFA/AdID support for cross-app campaigns.

See

Configure SDK Analytics Options

Postbacks let you send data collected by the SDK to a separate third-party server. Leveraging the same triggers and traits you use to display an in-app message, you can configure the SDK to send customized data to a third-party destination.

See

Configure Postbacks

Added a check box to enable or disable the ability for the Adobe SDK to backdate session info hits.

See

Mobile Services - June 2015

Feature Access Change

Customers must have Analytics—Mobile Apps or Analytics Premium in order to use the following functionality:

•

In-app Messaging

Historical Release Notes 165

•

Acquisition Campaign Tracking

•

Points of Interest Analytics

Customers with Analytics Standard or other analytics point products (such as SiteCatalyst) will be grand-fathered in to current functionality until renewal.

Analytics core customers will not have this functionality.

Fixes and Enhancements

• Expiration for tracking acquisition campaigns changed from visit to visitor for all customers. This change facilitates campaign attribution to post download activity to the visitor for all visits instead of just the first visit.

• Reorganized and improved the following guides:

•

Adobe Mobile Services Users Guide

(this guide)

•

iOS SDK 4.x for Marketing Cloud Solutions Admin Guide

•

Android SDK 4.x for Marketing Cloud Solutions Admin Guide

•

Windows 8.1 Universal App Store SDK 4.x for Marketing Cloud Solutions Admin Guide

Mobile Services - May 21 2015

Feature

Acquisition links

Description

Added desktop browser regional override for acquisition links. This setting lets you select the region-specific app store that you want an acquisition link to direct to when a user clicks the link from a desktop browser.

See

Create an Acquisition Link

Reports PDF/CSV export for Ranked, Trended, Retention, Funnel, Geo Location, and

Sunburst reports. (Public Beta)

Fixes:

• Resolved issue for some IMS users redirecting from marketing.adobe.com

not seeing any apps in mobilemarketing.adobe.com

• Added custom calendar support in Retention for 4-5-4 and 4-4-5 (custom and retail).

Mobile Services SDK Updates - April 29 2015

Update Description

iOS SDK Version 4.5

Starting in iOS SDK version 4.5, a new iOS extension lets you collect usage data from your

Apple Watch Apps, Today Widgets, Photo Editing widgets, and all the other iOS extension apps.

See

iOS Extension Implementation

in the

iOS SDK 4.x for Marketing Cloud Solutions

guide.

Android SDK Version 4.5

Starting in Android SDK version 4.5, a new Android extension lets you collect data from your Android Wearable app.

See

Android Wearable Implementation

in the

Android SDK 4.x for Marketing Solutions

guide.

Historical Release Notes 166

Mobile Services Maintenance Release - April 16 2015

• We updated our initial loading of Analytics apps to improve the speed of the login process.

• Using the Provide Feedback tool to submit issues of type Bug now submits those issues directly to Customer Care and creates a ticket. Customer Care should contact you soon thereafter.

• When creating an in-app message, you can now target the message using Lifetime Value or Locale.

• On Manage App Settings, under App SDK Downloads, we added links for Unity, Xamarin, and Phonegap.

• You can now link an Adobe Target company to your IMS organization for the length of your Mobile session.

• Updated the Customer Care link under Provide Feedback for Question to be correct for certain locales.

Mobile Services - March 19 2015

Feature

Mobile App Admin group

Description

Managing Acquisition and In-App Messages are now accessible only to users within the Mobile App Admin group managed through reports & analytics. This allows companies to manage who has access to these resources.

See

Mobile App Administrator

Multiple company switching in

Account Settings.

When you log in to Mobile Services using your Adobe ID, if you have multiple Analytics companies, you can switch between them in Mobile Services.

To change companies, click your user icon in the top right of the header.

Fixes:

• Fixed an issue with the funnel image. If no data was present for the specific audience, but there was data for All Users, the All

Users line would be a flat line rather than a funnel. Also improved spacing on this image.

• Fixed no or partial loading of apps when the company contained a large (100+) number of apps with large data sets.

Mobile Services Maintenance Release - February 19 2015

Fixes:

• Restored the In-App Messaging Names report (which was removed in January) to the main menu.

• The Acquisition > Overview main chart title is now Top Campaigns rather than Key Performance Indicators. This change better describes the type of information being displayed.

• Fixed an issue where using Location filters on the funnel chart caused the map to display, rather than a funnel.

• Updated the Retention Report to support the modified Gregorian calendar so that correct weekly values are returned.

• Fixed issue causing titles on In-App Messaging Overview cards to display non-localized titles.

• Improved the styling of Target Experience interface.

• Updated device names to be localized. For example, in en-US, iPhone7,1 will now display as iPhone 6 Plus.

• Fixed certain apps' pathing reports showing "undefined" on steps.

• Upon receiving a CSRF token error, rather than displaying an error message, the system now automatically logs you out and requires you to re-authenticate to restore the session.

Mobile Services Maintenance Release - January 15 2015

Feature Description

Funnel Report Usage > Funnel

Historical Release Notes 167

Feature

Retention Report (Formerly First

Launch Cohort)

Description

In Analytics, funnel reports you identify where customers abandon a marketing campaign or divert from a defined conversion path while interacting with your website or cross-channel campaign.

By default, the Funnel Report is empty. Click Customize to begin using standard metrics and filters.

In the Funnel Report, you can specify funnel steps (any variable or metric) and funnel comparisons (also any variable or metric). Each step shows falloff and conversion from the previous step. The comparison allows you to compare different filters (segments) per step.

Usage > Retention

The First Launch Cohort Report is now called Retention. This report allows reporting of feature retention. This report has been expanded to report on other events, such as social sharing cohorts, purchaser cohorts, and widget user cohorts. You also have more control over the date range.

For example, social sharers retained for N days tells product managers and developers how well new features are retaining users within the new feature set. This answers the question, "Do social sharers continue to share or do they stop after 1 week?"

You can also see a distribution in days for feature retention instead of a retention on a daily basis. For example, a distribution would show for the selected date range 30% of users retained 1 day, 25% retained 2 days, and 15% of users retained 3 days.

Fixes

• Fixed an issue causing segments to be ignored as filters on the Cohorts report.

• Fixed an issue preventing Target reports from displaying when zero is the conversion rate.

• Updated the visual preview for local notifications for in-app messages.

• Updated localized names for the latest iOS devices.

• Changed the icon for the Archive Selected option, to avoid confusion.

• Added a prompt to let you either append or replace when importing the CSV for Points of Interest.

Mobile Services Maintenance Release - November 13 2014

Fixes:

• Fixed garbled text for Japanese characters in Sticky Filter.

• Fixed an issue causing the Last Updated text (in Manage Apps) to always display today.

• Fix an issue causing the in-app message preview to disappear in some European locales.

• Login fields are no longer auto-corrected on iOS devices.

Mobile Services Fall 2014

Release date: October 15 2014

Historical Release Notes 168

Feature

In-App Messaging

Description

You can create, manage, and report on in-app messages, which are delivered to users in real-time, based on their actions and traits.

App Messaging Reports Messaging Performance Metrics: See cross-app promotion, total users, number of views, and click-throughs. You can run a report on any activated message. A KPI table is available to see what's important in your app messaging.

In-App Messaging Names: A ranked report of your most popular messages by Users, Message

Views, and Message Click-Throughs. If your message has never been shown, it does not show up in the list.

The baseline tracking for messages is built-in. If a message was shown, and the user dismissed it or clicked-through, Analytics collects that data automatically.

This report is populated based on a ranked list of in-app message names. The names are a classification of the message ID. If you change the message name, the data is updated retroactively. Because this is a classification report, it can take several hours for an updated message name to be reflected in the report.

Dynamic updates to the remote

Points of Interest list.

Using SDK 4.2, you no longer need to submit an app update to the store to update your points of interest.

On the Manage Points of Interest page, clicking Save packages any changes to the Point of

Interest list, then updates the configuration file in (App SDK Downloads) for the live app.

Saving also updates the list of points in your app on the user devices, as long as the app uses the updated SDK and configuration with a remote points-of-interest URL.

SDK 4.2 Documentation

•

iOS

•

Android

Fixes

• Fixed delete error on the App Overview page, which affected the ability to delete an app.

• Renamed Title to Subject on the Feedback page.

• Fixed an issue preventing the config file from being readable when packaged with the SDK.

• Fixed an issue causing overview KPI sparkline/totals to show up as blank cards.

• Product is now localized after changing the language.

• Fixed an issue preventing friendly names from displaying for Action Instances.

See

What's New in Mobile

for more information.

Mobile 2.0 Maintenance Release - September 18 2014

• Fixed an issue preventing customers with thousands of report suites to successfully log in.

• Updated help links to point to

https://marketing.adobe.com/resources/help/en_US/mobile/

• Minor change to background image displayed on login page.

• Fixed display of error tool tips on the Send Feedback dialog.

Historical Release Notes 169

Mobile 2.0 Maintenance Release - August 21 2014

• The Mobile help landing is now at:

https://marketing.adobe.com/resources/help/en_US/mobile/

Please update your bookmarks.

• Updated interface colors to increase contrast for accessibility.

• Added the ability to create offline-enabled report suites. Meaning, if you copy from an offline-enabled (time-stamped) report suite, the new report suite is offline-enabled. The Mobile App Template is offline-enabled as well.

• Log improvements: The logs now show that report suites with mobile application reporting enabled are automatically added to Adobe Mobile Services when you log in.

• Fix an issue causing incorrect sorting on trended reports.

• Fixed a layout issue of Manage Points of Interest page on iPads.

• Improved the validation of acquisition links to prevent links from failing to show a status of Ready.

• Fixed an issue preventing tracking codes from showing up in Analytics. This fix automatically populates s.campaign with acquisition tracking codes

• Fixed an issue preventing list variables from being copied when creating a new report suite.

• Fixed a search issue for Organizations in the User Account dialog box.

• Improved automatic Chinese detection in Internet Explorer for Windows 8 and 8.1.

• Mobile now does not allow you to disable eVars when there are custom processing rules that rely on the eVars.

• Fixed a scrolling issue in the store app search list in Internet Explorer.

• Fixed an issue causing Chinese and Korean characters to truncate in Internet Explorer.

• Fixed a sorting issue in the Cohorts Report.

• Fixed an issue causing spaces to be encoded as plus signs (+) in acquisition links.

• Fixed phantom clicks occurring on iPads

• Fixed minor display and behavior issues in the Notifications list.

Mobile 2.0 - Maintenance Release - July 17 2014

New features and fixes for July 17, 2014 primarily include menu streamlining and the combining of various reports into Overview reports. The new Standard Variables and Metrics page is available for mapping in Custom Data Content.

Feature Description

New All Apps menu The App Selector menu now has an item called All Apps. The selector also lets you type to easily search for applications.

Historical Release Notes 170

Feature

New Manage App Settings menu.

Description

The Settings menu is now called Manage App Settings. It has been reorganized and streamlined, along with Usage, Acquisition, and Location submenus.

All Apps Overview

When you click All Apps, the menu options are:

• Overview: Displays a report for key metrics for each your apps. This Overview report is one of several new Overview reports available in this release.

• Manage Apps: Displays the Manage Apps page.

• Manage Target Activities: Lets you log into your Target account and create Adobe Target activities.

Overview reports In addition to menu streamlining and organization changes, many reports have been combined into Overview reports.

For example, reports for countries, regions, and cities have been combined into a Location >

Overview report, which displays a sunburst visualization and breakdowns for Countries, Regions, and so on.

Changes to App Information The App Information page previously in Settings > About <app name> is now in accessed by clicking Manage App Settings in your app.

Child pages in your app are now accessible from the top of the App Information page. These pages have been renamed as follows:

• Custom Data Content is now Manage Variables & Metrics. (New feature. See Standard Variables

& Metrics below for more information.)

Historical Release Notes 171

Feature Description

• Acquisition Links is now Manage Acquisition Links.

• Points of Interest is now Mange Points of Interest.

Manage App Settings >

Manage Variables & Metrics

The former Custom Data Content page (now called Manage Variables & Metrics) has been expanded to include three tabs for context data mapping:

• Standard Variables & Metrics: (New) Lets you specify context data mapping for standard purchase variables and metrics (shopping cart and purchase activities). You can also enable or disable whether the variables and metrics are visible in Mobile Services.

• Custom Variables: Lets you map Analytics properties to a text value, and the context data variable that you would like mapped. (Not new functionality.)

• Custom Metrics: Lets you select the context data metric event that you would like mapped.

(Now new functionality.)

Usage > Action Paths The ranked Actions report now displays pathing information. (Click Customize to display a ranked report.)

French, Chinese, German, Korean, Spanish, and Portuguese are now supported.

Language support

Improvements and Fixes

• When you create a report suite, the company prefix is now displayed automatically on in the Report Suite ID field. This improvement removes the need for you to enter the ID, and reduces the potential of having double prefixes added to report suites.

• You can now copy acquisition links on iOS devices.

• Bulk uploading is no longer supported on Safari 5 and IE 9 and older.

• Added the option to cancel actions to most settings pages.

• Renamed Location Map report to Map.

• Zip Code is no longer shown by default in the menu, and is no longer shown as a map when you run through Customize panel.

• Made the details labels more clear (More Details | Fewer Details).

• Improved the appearance of reports when using the browser's print functions.

• Improved compatibility with password managers.

• Show modified or created by information on the Acquisition Links page.

• Improved messaging when switching to an app that does not support the current report.

• Fixed a JavaScript error on the Custom Data Content page.

• Fixed "undefined" being briefly shown on page titles when the page was loading.

• Fixed an error when part of a multi-ranked report has no data.

• Fixed validation messages and interface cleanup on the Points of Interest page.

• Fixed an error occurring when saving custom data content.

• Fixed a freeze issue in Firefox occurring on the Points of Interest page.

• Fixed an issue that was preventing the correct currency symbol from being used on the All Apps overview.

• Fixed an issue occurring in the total for the Instances metric on ranked reports.

• Fixed improper pop-up occurring when canceling from the Manage App Settings page.

• Fixed an issue occurring when switching from pathing to ranked reports in the Customize panel.

• Fixed a bug on the Delete Selected button on the Manage Apps page.

• Fixed key metrics not being saved properly.

Historical Release Notes 172

Mobile 2.0 - April 17 2014

New features and fixes for April 17, 2014.

Feature Description

App Acquisition Analytics You can create app store links that allow users to download applications directly from the Apple App Store and Google Play. The links you create enable you to attribute your success events to the downloads.

See