Airship integration with AppsFlyer

At a glance: Airship, an AppsFlyer integrated partner, provides the world’s leading mobile engagement platform, helping thousands of businesses of all sizes form a direct and lasting connection with their customers. With Airship, companies gain total control of their mobile footprint — apps, wallets and user-level data — to deliver experiences that get noticed and drive action across mobile or any other customer touch-point.


Some media sources restrict sharing data with 3rd parties. AppsFlyer cannot share user level data of users acquired through these media sources with 3rd party platforms or services. All installs from such media sources are therefore sent as organic.

For more details and a list of media sources that restrict sharing data with 3rd parties, click here.

Configuring Airship

Go to the dashboard of your app and click on Integrated Partners on the left bar.

Enter "Airship" in the search field and click on its logo to open Airship's configuration window.

Airship's configuration window only makes use of the Integration tab.

For a detailed description of the Partner Configuration Window Header, click here.

Integration tab

The Integration Tab is divided into different sections as described below.

Activate partner

On the first visit here, you will need to toggle below. ON the Activate Partner button to enable setup of the integration tab's parameters. The toggle MUST be ON for as long as you work with the partner.
For more details about partner activation please click here.

General settings

Airship connects with AppsFlyer via a unique App Key and Token. If you don't already have them, you can obtain it from Airship to continue with the integration, or see below for instructions how to obtain it.


To configure the integration with Airship:

Minimum requirements - AppsFlyer SDK:

  • Android – version and above
  • iOS – version 3.3.3 and above
  1. Integrating with Airship requires that the channelid (Airship's unique user identifier) is populated in AppsFlyer's SDK. This parameter is sent with every postback and enables the identification of each user. To perform this you must insert the following strings to your app code:

     Important Note

    Make sure the lines of code are inserted in the correct place – after Airship SDK is launched and before the appsflyer.sendtracking (Android) / trackAppLaunch (iOS) methods are called.

    HashMap<String, Object> customData = new HashMap<String,Object>();
    String channelId = UAirship.shared().getPushManager().getChannelId();
    customData.put("android_channel", channelId);
  2. Get the App Key and Token parameters from Airship:
    1. Login to your Airship account at:
    2. On the left menu, go to Settings > APIs & Integrations and click Tokens.
    3. Click Create Token.
    4. Enter token name and select role.
    5. Click Create token.


Default postbacks

AppsFlyer can send automatic postbacks to Airship following user installs and re-engagements. Use this section to define the source of the users that allow sending these postbacks.


Select Events attributed to any partner or organic to send postbacks for any user that downloads the app to Airship.

Once you have saved the configuration, AppsFlyer sends the following data to Airship for every organic and non-organic install:

    • Device ID (IDFA / Google Advertising ID)
    • Media Source
    • Campaign name

Attribution link tab

Attribution Links are not available for Airship.

Cost tab

Cost data is not supported in the integration with this partner.

Ad revenue tab

Ad Revenue is not supported in the integration with this partner.

Permissions tab

Permissions are not available for Airship.

Set up and manage the attribution data in Airship console

In Airship, attributes are key-value pairs that you associate with your audience to help better target them with messages. Use attributes to target audiences with greater specificity than you would with tags.

Configure your AppsFlyer attribution data in Airship by adding individual attributes to your project.


Was this article helpful?