Braze vs Oracle CX Marketing (formerly Oracle Marketing Cloud)

• Personalized customer journey
• Consolidation of marketing tools to bring multi channel communications under one roof and allowing each of them to talk to each other.
• The Braze community. This not only helps with idea generation, but makes a great place to network and grow your team.
• The Customer Success team is world class. They reply to anything and everything we send them promptly and with actual answers.

Read full review

• We are managing marketing via emails using it and hence I can claim that its email marketing is transcendent.
• We can interpret and analyze data as well.
• The insight it provides and analytics are quite helpful for us.
• The level of Flexibility.
• Mobile access.

Read full review

• If you do not have a solid understanding of your product instrumentation and Braze, it will be difficult to be effective with it initially.
• You need to spend some time learning about the platform as some aspects are not self-explanatory so you need to rely on other documentation or guidelines they have (i.e. how to find your instrumentations - need to find it by adding quotations marks, etc).

Read full review

• Integration options outside of auto-syncs. I am currently having an issue trying to find an adapter to use with Eloqua to API into our data warehouse but keep the functionality on the Eloqua side.
• To provide more transparency and visual details of the syncs (integrations of outside data) from any other system that is feeding Eloqua, like what is being updated or changed, better explanations of errors, drill down to newly created records.
• Custom Objects - Need to have a way to create CDOs outside of just form submissions and uploading of lists, like if you needed to import a file nightly to feed that CDO data but automate the import and make sure it maps to a contact record.
• Import of data from a file on SFTP - There is no way to filter or create logic to control what is being fed into Eloqua. Currently, that manipulation has to be done by the IT side first. Less flexibility.
• Better auditing capabilities within the canvas. meaning, sometimes if something is changed or not working the problem may not necessarily show up in immediately, the pattern could take a while to present itself. For example, the feeders into the program. If there is a problem, I don't know that maybe contacts are not entering the program until we do reporting that month and realize there was a lull of contacts going through. Then we have a whole month of missed records or other potential data issues. When you get do large and your Eloqua machine is very robust, the harder it is to see everything
• Be able to add more than 250 custom contact records. That definitely inhibits my organization in how we need to use that record.

Read full review

• Positive: A growth hacking experiment was proven successful in nudging users who abandoned their cart after checking out with a product/service and leaving their chart or 24 hours.
• Positive: A growth hacking experiment was proven successful in nudging users whose credit card failed when trying to upgrade to a paid account.
• Negative: With the plethora of teams (disciplines / business units / markets) with access to braze, it's easy to accidentally over-nurture users.

Read full review

• We are able to use it to help our clients scale through testing
• We have been able to measure the impact of our events and sales events so we can determine which events to continue in the future and determine future investment
• Launch a new brand out of Eloqua and measure awareness

Read full review