Braze is a customer engagement platform that enables relevant and memorable experiences between consumers and brands. With Braze, global brands can ingest and process customer data in real time, orchestrate and optimize contextually relevant, cross-channel marketing campaigns.
N/A
Drupal
Score 7.0 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
Braze is a fantastic tool if you're looking to build a large number of CRM journeys using complex canvas structures and maximising use of customer data to segment and personalise. There are numerous tools to ensure each channel is maximising impact and engagement. Braze offers great features for testing, managing message frequency and control groups and using dynamic attributes and liquid code. If you're looking to limit your use to single-send campaigns with no or few automations, I don't think this is the right tool. From my experience, many Braze users also use external tools for analytics rather than Braze's native analytics.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Canvas feature has been really good for creating customer journey paths and long-term messaging campaigns.
They have been addressing feature requests to continue to improve the Canvas feature. One of the simplest but most-handy features is allowing Delay steps wait for a very specific date on a calendar -- so you can plan seasonal campaigns or when you have evergreen-style drip campaigns it allows for avoiding public holidays/etc.
The catalog feature provides a lot of use-cases and flexibility for personalizing comms or customizing comms for whitelabeled versions of our standard comms (for our B2B2C scenarios).
We use the catalog as a repository of our B2B2C brand info, messaging customization - it basically allows us to offer a whitelabeled configurable version of our optimized automated in-life comms in the branding of our b2b customers.
Enabling GIF/videos to be directly uploaded on to Braze's platform
Easier way of creating canvases; right now it is too complex for someone new who is starting off in the company to understand what things do and where things are
Ability to track duplicate user profiles within the entire audience segment
Automated deduplicating email addresses/phone numbers in each targeting segment; right now it's done manually after extracting csv files
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
We are on a mission for an omnichannel experience for our customers and are already making good progress with Braze able to fully support and optimise this
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
It is an easy-to-understand platform, thanks to its design and accessibility. You can, for example, easily find any users and their data, check exact volumes of segments, follow the history of messages sent, and create reports. We can connect Braze with other platforms for analysis or email design (Snowflake, Hightouch, Stripo...).
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
Very responsive and helpful on simple questions, but not great other than that. They do not have a way for the customer/user to escalate a ticket. You have to contact your rep and in some cases, they don't respond within 24 hours so you have no idea if they have escalated it. There is no phone number for an urgent issue - you have to rely on email
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
It's really well explained, there are lots of documentation about all topics. When we want to perform in a specific area, there are always a dedicated path. For each new feature, there is always some videos explaining the purpose and the new functionalities. Also I used to do the certification which allows me to show my achievements in my business environment.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Braze is just the best one when it comes to aesthetics and usability, which matter when you're working every day, making complex or even simple changes to highly contextual campaigns for multiple stakeholders. Even without following tutorials, you just get it instantly and start crafting journeys very quickly. And they continue to keep adding new features at a rapid pace, so credit where it's due.
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
