Forwarding Data Subject Requests for Erasure

You can configure mParticle to forward Data Subject Requests (DSRs) for erasure to a number of supported partners. Once forwarded, mParticle can’t guarantee that data is deleted by the partner, so confirm that each partner fulfills the request.

You can distribute DSRs for erasure to the following partners. Click on the partner name to get details of their erasure APIs.

To forward DSRs for erasure:

  1. Obtain access credentials for each partner.
  2. Create and activate a data subject request output.
  3. Submit DSR for erasure using the UI or API.
  4. Check forwarding status.
  5. Verify that each partner has fulfilled the request.

Step 1: Obtain Partner Access Credentials

Collect partner credential information to use in the next step.

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

Step 2: Create and Activate a DSR Output

Create a DSR forwarding configuration for a partner 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 a partner.
  4. In the Data Subject Request dialog, add a Configuration Name and the access credential values you obtained in the previous section.
  5. When you are ready, set Forwarding Status to Active.
  6. Select I understand after reading the disclaimer.

DSR user interface

You can also check the status of a DSR output, or delete it.

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.

DSR Forwarding Considerations

Before you forward DSR for erasure, consider 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.
  • Different partners have different support IDs and distribution frequencies:

    Partner Supported IDs Distribution Frequency
    Amplitude User_id (mapped from user identification dropdown in Amplitude’s setup configuration Once an hour or every 1000 messages, with a max of 100 messages in each upload
    Blueshift customer_id, email Immediate
    Braze External Identity type Once an hour or every 1000 messages, with a max of 50 messages in each upload
    Kochava IDFA (iOS Advertising ID) and ADID (Android Advertising ID) Once an hour or every 10,000 messages

Other partners are not yet supported. Work with each partner directly to manage user data deletion.

Step 4: Check Forwarding Status

You can check distribution status in the UI or using v3 of the API.

Check Status With UI

To check status, visit Privacy > Data Subject Requests.

List of data subject requests

To see more detail, click a 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.

Was this page helpful?