The tap-appsflyer extractor pulls data from AppsFlyer that can then be sent to a destination using a loader.
Alternate Implementations
Getting Started
Prerequisites
If you haven't already, follow the initial steps of the Getting Started guide:
Installation and configuration
-
Add the tap-appsflyer extractor to your
project using
:meltano add -
Configure the tap-appsflyer
settings using
:meltano config -
Test that extractor settings are valid using
:meltano config
meltano add extractor tap-appsflyermeltano config tap-appsflyer set --interactivemeltano config tap-appsflyer testNext steps
Follow the remaining steps of the Getting Started guide:
If you run into any issues, learn how to get help.
Capabilities
The current capabilities for
tap-appsflyer
may have been automatically set when originally added to the Hub. Please review the
capabilities when using this extractor. If you find they are out of date, please
consider updating them by making a pull request to the YAML file that defines the
capabilities for this extractor.
This plugin has the following capabilities:
- catalog
- discover
- state
You can
override these capabilities or specify additional ones
in your meltano.yml by adding the capabilities key.
Settings
The
tap-appsflyer settings that are known to Meltano are documented below. To quickly
find the setting you're looking for, click on any setting name from the list:
You can also list these settings using
with the meltano configlist
subcommand:
meltano config tap-appsflyer list
You can
override these settings or specify additional ones
in your meltano.yml by adding the settings key.
Please consider adding any settings you have defined locally to this definition on MeltanoHub by making a pull request to the YAML file that defines the settings for this plugin.
API Token (api_token)
-
Environment variable:
TAP_APPSFLYER_API_TOKEN
Your API token. See the API docs for more details on obtaining your token. Also note if you change the account admin, the token changes, and you must update scripts with the new token.
Configure this setting directly using the following Meltano command:
meltano config tap-appsflyer set api_token [value]App ID (app_id)
-
Environment variable:
TAP_APPSFLYER_APP_ID
The app ID as shown in AppsFlyer.
Configure this setting directly using the following Meltano command:
meltano config tap-appsflyer set app_id [value]Base Url (base_url)
-
Environment variable:
TAP_APPSFLYER_BASE_URL
The base url to use for requests, defaul https://hq.appsflyer.com.
Configure this setting directly using the following Meltano command:
meltano config tap-appsflyer set base_url [value]Organic Installs (organic_installs)
-
Environment variable:
TAP_APPSFLYER_ORGANIC_INSTALLS
Whether to include the organic installs stream in your sync.
Configure this setting directly using the following Meltano command:
meltano config tap-appsflyer set organic_installs [value]Start Date (start_date)
-
Environment variable:
TAP_APPSFLYER_START_DATE
Determines how much historical data will be extracted. Please be aware that the larger the time period and amount of data, the longer the initial extraction can be expected to take.
Configure this setting directly using the following Meltano command:
meltano config tap-appsflyer set start_date [value]User Agent (user_agent)
-
Environment variable:
TAP_APPSFLYER_USER_AGENT
The user agent to send with requests.
Configure this setting directly using the following Meltano command:
meltano config tap-appsflyer set user_agent [value]Something missing?
This page is generated from a YAML file that you can contribute changes to.
Edit it on GitHub!Looking for help?
#plugins-general-brightgreen){kind=icon}
-2-c0c0c4){kind=icon}
