Adobe Analytics


This integration is maintained by Airship. Please contact Airship for support.


Adobe Analytics provides behavioral analytics and content performance measurement for websites and mobile apps. Airship Real-Time Data StreamingA service that delivers engagement events in real time via the Data Streaming API or an Airship partner integration. (RTDS) provides a live view into your application, adding the “messaging perspective” to your Adobe Analytics information. This integration enables a complete view of the user experience by combining Adobe Analytics data with user-specific interactions such as push sends, direct and indirect opens, and uninstalls.

Additionally, Airship augments Adobe’s device reporting with information on in-app behavior defined by the Airship SDK. Airship events can tell you when a Message Center message was delivered, read, and deleted. They can also describe what happened to an in-app notification — whether it was displayed or expired, and what happened to it after it was displayed. Did the user dismiss it, interact with it, or allow it to resolve itself?

There are three major steps to setting up this integration. You will need help from your developers (iOS and Android) and your Adobe Analytics and Airship administrators to:

  1. Add client code (Developers) — This code associates the user IDs between the two systems, tying events captured from the Airship SDK to events captured from the Adobe Analytics SDK.
  2. Configure an outbound integration for Adobe Analytics (Airship administrator) — The RTDS integration sends Airship events to an Adobe Analytics report suite.
  3. Set up Adobe Analytics processing rules (Adobe Analytics administrator) — These rules map Airship events to your Adobe variables and events.

Adobe Analytics Integration Requirements

This integration requires these accounts:

  1. Adobe Analytics
  2. Airship — Must include both:

Adding Client Code

Fetch the Adobe Analytics visitor ID for your user, then associate it with the Airship Channel IDAn Airship-specific unique identifier used to address a channel instance, e.g., a smartphone, web browser, email address.. See: Custom Identifiers.

Setting custom identifiers

// Get the Adobe visitor ID
let visitorID = ADBMobile.visitorMarketingCloudID()

// Add the visitor ID to the current associated identifiers
let identifiers =
identifiers.set(identifier: visitorID, key:"AA_visitorID")

// Associate the identifiers
// Get the Adobe visitor ID
NSString *visitorID = [ADBMobile visitorMarketingCloudID];

// Add the visitor ID to the current associated identifiers
UAAssociatedIdentifiers *identifiers = [ currentAssociatedDeviceIdentifiers];
[identifiers setIdentifier:visitorID forKey:@"AA_visitorID"];

// Associate the identifiers
[ associateDeviceIdentifiers:identifiers];
// Get the Adobe visitor ID
String visitorId = Visitor.getMarketingCloudId();

// Add the visitor ID to the current associated identifiers
    .addIdentifier("AA_visitorID", visitorId)

Once set, all associated identifiers are returned in RTDS under the "identifiers" key:

   "ios_channel": "a6b392d6-3b0d-4c00-98ef-5cb91d51268a",
   "named_user_id": "albert",
   "identifiers": {
     "foo": "bar",
     "verycustomid": "123554"
   "attributes": {
     "package_name": "com.company_name.app_name",
     "version": "1.0.0",
     "ua_library": "7.0.2"

See also: RTDS API: Device Information.

Configuring the Outbound Integration


Airship sends events to Adobe with timestamps. If your Adobe Analytics Report Suite has timestamps disabled, Adobe will drop Airship events. See Timestamps Optional for more information.

You will need your Adobe Analytics Report Suite ID and Tracking Server URL. If you do not have these, contact your iOS or Android developer.

In Airship:

  1. Go to Settings.
  2. Under Project Configuration, select Manage for Partner Integrations.
  3. Select Adobe Analytics.
  4. Select Configure for the outbound integration and follow the onscreen instructions to:
    • Enter your Report Suite ID
    • Enter your Tracking Server URL
    • Select the Airship events to send to your Report Suite

After configuring your app and your integration, you can create event-based Segments in Adobe Analytics. See Recommended Attribute Mapping for recommended mapping of Data Streaming events to Adobe Analytics events.

Recommended Property Mapping


If you set up your integration before March 11, 2020, your event fields will not belong to a global airship object. You must create a new integration to use the airship. namespace.

In Adobe Analytics, you capture the data that is valuable to you using context data and processing rules. Airship uses Adobe’s Data Insertion API to send data to Adobe Analytics. Airship uses the contextData field so that you can include every piece of relevant data from an Airship event without consuming the limited number of variables and properties that Adobe Analytics supports.

You can set the Adobe Analytics processing rules so that every field in an Airship event maps to an Adobe Analytics concept. After your Adobe Analytics administrator sets up your processing rules, you can view Airship event data in your Adobe Analytics dashboard.

We derive contextData keys from the original Data Streaming events using JSON notation, and use airship to represent the global parent for all Airship event properties. For example, this is the push identifier of a notification that caused an event:

   "body": {
      "triggering_push": {
         "push_id": "d99bd842-f816-4560-bc59-b057f7c0e164"

This field would be available for mapping as airship.body.triggering_push.push_id. When mapped to an sProp, eVar, event, or other Adobe Analytics concept, the variable’s value would be d99bd842-f816-4560-bc59-b057f7c0e164.


The above JSON represents a partial event object. Actual JSON objects coming from the Real-Time Data Streaming API are more complex.

To see all the available fields, read the Data Streaming API Reference.

Setting Up Adobe Analytics Processing Rules

You or your Adobe administrator must set up processing rules in the Adobe Analytics Admin Console to enable Adobe Analytics to capture events from Airship. These processing rules assign contextData variables to Adobe Analytics variables or increment events (counters) accordingly.

  1. In the Adobe Analytics interface, select Admin Console and navigate to Report Suites.

  2. Select the Report Suite that Airship is sending data to, and then go to Edit Settings, then General, then Processing Rules.

  3. Select Add Rule.

  4. Enter a title for the rule. For example, “Airship to Adobe Analytics Integration.”

  5. Select Add Action.

  6. If you need to setup an sProp or eVar to capture a dimension (e.g., Event Type), select Overwrite Value Of and then select the sProp or eVar that you want to set. After the With label, select the contextData variable that you want to set the sProp or eVar with.

  7. If you need to set up an Event to capture the number of times something occurred, e.g., the number of Opens, select Set Event and then select the Adobe Analytics Event you want to set. Select Custom Value and set the value to 1. Then set a condition for when you want to set the event.

    Continuing with the Opens example, you would set up a condition where the If is for the same type contextData variable, and the condition would be equals OPEN. This will increment the Open Event each time the Data Streaming Event Type is set to OPEN.

This is just one example of how you can set up a variable and an event. The same concept applies for each Airship event type and dimension that you want to capture in Adobe.

Below are some recommendations on different ways that you can get started mapping the Airship concepts to Adobe Analytics concepts.

This table provides example contextData variable keys and the recommended Adobe Analytics variable type to capture information from incoming Airship event information. See our Real-Time Data Streaming documentation for information on events and fields that aren’t listed below. Use JSON object notation to reach nested properties (in the format In Adobe analytics, all variables are preceded by airship..

Airship ConceptRecommended Adobe Analytics Mapping ContextData Variable
Data Streaming event type (e.g., send, direct open, indirect open)Custom event (one for each type), and an sProp for segmentation (all the people who received a message, or opened, etc.)type
Unique push id, group id, or varianteVarairship.body.push_id, airship.body.group_id, airship.body.variant, airship.body.triggering_push.push_id, airship.body.triggering_push.group_id, airship.body.triggering_push.variant, airship.body.last_delivered.push_id, airship.body.last_delivered.group_id, airship.body.last_delivered.variant, airship.body.replacing_push.push_id, airship.body.replacing_push.group_id, airship.body.replacing_push.variant
Device Identifiers (e.g., named user, Airship channel ID)eVarairship.device.ios_channel, airship.device.android_channel, airship.device.named_user,
In-App Message Resolution TypesProp AND eVarairship.body.type
In-App Message Expiration TypesProp AND eVarairship.body.type (and type is IN_APP_MESSAGE_EXPIRATION)
In-App Message Button identifierssPropairship.body.button_id, button.button_description
Adobe visitorId (via associated identifiers)eVarairship.device.identifiers.AA_visitorID
Other Data Streaming informationVariesYou can determine what the context variable name will be based on the Data Streaming event data. Inner properties are joined with outer properties via a period.

contextData can take a long time to appear in the Adobe Analytics dashboard. Please allow at least one hour before contacting Airship Support.


Known issue: If no processing rules have been defined, no contextData variables will be available for mapping.

As a workaround until Adobe Analytics fixes this issue, add a trivial rule that does nothing, then proceed establishing your mapping as normal.

Sample Data Sent to Adobe

<?xml version="1.0"?>