Articles in this section

See more

AppsFlyer + Iterable Integration

With the AppsFlyer + Iterable integration, you can send customer data from AppsFlyer to Iterable and use it to include deep links in your campaigns.

In this article

Enabling the integration

In Iterable

  1. Go to Integrations > API Keys.
  2. Click New API Key.
  3. Give your API key a name (for example, "AppsFlyer Integration") and select Server-side.
  4. Click Create.
  5. Copy the API key to your clipboard.

IMPORTANT

Store your API key in a safe location. Once you close this menu, you won't be able to view the full API key again.

In AppsFlyer

  1. Go to Collaborate > Partner Marketplace.

    Navigating to the AppsFlyer Partner Marketplace

  2. Search for "Iterable" and click Manage Integration.

    The Manage Integration button

  3. In the api_key field, enter the Iterable API key you created earlier.

    Entering the API key

  4. Select the events that you’d like to send to Iterable. (This integration currently does not support attribution links or data enrichment features.)

IMPORTANT

You must track user ID values with the AppsFlyer SDK in order to send postbacks from AppsFlyer to Iterable. For postbacks to be successful, the user IDs that you set up in AppsFlyer and Iterable must match. If you haven't set up an AppsFlyer customer user ID (CUID) for some of your users, you won't be able to track their install and event postbacks in Iterable.

To learn more about AppsFlyer's Customer User ID field (CUID) field, see AppsFlyer's support article Customer User ID (CUID).

TIP

Before getting started, set up your iOS and Android apps to support deep links. For more information, see iOS Universal Links Setup and Android App Links Setup.

In AppsFlyer

To get started with deep linking, you'll need to set up an AppsFlyer OneLink and enable deep linking in your AppsFlyer account. For detailed instructions on how to do this, see AppsFlyer's support guide OneLink Links and Experiences.

In Iterable

Step 1: Create a tracking domain

If you don't already have one, you'll need to create a tracking domain. See Email Setup for detailed instructions on how to do this.

Creating a tracking domain

Step 2: Configure HTTPS for your tracking domain

See Configuring HTTPS for Link Tracking Domains for detailed instructions on how to do this.

Step 3: Add a destination domain

Add your AppsFlyer OneLink domain (<YOUR_DOMAIN>.onelink.me) as a destination domain.

Step 4: Set up an Apple App Site Association (AASA) file for iOS

  1. In your browser, go to the following web address:

    https://<YOUR_APPSFLYER_ONELINK>/.well-known/apple-app-site-association

  2. Copy the contents of this page and paste them into the Apple section of your destination domain's configuration.

  1. In your browser, go to the following web address:

    https://<YOUR_APPSFLYER_ONELINK>/.well-known/assetlinks.json

  2. Copy the JSON content from this web page and paste it into the Android section of your destination domain's configuration.

TIP

For more information about this step, see the following support articles:

In your mobile apps

For detailed instructions on how to do this, see AppsFlyer's support article Setting Up Your App.

Step 2: Set up the AppsFlyer SDK

Update the code for your iOS and Android apps using AppsFlyer's iOS and Android SDKs.

  1. Set up your apps to support deep links.

  2. Call AppsFlyer's setResolveDeepLinkURLs method to fetch your OneLink URL from AppsFlyer.

  3. After fetching your OneLink URL, call AppsFlyer's onAppOpenAttribution method to get additional deep linking and attribution metdata from AppsFlyer.

NOTE

For help with this step, see AppsFlyer's documentation:

AppsFlyer postbacks reference

The following data fields are available in the installation postbacks:

  • attr_source : "AppsFlyer"
  • media_source: AppsFlyer Partner ID
  • campaign: Campaign Name
  • adset: Adset Name
  • ad: Ad
  • adgroup: Ad Group
  • publisher_id: Publisher ID
  • match_type: Fingerprinting, Device ID or Referrer
  • is_attributed: 0 (organic) or 1 (non-organic)
  • retargeting_type: Retargeting type
  • af_timestamp: AppsFlyer Install time
  • idfa: iOS Advertiser ID
  • advertiserId: Android Advertiser ID
  • app_id: App ID
  • app_name: App Name (as displayed in AppsFlyer)
  • language: device language
  • user_agent: device user-agent
  • platform: iOS or Android

These come through as custom tracking events, called install, via Iterable's POST /api/events/track API endpoint.

The post-install events contain the same fields, with additional fields to denote event and revenue-based values:

  • event_name: Event named tracked in AppsFlyer
  • attr_source : "AppsFlyer"
  • media_source: AppsFlyer partner ID
  • campaign: Campaign name
  • adset: Adset name
  • ad: Ad
  • adgroup: Ad group
  • publisher_id: Publisher ID
  • match_type: Fingerprinting, device ID or referrer
  • is_attributed: 0 (false) or 1 (true)
  • retargeting_type: Retargeting type
  • event_value: Event value JSON from AppsFlyer
  • revenue_usd: Event revenue displayed in USD
  • revenue: Event revenue displayed in the currency that was sent to AppsFlyer
  • currency: The currency that AppsFlyer originally received with the event
  • af_timestamp: AppsFlyer event timestamp
  • idfa: iOS advertiser ID
  • advertiserId: Android advertiser ID
  • app_id: App ID
  • app_name: App name (as displayed in AppsFlyer)
  • language: Device language
  • user_agent: Device user-agent
  • platform: Device operating system (iOS or Android)

Event names are passed through as they are named and tracked via AppsFlyer.

TIP

To learn about AppsFlyer and IDFA, see AppsFlyer's documentation:

Questions?

To contact AppsFlyer support, email support@appsflyer.com.

Related articles