Back

This article describes how to set up the AppsFlyer App Events connector in your Universal Data Hub account.

This connector replaces the (DEPRECATED) AppsFlyer App Events Connector. This feature is currently available in as an experiment only and must enabled prior to use. (Learn more)

In this article:

Table of Contents Placeholder

Connector Actions

Action Name AudienceStream EventStream
Track Install
Track in App Event

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • App ID
    • This is the App ID of the app for which you are passing data.
  • Dev Key
    • The account dev key taken from the App Settings screen in the AppsFlyer dashboard.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Track Install

Parameters

Parameter Description
Platform
  • The platform the event came from.
  • Values in drop-down list are Android, Windows, or iOS.
iad-adgroup-id
  • Ad ID group ID.
iad-adgroup-name
  • Ad ID group name.
iad-attribution
  • Ad ID attribution.
iad-campaign-id
  • Ad ID campaign ID.
iad-campaign-name
  • Ad ID campaign name.
iad-click-date
  • Ad ID click date.
iad-conversion-date
  • Ad ID conversion date.
iad-keyword
  • Ad ID keyword.
iad-lineitem-id
  • Ad ID line item.
iad-lineitem-name
  • Ad ID line item name.
iad-org-name
  • Ad ID organization name.

Action - Track in App Event

Parameters

Parameter Description
Platform
  • The platform the event came from.
  • Values in drop-down list are Android, Windows, or iOS.
Event Currency
  • Default currency for the event
  • Only use for 'USD', for all else, map under the Event Properties
    (event_value) section using the af_currency key.
Event Name
  • Required.
  • A string describing the event name.
  • Example: 'af_purchase'.