> For the complete documentation index, see [llms.txt](https://docs.roivenue.com/roivenue-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/appsflyer.md).

# AppsFlyer

How to connect AppsFlyer to Roivenue, what the default setup downloads, and how the figures are put together.

AppsFlyer is a mobile attribution platform. The Roivenue connector downloads its in-app events report, which lists the events AppsFlyer attributed to each media source.

## Setting up the connector

Add an AppsFlyer connector in Roivenue. It reads an AppsFlyer export URL, which contains both your app id and an account owner API token, so the URL itself is the credential.

## What the default setup downloads

One job, reading the in-app events report.

### Where the values land

| AppsFlyer field | Roivenue column |
| --------------- | --------------- |
| media source    | adCampaign      |
| event counts    | conversions     |
| event revenue   | conversionValue |

{% hint style="warning" %}
The recommended template ships with a sample export URL, including a placeholder app id and the text where the API token belongs. It will not return anything until that URL is replaced with one built for your own app. Your Account Manager does this as part of setup.
{% endhint %}

The report URL also fixes the timezone and the list of additional fields, so changing what the connector downloads means changing the URL.

The job reprocesses the last three days on every run.

## Available columns

The table above is what the recommended template downloads. Every column this connector can bring back is listed on [AppsFlyer - Supported Columns](/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/appsflyer/appsflyer-supported-columns.md).

Adding one means editing the connector in the Advanced Editor, which stops that connector receiving template updates.

## How far back the data goes

The connector will request up to three years of history. How much arrives depends on what the platform holds for the account.

## Troubleshooting

<details>

<summary>No data arrives</summary>

The most likely cause is the sample export URL still being in place. It carries a placeholder app id and no real API token. Ask your Account Manager to replace it with your own report URL.

</details>

<details>

<summary>Dates look shifted</summary>

The timezone is part of the export URL rather than a connector setting. If it does not match your reporting timezone, events land on neighbouring days.

</details>