You can create an output to Blueshift that forwards data subject requests for erasure.
Before you configure Blueshift 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 Blueshift, use the following process.
Step 1: Obtain Blueshift Access Credentials
Copy the Users API key. You must be a Blueshift admin user to see this information. Enable Delete All Matching Customers if you want to delete all matching profiles of a user in Blueshift.
If you can’t find the information, contact your Blueshift account representative.
Step 2: Create and Activate a DSR Output
Create a DSR forwarding configuration for Blueshift and activate it:
From your mParticle workspace, open Setup > Outputs and select the Data Subject Requests tab.
Click Add Data Subject Request.
Choose Blueshift.
In the Data Subject Request dialog:
a. Enter a DSR output Configuration Name.
b. Enter the User API key you obtained in Step 1.
c. Select a Delete User Option to specify behavior when a User is deleted. Blueshift supports two endpoints for deleting customer data. The DELETE endpoint permanently deletes all personal data of the customer. The FORGET endpoint permanently deletes all personal data of the customer as well as makes the platform forget the user by keeping a marker that a particular user was deleted and ignores new events for that user in future if they come in.
Select the “Delete a customer” option to use the DELETE endpoint.
Select the “Delete a customer and all matching profiles” option to use the DELETE endpoint AND delete all matching profiles of the customer in Blueshift.
Select the “Stop tracking a customer” option to use the FORGET endpoint.
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 Blueshift immediately.
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.
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.