mParticle’s customer data platform empowers you to do more with your data. Sophisticated marketers use mParticle to orchestrate data across their entire growth stack, enabling them to win in key moments of the customer journey.
You can improve your data flow by marrying mParticle and Braze for a seamless way to control the flow of information between systems. What’s more, with Currents, Braze’s real-time data export, connect data to mParticle and make it actionable across the entire growth stack.
If you’re looking for information on the Currents integration with mParticle, click here.
|mParticle Account & Account Information||mParticle||https://app.mparticle.com/login||You must have an active mParticle Account to utilize their services with Braze.|
If you want to connect your mobile and web apps to Braze, then you will need to use the embedded kit integration below.
If you have backend data outside of your apps, then you’ll want to use the Server API integration to pipe that data into Braze.
Please note that regardless of approach, it is necessary to integrate the mParticle embedded kit.
Embedded Kit Integration
Through the embedded kit integration, mParticle and Braze’s SDK will both be present on your application. Unlike a direct Braze integration, however, mParticle takes care of calling the majority of Braze SDK code for you. Any mParticle methods you use to track user data will automatically be mapped to Braze’s SDK. These mappings of mParticle’s SDK for Android, iOS and Web are open source and can be found on Braze’s mParticle’s GitHub page.
The embedded SDK integration allows you to take advantage of our full suite of features (Push, In-app Messages, News Feed, and all relevant message analytics tracking).
1. Integrate the mParticle SDKs
Integrate the appropriate mParticle SDKs into your app based on your platform needs:
2. Complete mParticle’s Braze Event Kit Integration
mParticle’s Braze Event Kit Integration Guide will walk you through custom mParticle:Braze alignment instructions based on your messaging needs (Push, Location Tracking, etc.).
3. Integrate the Braze SDK
Integrate the appropriate Braze SDKs into your app based on your messaging needs.
|In-App Messaging||Works automatically when the Braze Event Kit Integration (above) is completed successfully.|
|News Feed / Content Cards||Call Braze code directly (using REST API?)|
|Push for Android||Follow the mParticle Android Push Notification Integration Documentation.|
|Push for iOS||Follow the Braze iOS Push Notification Integration Documentation.|
|Push for Web||Works automatically when the Braze Event Kit Integration (above) is completed successfully.|
4. Configure your mParticle dashboard to enable the Braze Kit.
|API Key||Found in App Settings under the Manage App Group.|
|External Identity Type||The mParticle User Identity type to forward as an External ID to Braze. We recommend leaving this to the default value, Customer ID.|
|Braze Instance||Select Custom.|
|Custom SDK Endpoint||Given to you by your Braze support or account representative. For example:
|Custom REST Endpoint||Given to you by your Braze support or account representative. For example:
API keys will be different for each platform (iOS, Android, and Web).
Server API Integration
This is an add-on to route your backend data to Braze if you’re using mParticle’s Server-Side SDKs (e.g. Ruby, Python, etc.). To set up this server-to-server integration with Braze, please follow mParticle’s documentation here.
Connections Settings for your Braze Output
These settings are located in mParticle’s “Connections” tab under “Connect”. You will need to add Braze as an output.
The App Group REST API Key required to input in mParticle’s dashboard can be found in the Developer Console under the ‘API Settings’ tab.
Custom REST Endpoint: Set this to your relevant REST API endpoint. This should match the “Custom REST Endpoint” field in the Event Configuration for Braze found in your mParticle Dashboard in the “Setup” tab under “Outputs”.
On Data Mapping - Not all data types that are supported on mParticle are supported by Braze.
Custom Event Properties support string, numeric, boolean, or Date objects. It does not support arrays or nested objects.
Custom Attributes support string, numerical, boolean, date objects and arrays, but does not support objects or nested objects.