Integrating with Braze is a worth-while process. But you’re smart. You’re here. Clearly you already know that!
But what you probably don’t know was that you and your engineers/developers are about to go on a journey together that requires technical expertise, strategic planning, and consistent communication that will help you coordinate between the two!
Please note that this doesn’t count for email. Check that out in the Email Set Up Guide.
The Technical Side of the Integration Process
You may find yourself thinking “My engineers are magical! They can do anything, so I usually just leave them to it!” And they probably are and probably can! But there’s no reason why you shouldn’t know what they’re doing behind the scenes. In fact, it would help the entire process if you knew when to jump in with information and what to look for when they say “Can you send me the API Key and Custom Endpoint?”.
“So what are they doing when they integrate Braze with my app or site?”
Glad you asked!
Step 1: They Implement the Braze SDK
The Braze SDK (Software Development Kit) is how we send and get information to and from your app or site. Your engineers are, essentially, tying our apps together. To do this, they need a few pieces of key information:
- The API Keys
- Your Endpoint
You can either give this information to them directly, or you can give them access to Braze by creating an account for them.
Please ensure that you and your engineer don’t unknowingly or unintentionally change the company’s credentials in Braze, as this could cause issues during the implementation process or lock one or more of you out of your accounts.
Step 2: They Implement Your Desired Messaging Channels
Braze has many options for getting in touch with your customers/users, and each requires it’s own set up or tweaking to work the way you want. This is where communication with your engineers becomes critical.
Be sure to tell your engineers which channels you want to use to ensure that implementation is done efficiently and in proper order.
|In-App Messages||Requires SDK implementation as well as these channel-specific steps.|
|News Feed||This works upon proper implementation and is SDK required.|
|Push||Requires SDK implementation to provide proper handling around messaging credentials and push tokens.|
|This is an entirely different process. Check that out in our Email Setup section.|
Step 3: They Set Up Your Data
Braze isn’t a one-trick pony. This isn’t about just sending emails or sending push. This is about creating personalized customer journeys that are unique for every user/customer. The customer journeys are based on their actions within your app or site and you get to define what those are! However, what good is that definition if you can’t track, record, compile, and act on them. That’s your engineer’s next task - ensure that actions taken within your app or site are picked up by Braze.
So, what do you need to do to get them this information?
- Work with your marketing team to define campaigns, goals, attributes, and events that you need to track. Define those use cases, share them with your teams.
- Define your Custom Data Requirements (Attributes, Events, etc.).
- From there, discuss how that data should be tracked (triggered through the SDK, etc.).
- Define how many App Groups you need. They’ll need to know how to test and configure these.
Step 4: They Customize Based on What You Want
If you want things like API Triggered launching and Connected Content, discuss that with both your Braze contact and your engineers to ensure that you’ll be able to get data that lives outside of your app and Braze into your messages.
Step 5: QA Your Implementation
Keep in mind that the Implementation Finish Line isn’t also the green light to send a million messages at once! Sending a million push might break your app if every customer clicks the same link at once - we recommend discussing what your capacity of your internal set up is for handling requests from Braze before clicking that Send button. Then, you can set your rate limiting based on that.
Now that you’re more familiar with the integration process, check out the next article for suggestions on where to go next!