AppsFlyer

This documentation for the AppsFlyer integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate AppsFlyer, visit our connection instructions.

Version

This integration utilizes the AppsFlyer OpenDSR API v1 and v2.

Base URL

The base URL used for all AppsFlyer API endpoints:

https://hq1.appsflyer.com/api/gdpr/v1

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	/discovery	Validate credentials

---

Authentication & Authorization

The DataGrail AppsFlyer integration connects using token authentication which requires an API Token.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to AppsFlyer API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

---

Limits

Limits in AppsFlyer are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's AppsFlyer integration provides Asynchronous Access capabilities for the following supported identifier categories: Email and Service ID.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Submit an OpenDSR access request.

info

The identity_type parameter in the request payload is set to appsflyer_id. More information about the request parameters can be found in AppsFlyer's documentation.

2. Check request status.
3. Download and parse the access report.

note

The AppsFlyer integration does not support access for LAT User (Limit Ad Tracking / iOS privacy-restricted users) data. AppsFlyer’s Help Center clarifies that requests involving LAT users can’t be processed through the OpenDSR/GDPR Requests API.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/download/subject_request_id	Download the access report
POST	/opendsr_requests	Submit an OpenDSR access request
GET	/opendsr_requests/subject_request_id	Check request status

---

Deletion

DataGrail's AppsFlyer integration provides Asynchronous (Whole Record) Deletion capabilities for the following supported identifier categories: Email and Service ID.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

1. Submit an OpenDSR erasure request.

info

The identity_type parameter in the request payload is set to appsflyer_id. More information about the request parameters can be found in AppsFlyer's documentation.

2. Continuously check the request status until it is complete.

note

The AppsFlyer integration does not support deletion of LAT user (Limit Ad Tracking / iOS privacy-restricted users) data. AppsFlyer’s Help Center clarifies that requests involving LAT users can’t be processed through the OpenDSR/GDPR Requests API.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
POST	/opendsr_requests	Submit an OpenDSR erasure request
GET	/opendsr_requests/subject_request_id	Check request status

---