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.
Good to know: This page is about the Actions-framework Airship Segment destination. There’s also a page about the non-Actions Airship destination. Both of these destinations receive data from Segment.
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.
- 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
- From the Segment web app, navigate to Connections > Catalog, and select the Destinations tab in the catalog.
- Search for Airship (Actions) and select it.
- Click Configure Airship (Actions).
- Select an existing Source to connect to Airship (Actions).
- Name the destination and choose between filling in the settings manually or copying from an existing instance.
- Click Create Destination.
- 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.
- Select the appropriate data center.
Destination Settings
Setting | Description |
---|---|
Access Token | Required. Create in the Airship Go dashboard in Settings->Partner Integrations->Segment |
App Key | Required. The App Key identifies the Airship Project to which API requests are made. |
Data Center | Required. US or EU |
Available Presets
Airship (Actions) has the following presets:
Preset Name | Trigger | Default Action |
---|---|---|
Custom Events | Event type = "track" |
Custom Events |
Set Attributes | Event type = "identify" |
Set Attributes |
Available Actions
Build your own Mappings! Combine supported triggers with the following Airship-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Custom Events
Set Custom Events on Users
Custom Events is a Cloud action. The default Trigger is: type = "track"
Field | Description |
---|---|
Airship Named User ID* | Type: STRING The identifier assigned in Airship as the Named User |
Name* | Type: STRING Event Name |
Occurred* | Type: DATETIME When the event occurred. |
Event Properties | Type: OBJECT Properties of the event |
Batch Data to Airship | Type: BOOLEAN If true, Segment will batch events before sending to Airship. Limit 100 events per request. |
Manage Tags
Associate tags with users in your audience for segmentation and automation
Manage Tags is a Cloud action.
Field | Description |
---|---|
Airship Named User ID* | Type: STRING The identifier assigned in Airship as the Named User |
Tag Name | Type: OBJECT Tag name to add or remove. Values for each tag should be boolean only. A true value creates a tag, a false value removes a tag. Non-boolean values will be ignored. |
Tag Group* | Type: STRING The Tag Group to sync your tags to. This defaults to |
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"
Field | Description |
---|---|
Airship Named User ID* | Type: STRING The identifier assigned in Airship as the Named User |
Occurred* | Type: DATETIME When the Trait was set |
Attributes | Type: OBJECT User Attributes. Attributes should exist in Airship in order to be set, including the predifined ones defaulted here. |
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.
This page was last modified: 29 Jun 2023
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!