Airship helps you drive loyalty, engagement, and revenue in your app and beyond. Airship provides push messaging services, including segmentation and targeting capabilities.
For more information about Airship’s implementations, see Airship’s Getting Started Guide.
mParticle supports two methods for sending event data to Airship:
mParticle’s client-side Kit integrations for iOS and Android were built in partnership with Airship and support the full feature-set of the Airship platform. The integration will bundle Airship’s native SDK as an add on to the mParticle core SDKs, and as with all integrations allows for server-side dynamic enable/disable, configuration, and filtering.
The Kit integrations perform the following automatically by mapping mParticle’s APIs onto the analogous Airship APIs:
The source code to each kit is available if you would like to learn exactly how the above mappings occur:
The features above can be leveraged entirely via mParticle’s APIs. All other features of the Airship SDK, such as the message-center, are still supported by the kit integration by making direct API calls to the Airship SDK.
This step will add the mParticle SDK (if not present already), the Airship SDK, along with the Airship kit, which acts as a bridge between the two SDKs. See the Cocoapods and Gradle examples below, and reference the Apple SDK and Android SDK GitHub pages to learn more about kits.
target '<Your Target>' do
pod 'mParticle-UrbanAirship', '~> 6'
//add the Urban Airship Kit to your app's dependencies
In the Airship platform:
Create a new app if necessary, or use an existing app.
Note: Part of Airship’s wizard for setting up a new app involves sending a test message to your app. This process assumes you are using the regular Airship SDK instead of mParticle. You will not receive a test message in your app at this stage but, in order to proceed with setting up your app, you need to ‘confirm’ that you received the test push notification, when asked by the setup wizard.
For an in-depth definitions of App Keys and Security, see Airship’s App Keys & Security: Security topic.
The steps accomplish the equivalent of Airship’s quickstart guide - after this you’ll be setup to track session, events, and much more!
As long as the Airship Kit is included in your app, mParticle will pass any Push Notifications from Airship to the kit for display. However, you will need to provide credentials in the Airship dashboard.
See the main Push Notification documentation for more detail for the various platforms:
For Android push notifications you will need to provide your Server Key to Airship. See Airship’s Android Push Notifications documentation for more information.
For iOS push notifications you will need to upload your APNs Push SSL certificate to Airship. See the Airship’s iOS Push Notifications documentation for more information.
In case you’re integrating with Airship and need to implement a Service Extension for user notifications, please refer to this Airship’s Extension’s Documentation.
Airship tags can be used to easily group your users. Use them to track categories of interest, preferences, user behaviors and more. Each device can have multiple tags, and each tag can represent millions of devices.
mParticle has directly analogous user attribute and tag APIs, which mParticle’s kit integration maps onto Airship’s tag APIs. If there are some attributes that you would not like to map as tags, you may filter them individually via mParticle’s data filtering.
The mParticle kit integration can automatically set Airship tags when particular events and/or event attributes are detected. When enabling and configuring Airship, you may select the events that you’ve sent to mParticle in the past, and customize exactly which tag(s) those events should trigger. In the screenshot below, when an event named “Map View” is fired, mParticle will set the tag “my tag” within the Airship platform and when an event attributed named “Transaction Id” is seen, mParticle will set the tag “transaction”.
The S2S integration will forward Commerce, and Custom event types captured through the mParticle web SDK to Airship and allows for server-side dynamic enable/disable, configuration, and filtering.
The S2S integration will not create users in Airship. When data is sent to Airship without a known Named User you will not see these events or users in your Airship account.
Event Filters in mParticle will show all events supported between kit and S2S integrations. Because the S2S integration sends a subset of these events, only filters set on S2S-supported events will affect the forwarded data.
To configure an S2S integration, simply configure the connection according to the settings below.
Mapping of mParticle events to Airship events occurs automatically in both kit and S2S implementations. mParticle eCommerce events are mapped to Airship events as follows:
|mParticle Product Action Event
|Airship Mapped Name
|Add To Cart
|Add to Wishlist
If your Airship configuration uses the same App Key for Mobile and Web, all 3 configuration settings are required.
If your Airship configuration is for Web only, enter an App Key, and enable the
This App Key is for Web only in my Airship Setup. setting.
|Airship generated string identifying the app setup. Used in the application bundle.
|Airship generated string identifying the app setup secret. Used in the application bundle, and only used for Mobile configurations.
|The Airship site your credentials belong to, either ‘US’ or ‘EU’.
|App Key is for Web
|If enabled, this configuration will only be used for Web configurations.
|Airship generated string identifying the Bearer token.
|Notification Icon Name
|Name of the drawable resource to use for the notification icon, for example, ic_notification.
|Notification Accent Color
|Accent color to be used when constructing the notification, for example, #ff0000.
|Named User ID Type
|Set to “None,” “Other,” “Hashed e-mail address,” or “Customer ID” to define which identity to send to Airship. If a request does not include the Named User ID Type it will be dropped. Airship will return an error if ‘Other’ is selected but the ‘Other’ identity is not present in the event batch
|Event Names that map to User Tags
|Define the mapping of mParticle event names to the corresponding Airship tags.
|Event Attributes that map to User Tags
|Define the mapping of mParticle event attributes to the corresponding Airship tags.
|If enabled, tags will be sent to Airship.
|Send all user attributes as tags
|If enabled, all user tags and user attributes will be forwarded to Airship as tags. If not enabled, only user tags will be forwarded to Airship. This setting is dependent on the value of the ‘Enable Tags’ setting.
Was this page helpful?