web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Braze Connector Integr...
Customer experience | Sales, Customer Insights,...
Answered

Braze Connector Integration

(2) ShareShare
ReportReport
Posted on by Bill Ryan 8

Hello:

We're looking to use the OOB Braze connector.  We can successfully create the connection and have no issue there, but running into two issues:

1-When we setup the export, all of the attributes on the Customer Profile are part of it.  Braze charges by the attribute and most of the attributes we have in the customer profile do  not need to be sent.  So assume there's 30 attributes on the Profile, only 10 of them are needed in Braze. Is there a way to only send the 10 we need?
2-Braze has some built in default attributes, such as first_name.  These are case sensitive and have to match exactly.  Our value on the customer profile is FirstName.  I know we can change the attribute name, but changing each of those to match seems awkward and it will show on the customer profile cards and elsewhere like that which is undesirable.

From what we can see, there's an 'all or nothing on the attributes and  I don't see any way to customize the mappings between CI Export and Braze.  Is there a way to map and just select a subset of attributes?

I have the same question (0)
  • Verified answer
    PhilippeK Profile Picture
    PhilippeK 260 on at
    RE: Braze Connector Integration

    Hi Bill,

    Thanks for your questions around the Braze connector and great to see that the connector seems to work, albeit with some caveats.

    On your first question: When setting up the export, you should be able to select the following 5 attributes: “email” and “Braze customer ID” – both are mandatory, and optional you could select “First Name”, “Last Name”, “Phone”. If I understand you correctly you are saying that although you select some or all of those 5 attributes, all of the attributes are landing in Braze? That shouldn’t be the case and would indicate their might be a bug. Only the data attributes you select should be sent to Braze. Please let me know if my understanding is correctly.

    On your second question: you shouldn’t need to change the naming of your attributes in CI to enable it matching on Braze side. We only need to know which attribute we should match to which attribute in Braze. Do you have an example of when this fails?

    Thanks,

    Phil

  • Bill Ryan Profile Picture
    Bill Ryan 8 on at
    RE: Braze Connector Integration

    Philippek - thank you for the answer.  So I was able to find those 4 for mapping, that helps tremendously.  So to be  clear about the ask, there are several attributes that they need in Braze that are *not* one of the 5 we have a choice for. When i try to add additional attributes they aren't available.  But yes, the problem is, there are like 50+ attributes in the profile.  They only want 13 of them. And of those 13, there are 3 that weren't named in a way that matched braze (first_name, last_name and email) - so the mapping will address that piece. But we can't map anything else so we're seemingly stuck in a situation b/c of there's a cost per attribute/cell in braze, so if all 50+ go over, it's all wasted money on their part, or if we can only map 5 then we  have like 10 attributes short that won't go over.

    The name mapping answers a big part of this, definitely appreciate that. FWIW it doesn't fail though, there's just no way to map them so I figured I'd ask beforehand.  Thanks again!

  • Verified answer
    PhilippeK Profile Picture
    PhilippeK 260 on at
    RE: Braze Connector Integration

    Hi Ryan,

    The attributes you can send over at the moment are "hardcoded" so they can't be changed or extended at will. Moving forward we are looking into how this approach can be made more flexible so that customers have more options to extend as needed. There is no ETA for this yet.

    Nevertheless, since you need to send at least the mandatory attributes (and map those when configuring the export), we will never send more than those attributes that you configured, so even if you have 50+ attributes, we will never send all of them over. So, while you or your customer are safe from wasting money by sending too many attributes, they are still at the moment limited by the amount of attributes they can actually send.

    Let me know if you have additional questions, happy to help!

    Thanks,

    Phil

  • Bill Ryan Profile Picture
    Bill Ryan 8 on at
    RE: Braze Connector Integration

    Phil - THANK YOU FOR THIS.  I had erroneously assumed all would go over as custom attributes and b/c of the cost that would be a huge problem.  So if I'm following you correctly, basically the most that can go over will be the mapped ones.That's very helpful.  Thanks again

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 120 Super User 2025 Season 2

#2
MVP-Daniyal Khaleel Profile Picture

MVP-Daniyal Khaleel 119

#3
Erin Lubben Profile Picture

Erin Lubben 73

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans