Airship is an app experience platform that lets you create and deliver powerful in-app experiences with the help of engaging, personalized content and actionable customer insights.
RudderStack supports Airship as a destination to which you can seamlessly send your event data.
Find the open source transformer code for this destination in the GitHub repository.
You must install the Airship SDK on your website/app to use this integration successfully. See the Airship documentation for more information on setting up the Airship SDK on your preferred platform.
Also, note that:
Before sending events to Airship through RudderStack, make sure to first create the channel and named user in Airship via the Airship SDK.
RudderStack supports enhancing the existing user profiles and sending custom events in cloud mode.
Once you have confirmed that the source platform supports sending events to Airship, follow these steps:
From your RudderStack dashboard, add the source. Then, from the list of destinations, select Airship.
Assign a name to your destination and click Next.
Connection settings
To successfully configure Airship as a destination, you will need to configure the following settings:
API Key: Enter your Airship token which is required by RudderStack to communicate with your Airship project and authenticate all supported event calls, that is, identify, track, and group.
App Key: Enter your Airship project’s app key which RudderStack requires for the track calls. You can obtain the app key by going to Settings > Project Details in your Airship dashboard.
EU data center: Turn on this setting if you’ve implemented your app in Airship’s European data center. If you’re unsure which data center you are on, reach out to Airship support.
Consent management settings: Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. See Consent Management in RudderStack for more information on this feature.
Identify
The identify call lets you uniquely identify a user and record any associated traits about them like their name, email, etc.
In the above code snippet, RudderStack sends the Boolean values to Airship as tags, whereas the non-Boolean values are sent as attributes.
RudderStack maps some reserved traits to the predefined Airship attributes. See the Traits mapping section below for more information.
Tags
To successfully assign tags to Airship using the RudderStack identify events, you must create a tag group with the group key set to rudderstack_integration in Airship.
Note that this integration supports identify traits of Boolean data type only. Airship adds tags for the traits that are set to true and removes tags for the traits set to false.
Attributes
For identify traits that are not mapped to any predefined or custom-defined Airship attributes, you must create and enable those attributes in the Airship dashboard.
Track
The track call lets you capture user events along with the properties associated with them.
RudderStack sends the track events to Airship via their Custom Events API. You can use the event properties to personalize and trigger specific messages for your audience.
You need the Airship project’s App Key for authenticating the track calls.
A sample track call is shown below:
rudderanalytics.track("Product Clicked",{description:"Shoes viewed",brand:"Sneakers",colors:["red","blue"],items:[{text:"New Balance Sneakers",price:"$69.95"},{text:"G.I. Joe Sneakers",price:"$99.95"}]});
In the above snippet, the event name Product Clicked is automatically converted to product_clicked before sending to Airship.
The event name sent to Airship must not contain any upper case characters. Otherwise, Airship rejects it with a 400 status code.
RudderStack handles this scenario internally by converting any upper case characters to lower case and replacing any spaces with an underscore(_).
RudderStack also maps some event properties to the Airship properties before sending them over to Airship. See the Supported mappings section below for more information.
Group
The group call lets you link an identified user with a group such as a company, organization, or an account, and record any traits associated with that group, e.g., company name, number of employees, etc.
In the above code snippet, RudderStack sends the Boolean values to Airship as tags and the non-Boolean values as attributes.
To successfully assign tags to Airship using the RudderStack group events, you must create a tag group with the group key set to rudderstack_integration_group in Airship. Similarly, you need to create the relevant attribute identifiers in Airship to set the attributes for the named users.
This integration supports group traits of type Boolean only. Airship adds tags for the traits that are set to true and removes tags for the traits set to false.
Supported mappings
RudderStack maps the following event properties to the Airship properties before sending them over to Airship.
See the Airship documentation for more information on how the externally-generated custom events are mapped.
RudderStack property
Airship property
userId Required
named_user_id
event Required
name
properties
properties
value
value
interactionId
interaction_id
interactionType
interaction_type
sessionId
session_id
Note: RudderStack transforms this field based on the UUID v5 format using DNS as the reference namespace.
transaction
transaction
timestamp
occurred
Traits mapping
RudderStack trait
Airship attribute
address.city
city
address.country
country
address.postalcode
zipcode
address.state
region
createdAt
account_creation
firstName
first_name
lastName
last_name
name
full_name
phone
mobile_phone
FAQ
Where can I find the Airship API key?
RudderStack requires the Airship API key to communicate with your Airship project. This is a mandatory field to set up the integration.
In your Airship dashboard, go to Settings.
In the Project configuration window, go to Tokens and click Manage.
Click Create token.
Assign a name for your token. Under Role, select All access from the dropdown:
Once the token is created, copy and secure the credentials and click Got it.
Where can I obtain the Airship App Key?
In your Airship dashboard, go to Settings.
In the Project configuration window, look for the Project Details pane on the right side. You will find your project’s app key listed here.
How do I create a custom tag group in Airship?
Go to Settings > Project configuration > Tag Groups and click Manage.
Click Create Tag Group and enter the following settings:
Name: Enter the name for the tag group.
Description: Set additional information about the tag group in this field.
Group Key: Assign a unique ID for the tag group in this field. For example, to assign tags using the RudderStack identify events, you can set this to rudderstack-integration. For assigning tags using the group events, set this to rudderstack-integration-group.
For identify traits that are not mapped to any predefined or custom-defined Airship attributes, you must create and enable those attributes in the Airship dashboard.
Go to your Airship dashboard.
Navigate to Audience > Attributes.
Click Create Attribute.
Enter the Attribute ID, Name, and select the attribute Type.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.