AppsFlyer

Prerequisites

The user authorizing the application has an active AppsFlyer account with access to at least one app.
The user authorizing the application has Admin access.
A valid App ID and API Token is available in AppsFlyer.

Configuring AppsFlyer as a Source

Perform the following steps to configure AppsFlyer as the Source in your Pipeline:

Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select AppsFlyer.
In the Configure your AppsFlyer Source page, specify the following:
- Pipeline Name - A unique name for your Pipeline.
- App ID - The unique ID of your AppsFlyer app.
- API Token - The API token for your AppsFlyer account.
- Pull API Timezone - The timezone in which you want to receive the data.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.

Locating the App ID and the API Token

The App ID is the unique ID of the app listed in the AppsFlyer dashboard whose data you want to replicate to the Destination.

Step 1. Locate the App ID

Log in to your AppsFlyer account.
On the homepage, you can find the apps added to your account.
Copy the App ID of the app you want to fetch data from.
Hevo uses this App ID to configure AppsFlyer as a Source.

Note: The App ID for iOS apps starts with id.

Step 2. Locate the API Token

In the top right of the AppsFlyer homepage, click the drop-down next to your username, and then click Security center.
In the Manage your account security page, scroll down and select Manage your AppsFlyer API tokens.
In the page that is displayed, copy the API token V1.0 and use it in Hevo to configure AppsFlyer as a Source.

The API token V1.0 allows Hevo to pull raw and aggregated data reports from AppsFlyer.

Data Replication

Historical Data: On the first run of the Pipeline, Hevo fetches all the data for your selected objects up to the maximum duration allowed by the AppsFlyer API.

Refer to the following table to know about the maximum number of days for which Hevo can fetch historical data for each object:

Object	API Limit for Historical Data (Days)
daily_report	60
geo_by_date_acquisition_report	60
geo_by_date_retargeting_report	60
in-app_events_report	31
in-app_events_retargeting_report	31
installs_report	60
organic_installations_report	60
organic_in_app_events_report	31
partners_by_date_report	60
partners_report	100
uninstalls_report	60

Incremental Data: Every subsequent run of the Pipeline fetches the new and updated data. The default ingestion frequency is 24 hours. Contact Hevo Support if you want to change it.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

Data Model

Hevo uses the following data model to ingest data from your AppsFlyer account:

Object	Report Type	Description
daily_report	Aggregated	Contains details of clicks and impressions grouped by Date.
geo_by_date_acquisition_report	Aggregated	Contains an acquisition report grouped by date, country, agency, media source, and campaign. To view examples, see this.
geo_by_date_retargeting_report.	Aggregated	Contains retargeting report grouped by date, country, agency, media source, and campaign. To view examples, see this.
in-app_events_report	Raw	Contains report of in-app events as per the user’s action.
in-app_events_retargeting_report	Raw	Contains the data of the media sources attributed to the conversion.
installs_report	Raw	Contains report of the event generated when the app is opened for the first time.
organic_installations_report	Raw	Contains installation reports of the app, such as, the time of installation, type of device, operating system, region, city, and country.
organic_in_app_events_report	Raw	Contains details of actions performed by users.
partners_by_date_report	Aggregated	Contains partner data grouped by date, agency, media source, and campaign. View examples here.
partners_report	Aggregated	Contains partner data grouped by date, agency, media source, and campaign. View examples here.
uninstalls_report	Raw	Contains uninstallation reports of the app, such as, time of uninstallation, type of device, operating system, region, city, and country.

Note: __hevo_id, which represents a unique ID for the Source data, is derived by hashing the Source data’s primary key columns.

Limitations

Hevo does not support raw reports of Ad revenue and Retargeting fetched from AppsFlyer.

Revision History

Refer to the following table for the list of key updates made to this page:

Date	Release	Description of Change
Mar-17-2022	NA	Removed the Pipeline frequency table from the Data Replication section as you cannot configure the Pipeline frequency from the UI.
Mar-07-2022	NA	- Updated the steps under the Locating the App ID and the API Token section, to reflect the latest AppsFlyer UI. - Updated the Pipeline Frequency table and added information about historical data in the Data Replication section.
Oct-25-2021	NA	Added the Pipeline frequency information in the Data Replication section.

Last updated on 27 May 2022