Already have an account? Sign in

AppsFlyer (v1)

AppsFlyer integration summary

Stitch’s AppsFlyer integration replicates data using theAppsFlyer Raw Data Reports V5 API. Refer to theSchema section for a list of objects available for replication.

AppsFlyer feature snapshot

A high-level look at Stitch's AppsFlyer (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting AppsFlyer

AppsFlyer setup requirements

To set up AppsFlyer in Stitch, you need:

• To be the AppsFlyer Account Owner. Only Account Owners have access to API credentials in AppsFlyer, which is required to set up the integration.

• Access to raw data exports in AppsFlyer. Stitch’s AppsFlyer integration uses theRaw Data Report API to replicate installation and in-app event data. Access to raw data is an AppsFlyer premium feature, which may only be available on their higher tiers.

  To determine if you have access to raw data pulling,follow these instructions in AppsFlyer’s documentation.

Step 1: Retrieve the app ID

Sign into your AppsFlyer account.

Depending on the app’s type (iOS, Android, or Windows), the app ID format will vary:

• iOS - This will be the iTunes ID of your app. Example:id987654321.
• Android - This will be the package name registered on AppsFlyer. For example: If the package is registered ascom.stitchdata.test, the ID would becom.stitchdata.test.
• Windows - This will be the Windows app ID. For example:f1e2d3c4b5a6

The location of each type of app ID is highlighted in the image below:

Step 2: Retrieve the account's API key

1. In the list of apps, click the app you want to replicate data from. This will open the app’s dashboard page.
2. Under theIntegration section, clickAPI Access.
3. Copy the key from theYour API Key field.

Step 3: Add AppsFlyer as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click theAdd Integration button.

3. Click theAppsFlyer icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch AppsFlyer” would create a schema calledstitch_appsflyer in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theApp ID field, enter the ID of the app you want to replicate data from.
6. In theAPI Token field, paste the API key fromStep 2.

Step 4: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your AppsFlyer integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond AppsFlyer’s default setting of60 days. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Note: AppsFlyer imposes limits on date ranges for replicating historical data. If theStart Date is more than 90 days from the current date, replication will be unsuccessful. Refer to theHistorical AppsFlyer data limitations section for more info.

Step 5: Create a replication schedule

In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

AppsFlyer integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up AppsFlyer, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

AppsFlyer replication

Historical AppsFlyer data limitations

Due to limits imposed by AppsFlyer on date ranges while querying, only the past90 days’ of historical data is available for any given app.

If the integration’sStart Date setting in Stitch is set to a date older than 90 days ago, extraction errors will occur and be surfaced in the integration’sExtraction Logs.

AppsFlyer API call limits and Replication Frequency

In addition to historical limitations, AppsFlyer alsoimposes a limit on the number of raw data API calls that can be made per day. Currently, the maximum is10 API calls per day, per app and increases when upgrading to a higher AppsFlyer tier.

Each time Stitch requests data for an app - or a single AppsFlyer integration - two API calls will be used: One to replicatein_app_events, and one forinstallations.

If your Stitch AppsFlyer integration is set to replicate frequently (ex: every 30 minutes), you may quickly consume your AppsFlyer API quota. When this occurs, Stitch will pause replication and resume where it left off when more quota is available.

To avoid disruptions in replication, we recommend selecting a lowerReplication Frequency, such as 12 or 24 hours.

AppsFlyer table reference

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.