Once set, all associated identifiers are returned in RTDS under the "identifiers" key:
See also: RTDS API: Device Information.
## Configuring the Outbound Integration > **Warning:** Airship sends events to Adobe with timestamps. If your Adobe Analytics Report Suite has timestamps disabled, Adobe will drop Airship events. See [Timestamps Optional](https://docs.adobe.com/content/help/en/analytics/admin/admin-tools/timestamp-optional.html) 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, Android, or Web developer. In Airship: 1. Next to your project name, select the dropdown menu ( ), then **Settings**. 1. Under **Project settings**, select **Partner Integrations**. 1. Select **Adobe Analytics**. 1. 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](#connect-aa-mapping) for recommended mapping of Data Streaming events to Adobe Analytics events. ### Recommended Property Mapping {#connect-aa-mapping} > **Important:** 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](https://helpx.adobe.com/analytics/kb/data-insertion-api-post-method-adobe-analytics.html) 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: ```json { "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`. > **Note:** 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](https://www.airship.com/docs/developer/rest-api/connect/). ## 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**. 1. Select the Report Suite that Airship is sending data to, and then go to **Edit Settings**, then **General**, then **Processing Rules**. 1. Select **Add Rule**. 1. Enter a title for the rule. For example, "Airship to Adobe Analytics Integration." 1. Select **Add Action**. 1. 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. 1. 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. ### Recommended Concept Mappings 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](https://www.airship.com/docs/developer/rest-api/connect/) for information on events and fields that aren't listed below. Use JSON object notation to reach nested properties (in the format `airship.property.sub-property`). In Adobe analytics, all variables are preceded by `airship.`. | Airship Concept | Recommended Adobe Analytics Mapping Context | Data Variable | | --- | --- | --- | | Data Streaming event type (e.g., send, direct open, indirect open, web notification click) | 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 variant | eVar | `airship.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 — mobile (e.g., Named User, Airship Channel ID) | eVar | `airship.device.ios_channel`, `airship.device.android_channel`, `airship.device.named_user`, `airship.device.identifiers.com.urbanairship.idfa` | | Device Identifiers — web (Airship Channel ID) | eVar | `airship.device.channel` | | Web browser context | sProp | `airship.device.attributes.web_browser_name`, `airship.device.attributes.web_browser_type`, `airship.device.attributes.web_browser_version`, `airship.device.attributes.web_user_agent_string` | | In-App Message Resolution Type | sProp AND eVar | `airship.body.type`