Airship (Actions) Destination

Airship provides an end-to-end solution for capturing value across the entire customer app lifecycle — from acquisition and activation to engagement and loyalty. It starts with Airship’s market-leading app store optimization (ASO) solutions promoting app discovery and downloads. Then the unified journey orchestration, content creation and experimentation solutions kick in. App teams can quickly design, deploy and iterate no-code native app experiences and cross-channel campaigns — bridging inside-the-app experiences with outside-the-app messaging.

Airship maintains this destination. For any issues with the destination, contact the Airship Support team.

Benefits of Airship (Actions) vs Airship Classic

Airship (Actions) provides the following benefits over the classic Airship destination:

• Flexibility. Complete flexibility for mapping your data from any Segment event type to one of three Airship endpoints. Make optimal use of data from Segment to trigger Automations, audience segmentation, or to personalize end-users in-app experiences and messages.
• Additional functionality. Supports email registration, named user association, as well as delete for GDPR compliance. This is in addition to the previously supported custom events, tag management, and attributes.
• Reporting. Better and more meaningful feedback from the Airship API. This integration calls the Airship API directly, so the endpoint response shows precisely how the integration is performing.

Getting started

1. From the Segment web app, navigate to Connections > Catalog, and select the Destinations tab in the catalog.
2. Search for Airship (Actions) and select it.
3. Click Configure Airship (Actions).
4. Select an existing Source to connect to Airship (Actions).
5. Name the destination and choose between filling in the settings manually or copying from an existing instance.
6. Click Create Destination.
7. Enter your Access Token and App Key. You can get your access token and app key by going to your Airship project and navigating to Settings > Partner Integrations and selecting Segment. Following the instructions there will create a Tag Group, Attributes, and provide the Access Token and App Key.
8. Select the appropriate data center.

Destination Settings

Available Presets

Airship (Actions) has the following presets:

Available Actions

Build your own Mappings. Combine supported triggers with the following Airship-supported actions:

• Custom Events

• Manage Tags

• Set Attributes

• Register And Associate

Custom Events

Set Custom Events on Users

Custom Events is a Cloud action. The default Trigger is: type = "track"

Click to show / hide fields

Manage Tags

Associate tags with users in your audience for segmentation and automation

Manage Tags is a Cloud action.

Click to show / hide fields

Set Attributes

Set user attributes in Airship with data from Segment. Some common user attributes are predefined in the attributes field, however note that all must be created in Airship before use. More information here: https://docs.airship.com/guides/messaging/user-guide/audience/segmentation/attributes/project/#adding-attributes

Set Attributes is a Cloud action. The default Trigger is: type = "identify"

Click to show / hide fields

Register And Associate

Register an Email address or SMS number and associate it with a Named User ID.

Register And Associate is a Cloud action. The default Trigger is: type = "track" and event="Address Registered"

Click to show / hide fields

Named User ID

Named User is an Airship concept for identifying users and associating them with devices and delivery addresses. For more information, see Airship | Named Users. This integration does not perform the association of a Named User to a delivery address, configure that in either the mobile/web SDK or through a custom workflow out of band from this integration.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.