Any braze/amplitude power users?!

We are long time users of Braze and finally just got access to Amplitude at a new company! I've heard great things about using Amplitude to analyze Braze campaigns, but don't know where to begin. Can anyone provide any insight? Bonus points if you're willing to discuss over a call.

Find more posts tagged with

Currents

Comments

DavidO

Hey @csfernandez74

Not going to say I'm an Amplitude power user but we have our Braze instance connected via currents as Amplitude is our app's main source of truth. I'm not the right person to discuss the technical details of connecting Amplitude and passing the data but here is what I can tell you.

We pass our Braze events such as email opens, IAM clicks and so forth back to Amplitude where we can compare them to events and property data that is already collected in Amplitude. Amplitude is our main source of event data and captures more events than we capture in Braze, so it makes sense to pass Braze data back to Amplitude for us as we can analyze a broader range of data and compare it to other teams who use Amplitude for their work, such as PMs and engineering.

One thing to be aware of is that when filtering by canvas or step in Amplitude, we found it can be very hard to tell what is what if every step is called 'Delay' or 'Onboarding 1' for example. So, we use quite lengthy clear naming conventions for the canvas name and canvas steps, which looks a bit messy in Braze but makes it so much easier to work with in Amplitude. e.g. a canvas step might be 'Onboarding_AllUsers_Email1' but it is clear in Amplitude what step we are looking at.

AllanHeoFNM

From our experience, the first few steps that anyone can get started with are:

1. Sync Braze to Amplitude

2. Read through every data schema one by one. There seems to be a ton of data available, but once you start reading through it, you realize many many tables are very repetitive, and you start to get familiar with the fields available in Amplitude.

Every single message interaction is logged, so it's a matter of grouping by Campaign IDs, and filtering for users who performed certain actions.

@DavidO's point about naming conventions is crucial as well!

Here's the Braze docs that we've read through hundreds of times: https://www.braze.com/docs/user_guide/data/braze_currents/event_glossary/message_engagement_events/?tab=amplitude

marionb

Hi

We use the current Braze x Amplitude too. Same as David, we mostly use it to be able to do all our analytics dashboards in Amplitude. We send all the campaigns/canvases events (email sent, email opened, campaign control, canvas entry, experiment step etc). Even if it is not always easy, Amplitude enable us to go deeper than Braze (more precise funnels, flexible date range, use of filters like event properties, user properties etc) and we also have more data in Amplitude.

I confirm that naming the steps (and campaign variants) with details is absolutely needed to be able to analyze better in Amplitude. I hope Braze will add a button to be able to copy a name of a step to paste more easily in Amplitude.

We also use it a lot to create some cohorts (segments) that we sync to Braze (realtime, daily, once). Since there are some events we don't send to Braze (to save some data points) but that we have in Amplitude, we can create more precise cohorts and we can use it in Amplitude for analytics than. We don't need to export/imports csv.

To be able to better understand what campaigns a user received months ago it is helpful and better in Amplitude. To see if the campaign/canvas has been sent for the expected reason as well.