mParticle

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

Version

This integration utilizes the mParticle Identity v1, Events v2 and Data Subject Request v3 APIs.

Base URL

The base URL used for all mParticle API endpoints:

https://opendsr.mparticle.com/v3

Endpoints Utilized

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

Method	Endpoint	Purpose	Docs
GET	/requests/0	Verify connection
POST	https:​//events_base_url/v2/events	Verify connection

---

Authentication & Authorization

The DataGrail mParticle integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.

Sensitive Credentials

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

---

Limits

Limits in mParticle 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 mParticle integration provides Asynchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Submit a Data Subject Request.
   • Regulation: gdpr.
   • Subject Request Type: access.
   • Subject identities include the configured identifiers.
2. Continuously check the status of the OpenDSR request until complete.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
POST	/requests	Submit a Data Subject Request
GET	/requests/request_id	Get the status of an OpenDSR request

---

Deletion

DataGrail's mParticle integration provides Asynchronous (Whole Record) Deletion capabilities for the following supported identifier category: Email.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

1. Submit a Data Subject Request.
   • Regulation: gdpr.
   • Subject Request Type: erasure.
   • Subject identities includes the configured identifiers.
2. Continuously check the status of the OpenDSR request until complete.
3. Search user identities using configured identifiers to confirm erasure.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
POST	/requests	Submit a Data Subject Request
GET	/requests/request_id	Get the status of an OpenDSR request
POST	https:​//identity.mparticle.com/v1/search	Search user identity

---

Opt Out

DataGrail's mParticle integration provides Opt Out capabilities for the following supported identifier category: Email.

Data Interactions

For Opt Out requests, DataGrail will take the following actions:

1. Search user identities using configured identifiers.
2. If a user identity is found, upload the event data to update consent status.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
POST	https:​//events_base_url/v2/events	Upload an event batch
POST	https:​//identity.mparticle.com/v1/search	Search user identity

---