Under the Hood: The Nuts and Bolts of Using Braze with a CDP
It’s true—customer data platforms (CDPs) are hot right now.
Over the past few years, we’ve seen a significant increase in the number of Braze customers choosing to pair our platform with one of these solutions, which are intended to help companies unify and better manage data. Whether it’s mParticle, Segment, Tealium, or others, this trend knows no geographic bounds; companies across the Americas, Europe, and Asia are taking steps to make these solutions a centralized hub for managing and routing data to their entire tech ecosystem.
With that said, it’s important to understand both the value that you can receive from using Braze together with a CDP and what it takes to get that sort of connection up and running. So let’s take a look under the hood...
Braze and CDPs: Supporting Bi-Directional Data Flows
At a high level, using Braze together with a CDP can support a bi-directional flow of data that enables you to easily collect, connect, and take action upon your data across any customer touchpoint. CDPs are able to do this by collecting data from two primary sources:
- Web and mobile applications
- Backend servers and third-party systems
At the same time, these solutions can connect all of the engagement and additional data collected and streamed by the Braze platform in near real time. That makes it possible for your brand’s existing technology solutions—think analytics platforms, recommendation engines, etc.—to access and analyze nuanced user engagement data across email, push notification, and other messaging channels, supporting thoughtful iteration and more impactful user outreach.
That connection with your web and mobile applications, which is known as side-by-side (SBS) integrations, is based on a mapping between the Braze platform’s mobile SDKs and the ones associated with your CDP. Separately, data from your backend servers or other third-party systems can be routed to the Braze platform’s REST APIs, resulting in what’s known as a server-to-server (S2S) integration. Let’s dig a little deeper into the differences between these two key integration types and the distinct functionalities they can support:
1. Side-by-Side (SBS) Integrations
For many brands, one of the main advantages of using a CDP is being able to use a single tool to take care of centralizing, tracking, and routing all your user data. However, if your CDP of choice is doing all the data-routing work, it raises the question of why you would even need your engineering team to add the Braze SDK to your company’s mobile and web applications. It’s a great question, and the reason it’s so important has to do with the key role that the Braze SDK plays when it comes to messaging.
At its core, the Braze SDK provides two essential functions:
- Displaying mobile and web messaging channels: The Braze SDK processes and displays the push, in-app message, and Content Card campaigns you create within Braze; without it, you’d lose your ability to display mobile and web messaging at the right time and to the right users.
- Tracking message engagements: The Braze SDK makes it possible to track any interaction a user has with a message, such as a push notification open, a button click, or an in-app message impression.
With a SBS integration, the SDK associated with your chosen CDP are bundled with both the Braze SDK and a mapping file, which serves as an interface between the two SDKs. Your CDP’s integration documentation (mParticle and Segment) should provide detailed instructions on adding the bundled SDKs to your applications. Those instructions will also point your development team to specific Braze code implementation steps for messaging channels, giving you access to all the newest features associated with push, in-app messaging, and Content Cards.
In contrast, all the user behavior data you’re tagging through the CDP’s SDK will automatically be mapped to Braze. Whether you’re tagging user emails, favorite music genres, or abandoned cart events, the CDP methods your developers invoke will be mapped to the equivalent Braze methods for you. What does that look like? Well, for instance, both mParticle’s `mParticle.logEvent()` and Segment’s `analytics.track()` methods are mapped to the Braze `appboy.logCustomEvent` when your developers tag an “abandoned cart” or “song added to playlist” event. Because this data will be passed to Braze, it’s then possible to use this data to trigger responsive push or in-app message campaigns based on these behavioral cues.
2. Server-to-Server (S2S) Integrations
In connection with data that originates from your company’s backend systems or databases, CDPs generally provide server-side libraries that developers can use to forward calls to a host of different companies’ APIs. This makes it possible for you to send user account information from your internal systems to both your BI tools and to Braze without requiring your developers to write multiple scripts that adhere to each tool’s respective API. The only work your team will need to do here is inputting the necessary API credentials into your CDP dashboard to ensure data is passed to the relevant account (see mParticle and Segment documentation).
Passing Braze Engagement Data to a CDP
For Braze customers, our SDK plays an instrumental role in capturing messaging engagement statistics—from data on email clicks, push opens, and the like. This data can provide valuable insight into the effectiveness of your marketing campaigns and can be streamed on an ongoing basis using the Braze platform’s Currents data export feature.
While Currents is often used to stream information into data storage solutions like Amazon S3 or Google Cloud Storage, it also makes it possible to funnel engagement data directly to your chosen CDP. And once it’s there, you have the ability to forward that messaging data to any other element of your tech stack for data synthesis or analysis—allowing for richer customer engagement insights. As with the S2S integration, all you need to get up and running with the feature is inputting several keys into your Braze and CDP dashboards (mParticle and Segment documentation).
Things to Watch Out for When Using Braze With a CDP
While taking advantage of a CDP can support the bi-directional flow of data between Braze and other elements of your tech stack, there are a couple key areas to watch when using them together.
First, data mapping isn’t always apples to apples. Braze and the CDPs we integrate with don’t always support exactly the same data types and concepts, which can result in situations where data doesn’t transfer as expected. For instance, when you’re using a CDP’s event tracking method to record instances where users abandon carts, you might include metadata, which Braze calls “event properties.” These event properties—such as the product IDs associated with items abandoned in a particular cart, the price of each abandoned item, or the quantity of each item—can be structured in different ways depending on what the CDP supports.
But while structuring your event properties as an array of products containing an object for each of the relevant items may well be supported by your CDP and your BI tool, this kind of approach isn’t supported within Braze. As a result, Braze would receive the “abandoned cart” custom event when it occurs, but with the related event properties missing, preventing your marketing team from using that data to support relevant segmentation or personalization needs. In situations like this, you may find it’s necessary to pull in your developers to alter how your systems are logging the event properties. To avoid that, it’s best to be very thoughtful and take advantage of the services your CDP may offer—such as data planning, quality enforcement and validation features—to ensure that you have a cohesive, scalable data strategy and that your data mapping is standardized across your entire stack.
Second, you may find that new features and updates can be delayed. Why? When Braze comes out with new features or releases, the mapping file connecting the CDP’s SDK to the Braze SDK needs to be updated in order to allow shared customers to take advantage of them.
If, for example, Braze releases an Android SDK update that supported a new push notification functionality, your apps would need to reference the most recent version of the Braze SDK to be able to take advantage of the new capabilities. But because the mapping file determines which version of the Braze SDK to reference—and because updates to the most recent version don’t happen automatically—CDPs and the Braze product teams are required to coordinate, update, and QA connections if a new SDK version introduces changes that could result in potential breaks. When choosing a CDP, understanding how closely they partner with Braze will help ensure that you’ll be able to use the Braze platform’s newest features as quickly as possible.
How Braze and CDPs Address Issues
Braze and our CDP partners are very aware of how the two roadblocks mentioned above can potentially cause issues for our shared customers. For that reason, we’ve created cross-organization processes designed to minimize these risks and address issues in a timely manner.
On the product front, Braze product managers have ongoing meetings with our partners at mParticle and Segment to coordinate and plan new feature releases and changes. Additionally, Braze and CDP go-to-market teams are hard at work building joint relationships and systems that can more effectively address immediate customer asks around hot topics like implementation best practices, strategy, and support issues. That said, if you’re already using Braze with a CDP and find yourself running into problems, don’t be afraid to loop in representatives from both sides when necessary.
Ensuring that you’re set up to use Braze and a CDP together effectively doesn’t just happen. But while bumps are possible, we believe that customer processes are often streamlined by a joint integration.
For one thing, CDPs provide thorough data mapping exercises, working with your team to tag relevant user behavior for analysis, attribution, or marketing. That means that when the time comes for your team to add Braze to your tech stack, that user data can often be automatically passed over to the Braze platform to power your team’s personalized messaging campaigns. Beyond tagging, CDPs can also help break down silos in your data infrastructure, connecting different sources of valuable information that don’t traditionally mix well. This data, which could have required a lot of coordination to pass to a new partner like Braze or a BI tool, will now also be accessible. Completing the loop, all the message engagement data that’s captured by the Braze SDK and backend can now be easily made available to the rest of your tech ecosystem, supporting true data agility within your stack.
Ultimately, with the right planning and resource allocation, your development work with the CDP and Braze will help create more holistic views of your customers, allowing for improved personalization, deeper data analysis, and a singular source of truth.
To learn more about how Braze can partner with other technology solutions to support more impactful customer engagement, check out our exclusive look at the six pillars of the Braze Alloys partnership hub.