> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/measurement/mmp-guides/appsflyer.md).

# AppsFlyer

This guide helps you add Digital Turbine as an integrated partner with AppsFlyer, set up event postbacks, create tracking links, establish cost integration, and utilize the AppsFlyer Audiences tool to manage suppression lists.

{% hint style="info" %}
Some of the features described in the steps below require an active **AppsFlyer ROI360 Advanced** subscription to access.
{% endhint %}

{% stepper %}
{% step %}

#### [Configure Digital Turbine as an Integrated Partner](#step1-dt-partner)

Configure Digital Turbine as an Integrated Partner on the AppsFlyer dashboard.
{% endstep %}

{% step %}

#### [Configure Event Postbacks](#step2-postbacks)

Configure event postbacks on the AppsFlyer Dashboard.

{% hint style="info" %}
Sharing ad revenue data as a postback is available only with an active **ROI360 Advanced** subscription.
{% endhint %}
{% endstep %}

{% step %}

#### [Create a Tracking Link](#step3-tracking-link)

Create tracking links for Digital Turbine clicks and impressions.
{% endstep %}

{% step %}

#### [Enable Cost Tracking](#step4-cost-tracking)

Set up cost integration between Digital Turbine and AppsFlyer.

{% hint style="info" %}
Cost aggregation data is available only with an active **ROI360 Advanced** subscription.
{% endhint %}
{% endstep %}

{% step %}

#### [Set Up a Suppression List with Audiences](#step5-audiences)

Using the AppsFlyer **Audiences** tool, set up a suppression list.
{% endstep %}
{% endstepper %}

## Configure Digital Turbine as an Integrated Partner <a href="#step1-dt-partner" id="step1-dt-partner"></a>

To configure Digital Turbine as an integrated partner:

1. On the AppsFlyer dashboard, navigate to **My Apps**.
2. From the left panel, navigate to **Collaborate→Integrated Partners**.
3. Select the required app from the **App** dropdown list.
4. Search for **Digital Turbine** in the search field and select the required **Digital Turbine** partner from the results.

<div align="left" data-with-frame="true"><img src="/files/ba4ff98ffe929027aadc61b2ae8e79df6fd6c1c2" alt=""></div>

5. In the **Integration** tab, click **Activate Partner** and enable the **Share organic/non-organic indication** toggle in the **General Settings** area.

<div align="left" data-with-frame="true"><img src="/files/80e147e05ae5a5bb5d4706cda97e81c6b7813eaf" alt=""></div>

6. Select the appropriate tab to continue with platform-specific requirements.

{% tabs %}
{% tab title="Android" %}
{% hint style="info" %}
AppsFlyer enables preload attribution by default to ensure accurate tracking when an app is installed directly on a device.
{% endhint %}

* Keep the **Preload Attribution** toggle enabled.
* Set the **Preload lookback window** to at least `90` days (AppsFlyer's recommended default).

{% hint style="success" %}
To prevent attribution loss post successful app preload, consider extending the lookback window to up to `180` days.
{% endhint %}

<div align="left" data-with-frame="true"><img src="/files/UHGoTIb7RoO0ElKKk3py" alt=""></div>

{% hint style="warning" %}

* Preload Attribution requires AppsFlyer SDK 6.8.0 and later.
* Preload Attribution is applicable for on-device inventory only.
* Enabling Preload Attribution gives Digital Turbine longer lookback window options, deterministic matching without a device ID, and preload attribution priority for Digital Turbine above other ad engagements (impressions and clicks). Credit goes to Digital Turbine because the app is installed directly on the device as opposed to redirecting to the Store.
* Ensure that the **Preload equal attribution priority** toggle is off.
  {% endhint %}
  {% endtab %}

{% tab title="iOS" %}

* Turn off the **Enable** **Advanced Privacy** toggle.\
  For more information, see [Advanced Privacy](https://support.appsflyer.com/hc/en-us/articles/360011316197-Advanced-Privacy-guide-postback-macros-for-ad-networks).\
  This is required for probabilistic matching to be enabled.

<div align="left" data-with-frame="true"><img src="/files/91c5106004a1007e38b806c4b285d6b26b5d785e" alt=""></div>
{% endtab %}
{% endtabs %}

7. Enable the **Install View-Through Attribution** toggle.

<div align="left" data-with-frame="true"><img src="/files/255320b8463aac6e89a603940267cffc5e739971" alt=""></div>

8. Enable the **In-app event postbacks** toggle and set the **In-app event postback window** to **Lifetime**.

<div align="left" data-with-frame="true"><img src="/files/ddfebc8ea6edb2cc5118f6eded44d74080a6dae0" alt=""></div>

{% hint style="info" %}
Partner integration automatically triggers default postbacks for user actions that occur before the app launch—such as installs, rejected installs, and re-engagements.
{% endhint %}

## Configure Event Postbacks <a href="#step2-postbacks" id="step2-postbacks"></a>

{% hint style="info" %}
Sharing ad revenue data is available only with an **ROI360 Advanced** subscription.
{% endhint %}

1. While on the integration partner **Integration** tab, in the **In-app event postbacks** area, click **Add event**.
2. Select the required events and map them to the corresponding [partner events](#partner-events).
3. To share ad revenue data, add the `af_ad_revenue` postback event and map it to the partner identifier.

<div align="left" data-with-frame="true"><img src="/files/2517bf47681770a16e1c87073954e63ab8885321" alt=""></div>

<details>

<summary>Partner Events</summary>

Digital Turbine machine learning algorithms rely on standard event names to improve ad targeting, optimization, measurement, and insights.

For best results, use these names for event mapping:

* `ad_revenue`
* `app_open`
* `purchase`
* `level_achieved`
* `ad_click`
* `ad_view`
* `login`
* `add_payment_info`
* `add_to_cart`
* `add_to_wishlist`
* `checkout_initiated`
* `complete_registration`
* `complete_tutorial`
* `reservation`
* `update`
* `subscribe`
* `search`
* `view_content`
* `credits_spent`
* `achievement_unlocked`
* `app_rated`
* `tutorial_complete`
* `social_share`

If there's no suitable name on this list for an event, you can add an arbitrary event name. Use custom names without spaces or special characters other than the underscore ( \_ ).

</details>

4. For all designated events, including `af_ad_revenue`, select:

* **All media sources, including organic** from the **for users from** dropdown list.
* **Values & revenue** from the **including** dropdown list.

5. Click **Save Integration**.

## Create a Tracking Link <a href="#step3-tracking-link" id="step3-tracking-link"></a>

1. While on the integration partner setup form, select the **Attribution Link** tab.
2. Select the **Single-platform link** checkbox.

{% hint style="info" %}
Digital Turbine does not support **OneLink**.
{% endhint %}

3. Configure the following attribution windows:

* **Click-through window:** `30` days
* **View-through window:** `24` hours

<div align="left" data-with-frame="true"><img src="/files/ef20b7b072832a6a14947d3118bb8ab52a71bee1" alt=""></div>

4. Click **Save Attribution Link**.
5. Copy and send the two links to your Digital Turbine representative.

## Enable Cost Tracking <a href="#step4-cost-tracking" id="step4-cost-tracking"></a>

{% hint style="info" %}
Cost aggregation data is available only with an **ROI360 Advanced** subscription.
{% endhint %}

1. While on the integration partner setup form, select the **Cost** tab.
2. Click **+ New Integration**.

<div align="left" data-with-frame="true"><img src="/files/PDqB2mCdAaMufqepjbFP" alt=""></div>

3. Enter the integration name in the **Integration name** field.

<div align="left" data-with-frame="true"><img src="/files/1rRUJjcXZOfEp3TdcyKZ" alt=""></div>

4. To add additional Apps, click **Edit**.\
   The **Select the apps for this integration** dialog box appears.

<div align="left" data-with-frame="true"><figure><img src="/files/jIOCDcBhysya7rZMLUj7" alt=""><figcaption></figcaption></figure></div>

5. Select the checkboxes for the required apps and click **Apply**.\
   The additional apps appear in the **Apps** area.
6. Click **Save Cost**.

## Set Up a Suppression List With Audiences <a href="#step5-audiences" id="step5-audiences"></a>

{% hint style="info" %}
Digital Turbine requires suppression lists of existing devices through historical audience lists and real-time unattributed install postbacks (set up in a previous section). This section explains how to set up historical audience lists for suppression through AppsFlyer’s **Audiences** tool and only applies if you have this enabled on your AppsFlyer account.
{% endhint %}

1. Add an audience by following the steps outlined in [AppsFlyer's support documentation](https://support.appsflyer.com/hc/en-us/articles/115002689186-Audiences-guide#get-started).
2. Go to **Engage→Audiences→Connections**.
3. Click **+ New connection**.

{% hint style="info" %}
If you are creating a new partner connection from within the Audience Builder, click on **+ Add partner connection** within the **Manage audience connections** window.
{% endhint %}

4. Select **Appreciate** from the **Partner name** dropdown list.
5. Enter **Digital Turbine** in the **Connection name** field.

<div align="left" data-with-frame="true"><img src="/files/f82dd1a544288cbf2e6c2d82bb3926f7a13e269b" alt="" width="563"></div>

6. Enter the **Your** **buyer ID** and **API key** values in the partner connection. Your Digital Turbine representative will provide these values to you.

<div align="left" data-with-frame="true"><img src="/files/a0dd90683583eb2302d5580ffbe6ba52019ff7af" alt="" width="563"></div>

7. Select **GAID** and **IDFA** as the user identifiers that you authorize for sharing with this partner, then click **Save**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalturbine.com/measurement/mmp-guides/appsflyer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.