AppsFlyer Source

Ingest your event data from AppsFlyer into RudderStack.

3 minute read

AppsFlyer is an industry-leading mobile attribution and marketing analytics platform. It enables you to understand your customers better through intuitive dashboards, real-time data reports, and a unique deep linking technology.

You can send your AppsFlyer events by adding an endpoint that points to RudderStack and using AppsFlyer’s Push API option. This way, you can capture all relevant AppsFlyer events related to re-engagement, reattribution, in-app install events, etc., and send them to RudderStack.

This guide will help you set up AppsFlyer as a source in RudderStack.

Get started

Go to your RudderStack dashboard and click Add Source. From the list of Event Streams sources, select AppsFlyer.
Assign a name to your source and click Continue*.
Your AppsFlyer source is now configured. Note the source write keyThe write key (or source write key) is a unique identifier for your source. RudderStack uses this key to send events from a source to the specified destination. required to configure the endpoint URL.
Go to your AppsFlyer account. From the sidebar, go to Integrations > API Access > Push API:

Add the Endpoint URL pointing to RudderStack in the following format:

<DATA_PLANE_URL>/v1/webhook?writeKey=<WRITE_KEY>

Make sure to:
Replace <DATA_PLANE_URL> with the data plane URL associated with your RudderStack workspace.
Add the source write key obtained in Step 3 as a query parameter to the URL. This is required to prevent the webhook from failing.
Validate the endpoint before proceeding.

Save the endpoint.

Event transformation

RudderStack converts all AppsFlyer push events into track events using the RudderStack event format. For example, RudderStack converts the customer_user_id property set by AppsFlyer into userId.

Supported mappings

The following table shows how AppsFlyer event properties map to RudderStack event properties:

AppsFlyer property	RudderStack property
`android_id` Android	`context.device.advertisingId`
`idfa` iOS	`context.device.advertisingId`
`app_name`	`context.app.name`
`app_version`	`context.app.version`
`appsflyer_id`	`context.externalId[0].value`
`bundle_id`	`context.app.namespace`
`carrier`	`context.network.carrier`
`city`	`traits.address.city` `context.traits.address.city`
`country_code`	`traits.address.country` `context.traits.address.country`
`customer_user_id`	`userId` `context.traits.userId`
`device_type`	`context.device.model`
`event_name`	`event`
`event_time`	`timestamp` `originalTimestamp`
`ip`	`context.ip`
`os_version`	`context.os.version`
`platform`	`platform` `context.os.name`
`postal_code`	`traits.address.zip` `context.traits.address.zip`
`selected_timezone`	`context.timezone`
`user_agent`	`context.userAgent`
`wifi`	`context.network.wifi`

All unmapped properties from the AppsFlyer event payload are preserved in the properties object of the resulting track event.

Sample payload and transformation

This section details how RudderStack receives the data from AppsFlyer and creates the resulting payload.

A sample payload sent by AppsFlyer is shown:

json

{
  "idfv": "868049A3-4B2F-4A11-9B00-CFFC362XXXXX",
  "device_category": "phone",
  "customer_user_id": "alex@example.com",
  "bundle_id": "com.appsflyer.AppsFlyer",
  "app_version": "1.4.1",
  "city": "New York",
  "selected_currency": "USD",
  "app_name": "AppsFlyer",
  "postal_code": "10001",
  "wifi": true,
  "country_code": "US",
  "appsflyer_id": "1234567890",
  "event_value": "{}",
  "ip": "1.1.1.1",
  "event_time": "2020-01-15 14:57:24.898",
  "device_type": "iPhone 13",
  "idfa": "A7071198-3848-40A5-B3D0-XXXXXXBZZZZ",
  "language": "en-US",
  "event_name": "My Apps",
  "os_version": "12.3.1",
  "platform": "ios",
  "selected_timezone": "UTC",
  "user_agent": "AppsFlyer/1 CFNetwork/978.0.7 Darwin/18.6.0"
}

RudderStack transforms the above payload into the following track payload: