Forwarding Data Subject Requests

You can create an output to AppsFlyer that forwards data subject requests for erasure.

Before you configure AppsFlyer to forward data subject requests, be aware of the following:

• To avoid profile resolution complexities and subsequent conflation of user data deletion downstream, only a single user profile is resolved. All other identities associated with the resolved user profile are included in the user deletion message sent to downstream partners.
• When using the API or user interface, only a single identity of the same identity type is allowed when DSR for erasure forwarding has been enabled, such as a single customer ID, email address, or IDFA. You can send in multiple identities of different types such as Customer ID and email address. See API error messages for ID validation rules.
• To forward DSR for erasure for multiple user profiles, send one erasure request per user profile.
• mParticle forwards erasure requests on receipt of the request. The general processing time specified in General Request Workflow only applies to the mParticle fulfillment processing and does not apply to DSR for erasure forwarding.
• Once forwarded, mParticle can’t guarantee that data is deleted by the partner. You can confirm with the partner that the request has been fulfilled.

To forward data subject requests to AppsFlyer, use the following process.

Step 1: Obtain AppsFlyer Access Credentials

1. Obtain the API V2 Token from the API token page in the Dashboard. The API V2 token is the same API token used for Pull API.
2. Obtain the Property ID of the mobile app to which DSR forwarding requests should be scoped. This value represents the mobile app to which this request is scoped. Examples: iOS: id123456789 Android: com.example, com.publishers.name Android out-of-store: com.publisher.name-channel

In some cases, app owners record out-of-store attribution using the Android Google Play name. In these cases use the regular app name as it displays in the Dashboard.

If you can’t find the information, contact your AppsFlyer account representative.

Step 2: Create and Activate a DSR Output

Create a DSR forwarding configuration for AppsFlyer and activate it:

1. From your mParticle workspace, open Setup > Outputs and select the Data Subject Requests tab.
2. Click Add Data Subject Request.
3. Choose AppsFlyer.

4. In the Data Subject Request dialog:

   a. Enter a DSR output Configuration Name.

   b. Enter the API V2 Token you obtained in Step 1.

   c. Enter the Property ID you obtained in Step 1.

5. Save the configuration with the default Inactive or, if you are ready, set Forwarding Status to Active. Once the status has been set to Active, erasure requests are forwarded to AppsFlyer immediately.
6. Select I understand after reading the disclaimer.

Step 3: Submit Requests for Erasure

After the DSR forwarding is configured, use either the mParticle user interface or API to submit requests for erasure.

• Instructions for the user interface
• Instructions for the API You must use v3 of the API with DSR.

Step 4: Check Forwarding Status

You can check the forwarding request status in the mParticle UI or using v3 of the mParticle DSR API.

Check Status With UI

To check status, visit Privacy > Data Subject Requests.

To see more detail, click the request ID.

Check Status With API

To check forwarding status per partner, use the GET /requests/{RequestID} resource. The status reported is for forwarding and does not indicate fulfillment status from the partner.

See Data Subject Request API for information about API callbacks and the extensions element that supports erasure.

Step 5: Verify Partner Fulfillment

Once forwarded, mParticle cannot guarantee that data is deleted from your outputs. Always confirm that each partner fulfills the request.