ⓘ Changes are on the way!
Braze Bonfire is read-only from April 6–April 13, 2026. 

Braze Bonfire is getting an upgrade. From April 6 through April 13, 2026, Bonfire will be read-only while we tinker behind the scenes to improve your experience in the community. Read more.

Google Tag Manager

Forum Discussion

Kaila_Widmann's avatar
Kaila_Widmann
Supporter
10 months ago

Seeking Braze implementation insights and best practices

Our team is currently transitioning our customer engagement platform to Braze, and we're looking to connect with fellow product or project managers who have gone through this journey. We'd appreciat...
experimentation
Inspiration
LiorPeleg's avatar
LiorPeleg
Expert
10 months ago

Feel free to reach out if you have any questions :)

In the meantime, here are a few points that might help guide you:

  1. Are you migrating from another platform, or is this your first time using a marketing automation system?

    This makes a big difference - if you’re switching from another system, you likely already have a data structure, customer journeys, etc. In that case, you probably know what works, what’s missing in terms of data, events, and so on.

    If there’s a deadline for replacing your existing system, make sure to plan everything carefully so you don’t end up without active campaigns or journeys during the transition.

    If you’ve never used a system before, it’s important to plan your customer journeys in advance and define the types of data and events you’ll need to sync with Braze to support those journeys.

    I highly recommend checking out the official Braze courses - they’re a great way to get familiar with the platform and understand its capabilities before implementation starts.

  2. Get your tech and data teams involved early.

    One of the common pitfalls is that these teams are brought in too late, often after the decision has been made, and only when integration work begins. That usually causes unnecessary delays.

    Make sure to involve them as early as possible. Share the API/SDK documentation with them so they can estimate the required effort and allocate time in advance.


    If you’d like to share more about your company and what you’re planning to do with Braze, I’d be happy to give you more tailored tips and suggestions based on your specific use case.
Kaila_Widmann's avatar
Kaila_Widmann
Supporter
10 months ago

Thanks for these insights! We are transitioning from another platform, but we are viewing our data structure as a clean slate in the transition. We did involve our data and engineering teams from the beginning, so seems like we're off to a good start! I'll follow up here if more questions come up as we continue the transition. Thanks!

  • LiorPeleg's avatar
    LiorPeleg
    Expert
    10 months ago

    It’s great that you’re viewing your data structure as a clean slate during the transition.
    Many companies simply copy everything over as-is when switching platforms, without considering the differences between systems or leveraging the lessons learned from working with customer journeys in their previous tools.

    A transition like this is the perfect opportunity to evaluate what worked well and should be preserved - and what needs to be changed or improved in the new platform.