You must completely configure your MMP to ensure accurate data tracking and optimal campaign performance. Complete all the steps listed below before you launch any campaign. Unless otherwise indicated, do each step in the AppsFlyer dashboard.
Configure AppLovin as a partner. To configure AppLovin as a partner, do the following:
Open appsflyer.com in your browser.
Choose which app you want to enable for data sharing with AppLovin on the AppsFlyer homepage.
Select Collaborate > Active Integrations.
To activate the AppLovin partnership, search “AppLovin” using the search bar, then select it from the search results.

Select the Integration tab.
Toggle Activate partner to ON.
Click Save Integration.

Configure privacy settings. You can skip this step for Android apps. To configure privacy settings for iOS apps, do the following:

Enable organic data indication.

Configure SDK key.

Enable install attribution.

Configure install postbacks.

Configure uninstall postbacks. AppsFlyer can measure uninstalls and send uninstall postbacks to AppLovin. Complete the steps below in order.
Complete the developer-side SDK setup. Your developer must integrate the SDK first so AppsFlyer can detect uninstalls. For Android, connect Firebase Cloud Messaging, then integrate the SDK. For iOS, generate a P12 certificate, then then integrate the SDK.
Enable uninstall measurement. Select Settings > App Settings > Uninstall measurement and toggle it on. For Android, select HTTP V1, enter your FCM Project ID, then click Test connection and Save settings. For iOS, upload your P12 file, enter the certificate password if applicable, then click Validate and Save settings.

Map the uninstall event. For marketers, now you can select the Integration tab. In the In-app event postbacks subsection:

Tip: The developer-side setup and uninstall measurement must both be complete before AppLovin receives any postbacks. Mapping af_uninstall alone is not sufficient.
Configure in-app event postback settings. To configure in-app event postbacks such as checkout or other post-install events, do the following:

Map in-app event postbacks. In the In-app event postbacks subsection, map all postback events by selecting and completing the required details for each field: AppsFlyer event, mapped to partner event, for users from, and including. In the mapped to partner event field, you can map events as landing, checkout, or postinstall. Set your AppsFlyer events according to the following table:
| AppsFlyer events | mapped to partner event | for users from | including |
|---|---|---|---|
| Any app open events | landing | All media sources, including organic | No values & no revenue |
| Any revenue events | checkout | All media sources, including organic | Values & revenue |
| All other events | postinstall | All media sources, including organic | No values & no revenue |
| The uninstall event | postinstall | All media sources, including organic | No values & no revenue |

Only send revenue that you generate from direct user payments for digital or physical goods or services.
Send:
Do not send:
Always send the full value the user is being charged (including all taxes and fees). If the transaction is not in USD, you may send the local currency amount and specify the currency of the transaction, or have your MMP handle the currency conversion to USD using the exchange rate of the day. Contact your MMP representatives if you have questions about currency reporting and exchange in checkout postbacks.
Configure attribution link type

Configure tracking URLs. In the Attribution link parameters subsection, select Parameter names and their corresponding Values to auto-populate your click and view-through tracking URLs.

Set attribution windows.

AppsFlyer can pull AppLovin cost data directly from AppLovin’s reporting API. To configure this:
&af_c_id={CAMPAIGN_ID}”.com.example.PackageExample format for both iOS and Android.