On This Page
AppsFlyer is a mobile-app tracking and attribution analytics platform that helps app developers and marketers to manage, measure, and optimize their mobile user acquisition process.
Hevo uses AppsFlyer’s PULL API to replicate the raw and aggregated app performance reports from your AppsFlyer account to the Destination system. The user needs to provide the AppsFlyer API Token to connect Hevo to the AppsFlyer account.
The user authorizing the application has an active AppsFlyer account with access to at least one app.
The user authorizing the application has
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: App ID for iOS apps starts with
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 API tokens.
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.
Incremental Data: Once the Pipeline is created, Hevo fetches all the data for the last 90 days during the first run. Every subsequent run of the Pipeline fetches the new and updated data.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination:
Hevo uses the following data model to ingest data from your AppsFlyer account:
|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.
- Hevo does not support raw reports of
Retargetingfetched from AppsFlyer.