AppsFlyer Android

Send Android app events and conversions to AppsFlyer server-to-server for mobile attribution, analytics, and campaign optimisation.

⚠️

This blueprint is currently alpha — schema and behaviour may change before GA.

Prerequisites

Complete these steps in the AppsFlyer dashboard before configuring Signal.

Create an AppsFlyer account

Register your Android app

Click Add App in the dashboard, select Android, and enter your package name (e.g. com.example.myapp). The app must be registered before you can send server-to-server events.

Find your Dev Key

Navigate to Configuration > App Settings in the left sidebar. Your Dev Key is displayed at the top of the page. Copy this value.

Generate an API token

Go to Security Center (accessible from the top-right user menu or under Configuration). Generate a V2 API Token. This token authenticates all server-to-server event calls.

Note your App ID

Your App ID is the Android package name you registered (e.g. com.example.myapp). You will need this when configuring the integration in Signal.

Configuration

Field	Type	Required	Description
`app_id`	string	Yes	The Android package name as registered in AppsFlyer (e.g. `com.example.myapp`).
`dev_key`	string	Yes	Your AppsFlyer Dev Key from Configuration > App Settings.
`api_token`	secret	Yes	The AppsFlyer V2 API token from Security Center.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find AppsFlyer Android or filter by Attribution.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/appsflyer_android/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "AppsFlyer Android",
    "variant": "default",
    "config": {
      "app_id": "com.example.myapp",
      "dev_key": "AbCdEfGhIjKlMnOpQrSt",
      "api_token": "your_api_token"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The Retail variant maps the following Datafly events to AppsFlyer in-app event names:

Datafly Event	AppsFlyer Event	Notes
`Product Viewed`	`af_content_view`	Product details map to `af_content_id`, `af_price`, `af_currency`
`Product Added`	`af_add_to_cart`	Product details map to `af_content_id`, `af_price`, `af_currency`
`Order Completed`	`af_purchase`	Requires `af_revenue`, `af_currency`, `af_order_id`
Custom events	Passed through	Add the AppsFlyer event name in the blueprint event map

Identity

The default blueprint forwards the following identifiers to AppsFlyer:

Source	AppsFlyer field
`vendor_ids.appsflyer_id`	`appsflyer_id`
`vendor_ids.gps_adid`	`advertising_id` (Google Play)
`context.ip`	`ip`
`context.user_agent`	`user_agent`

Capture appsflyer_id from the AppsFlyer Android SDK at app start and pass it via the Datafly mobile SDK — every S2S event requires it.

Default consent category: advertising. Gate behind advertising consent in your CMP; only forward gps_adid when the user has not opted out of personalised ads.

AppsFlyer requires the appsflyer_id device identifier on every S2S event. Ensure your mobile app captures and forwards this ID through Signal.

Verify it’s working

Install your Android app on a test device and trigger the events you want to track.
In the Signal Management UI, open your AppsFlyer Android integration and watch the Live Events stream.
In the AppsFlyer dashboard, navigate to Activity > Event Timeline and filter by your test device.
Verify the event name, revenue, and custom parameters match expectations.
Confirm 200 responses in Signal’s Live Events log.

Troubleshooting

Symptom	Cause	Resolution
`401 Unauthorized`	Invalid API token	Regenerate the V2 API token in Security Center and update Signal.
`400 Bad Request`	Missing required fields	Ensure `appsflyer_id` and `app_id` are present in the event payload.
Events not appearing	Wrong app ID	Confirm `app_id` matches the package name registered in AppsFlyer.
Revenue not tracked	Missing `af_revenue` field	Map your revenue field to `af_revenue` (numeric) and `af_currency` (ISO 4217) in the blueprint.

Visit AppsFlyer documentation for full API reference and credential setup instructions.

Blueprint

The AppsFlyer Android blueprint version is 0.1.0 (alpha). It ships with a Retail variant covering af_content_view, af_add_to_cart, and af_purchase events.