Skip to content

mParticle for Currents

mParticle is a customer data platform that collects and routes information from multiple sources to a variety of other locations in your marketing stack.

The Braze and mParticle integration allows you to seamlessly control the flow of information between the two systems. With Currents, you can also connect data to mParticle to make it actionable across the entire growth stack.

Prerequisites

Requirement Description
mParticle account An mParticle account is required to take advantage of this partnership.
Currents In order to export data back into mParticle, you need to have Braze Currents set up for your account.
mParticle server to server key

mParticle server to server secret
These can be obtained by navigating to your mParticle dashboard and creating the necessary feeds that allow mParticle to receive Braze interaction data for iOS, Android, and Web platforms.

Integration

Step 1: Create feeds

From your mParticle admin account, navigate to Setup > Inputs. Locate Braze in the mParticle Directory and add the feed integration.

The Braze feed integration supports four separate feeds: iOS, Android, Web, and Unbound. The unbound feed can be used for events such as emails that are not connected to a platform. You will need to create an input for each main platform feed. You can create additional inputs from Setup > Inputs, on the Feed Configurations tab.

For each feed, under Act as Platform select the matching platform from the list. If you do not see an option to select an act-as feed, the data will be treated as unbound, but can still be forwarded to data warehourse outputs.

The first integration dialog box, prompting you to provide a configuration name, determine a feed status, and select a platform to act as. The second integration dialog box showing the server-to-server key and server-to-server secret.

As you create each input, mParticle will provide you with a key and secret. Copy these credentials, making sure to note which feed each pair of credentials is for.

Step 2: Create Current

In Braze, navigate to Currents > + Create Current > Create mParticle Export. Provide an integration name, contact email and the mParticle API key and mParticle secret key for each platform. Next, select the events you want to track; a list of available events is provided. Lastly, click Launch Current

The mParticle Currents page in Braze. Here, you can find fields for integration name, contact email, API key, and secret key.

All events sent to mParticle will include the user’s external_user_id as the customerid. At this time, Braze does not send event data for users who do not have their external_user_id set.

Integration details

You can export the following data from Braze to mParticle:

Event Name Feed Type Description Currents Properties
Push Notification Sends Platform-specific Feed A push notification was successfully sent to a User. app_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Push Notification Opens Platform-specific Feed User opened a push notification. app_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Push Notification Bounces Platform-specific Feed Braze was not able to send a push notification to this User. app_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
In-App Message Impressions Platform-specific Feed User viewed an In-App Message. app_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
In-App Message Clicks Platform-specific Feed User tapped or clicked a button in an In-App Message. button_id, app_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Content Card Sent Platform-specific Feed A Content Card was sent to a user’s device app_id, card_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Content Card Viewed Platform-specific Feed User viewed a Content Card app_id, card_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Content Card Clicked Platform-specific Feed User clicked a Content Card app_id, card_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Content Card Dismissed Platform-specific Feed User dismissed a Content Card app_id, card_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
News Feed Views Platform-specific Feed User viewed the native Braze News Feed. app_id, card_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
News Feed Card Views Platform-specific Feed User viewed a Card within the native Braze News Feed. app_id, card_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
News Feed Card Clicks Platform-specific Feed User clicked on a Card within the native Braze News Feed. app_id, card_id, campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Application Uninstalled Platform-specific Feed User uninstalled the App. app_id
Event Name Feed Type Description Currents Properties
Email Sends Unbound Feed An email was successfully sent. campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Email Deliveries Unbound Feed An email was successfully delivered to a User’s mail server. campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Email Opens Unbound Feed User opened an email. campaign_id, canvas_step_id, canvas_id, canvas_variation_id, user_agent, machine_open
Email Clicks Unbound Feed User clicked a link in an email. Email click tracking must be enabled. Link ID and Alias require Link Aliasing to be enabled campaign_id, canvas_step_id, canvas_id, canvas_variation_id, link_id, link_alias, user_agent
Email Bounces Unbound Feed Braze attempted to send an email, but the User’s receiving mail server did not accept it. campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Email Marks As Spam Unbound Feed User marked an email as spam. campaign_id, canvas_step_id, canvas_id, canvas_variation_id, user_agent
Email Unsubscribes Unbound Feed User clicked the unsubscribe link in an email. campaign_id, canvas_step_id, canvas_id, canvas_variation_id
SMS Sends Unbound Feed An SMS was sent to a user. campaign_id, campaign_name, message_variation_id, canvas_step_id, canvas_step_name, canvas_id, canvas_name, canvas_variation_id, canvas_variation_name, to_phone_number*
SMS Carrier Sends Unbound Feed An SMS was set to a carrier. campaign_id, campaign_name, message_variation_id, canvas_step_id, canvas_step_name, canvas_id, canvas_name, canvas_variation_id, canvas_variation_name, to_phone_number* , from_phone_number
SMS Deliveries Unbound Feed An SMS was delivered successfully. campaign_id, campaign_name, message_variation_id, canvas_step_id, canvas_step_name, canvas_id, canvas_name, canvas_variation_id, canvas_variation_name, to_phone_number* , from_phone_number
SMS Delivery Failures Unbound Feed An SMS unable to be delivered successfully. campaign_id, campaign_name, message_variation_id, canvas_step_id, canvas_step_name, canvas_id, canvas_name, canvas_variation_id, canvas_variation_name, to_phone_number* , from_phone_number, error, provider_error_code
SMS Rejections Unbound Feed An SMS was rejected. campaign_id, campaign_name, message_variation_id, canvas_step_id, canvas_step_name, canvas_id, canvas_name, canvas_variation_id, canvas_variation_name, to_phone_number* , from_phone_number, error, provider_error_code
SMS Inbound Received Unbound Feed An inbound SMS was received. inbound_phone_number, action, message_body
Subscription Group State Change Unbound Feed User’s subscription group state changed to ‘Subscribed’ or ‘Unsubscribed’ campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Webhook Sends Unbound Feed A webhook message was sent on behalf of a User. campaign_id, canvas_step_id, canvas_id, canvas_variation_id
Campaign Conversions Unbound Feed User performed the primary conversion event for a campaign within its conversion window. campaign_id
Campaign Control Group Enrollments Unbound Feed User was enrolled in a campaign control group. campaign_id
Canvas Conversions Unbound Feed User performed the primary conversion event for a Canvas within its conversion window. canvas_step_id, canvas_id, canvas_variation_id
Canvas Entries Unbound Feed User was entered into a Canvas. in_control_group, canvas_id, canvas_variation_id

* The mParticle $mobile attribute is used as the destination phone number (to_phone_number) in mParticle.

To read more about the mParticle integration, visit their documentation here.

WAS THIS PAGE HELPFUL?
New Stuff!