AppsFlyer
AppsFlyer is a mobile marketing analytics and attribution platform that helps businesses track, measure, and optimize their app marketing efforts across various channels.
ingestr supports AppsFlyer as a source.
WARNING
AppsFlyer uses different names for input dimensions vs their name in the output schema. For instance, in order to obtain campaign information, you need to use the c
dimension; however, in the output schema, the resulting column will be called campaign
.
URI Format
The URI format for AppsFlyer is as follows:
appsflyer://?api_key=<api-key>
An API token is required to retrieve reports from the AppsFlyer API, please follow the guide to obtain an API key
Let's say your API key is ey123
, here's a sample command that will copy the data from AppsFlyer into a DuckDB database:
ingestr ingest
--source-uri 'appsflyer://?api_key=ey123'
--source-table 'campaigns'
--dest-uri duckdb:///appsflyer.duckdb
--dest-table 'appsflyer.output'
The result of this command will be a table in the appsflyer.duckdb
database.
Supported Tables
ingestr integrates with the Master Report API of AppsFlyer, which allows you to retrieve data for the following tables:
campaigns
: Retrieves data for campaigns, detailing the app's costs, loyal users, total installs, and revenue over multiple days.creatives
: Retrieves data for a creative asset, including revenue and cost.custom:<dimensions>:<metrics>
: Retrieves data for custom tables, which can be specified by the user.
Use these as --source-table
parameter in the ingestr ingest
command.
Custom Tables
You can also ingest custom tables by providing a list of dimensions and metrics.
The table format is as follows:
custom:<dimension1>,<dimension2>,<metric1>,<metric2>
This will automatically generate a table with the dimensions and metrics you provided.
For custom tables, ingestr will use the given dimensions as the primary key to deduplicate the data.
NOTE
ingestr will add install_time
as the primary key to the table by default if it is not provided as one of the dimensions.