Inbound Integrations

Partners can send client data to mParticle as a Feed, so that mutual customers can forward their data on to other services. To make a customer’s data available as a Feed, you need to send it to mParticle’s Events API using our dedicated partner URLs:

mParticle will provide you with a template to complete with information about your company and the data your feed will provide. We will also work with you to document your feed and test that it performs as expected.

To begin building a Feed integration, you need to:

1. Create a function or service to convert the data you want to forward into mParticle’s batch format. Please determine:

   1. Does the data you will forward to mParticle have platform-specific data for iOS/Android? Will this always be the case or just sometimes?
   2. What are all of the possible Device Identities you may send into mParticle?
   3. What are all of the possible User Identities you may send into mParticle?
   4. Will you send a Partner Identity into mParticle? What will this be called?
   5. What are all of the possible Event Types you may send into mParticle?
2. Create a secure way for your clients to be able to provide you with the API Key and Secret necessary to send their data to mParticle’s Events API. You can either build this into your Platform UI or communicate directly with each client wanting to access your Feed in mParticle.
3. In your mParticle Account use a Custom Feed to test your function or service. Forward data to this input using our HTTPS API endpoint. See our Events API documentation for more information. Note that Custom Feeds will not accept Partner Identities.
4. Ensure that your function or service will respond to an HTTP 429 Too Many Request response so that no data is dropped. Learn more about API throttling in Default Service Limits.

Don’t forget to provide a high-resolution logo to mParticle in SVG format with a transparent background.

Note: Different input sources have different priorities in mParticle. Data from partner data feeds has a lower priority than data input from CSV, SDK, or custom feeds. For example, once you set a user attribute’s key value from the Web SDK, you won’t be able to set that same key value from a partner data feed. For details, see Profile API.

Once you’re ready to publish your integration, mParticle will provide you with a template to complete with information about your company and the data your feed will provide.