Bloomreach personalizes the customer experience for brands around the world. Loomi AI, its agentic platform, understands customers in context — then tailors their experience in real time. Connected to applications at every touchpoint, Loomi AI brings personalization to life across email, web,…
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.
N/A
Pricing
Bloomreach
Drupal
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Bloomreach
Drupal
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Bloomreach pricing is quote-based. Bloomreach pricing is customized to the number of customers served, product catalog size, and the number of events executed – such as how many emails or SMS messages are sent.
One scenario Bloomreach is particularly suited for is omnichannel abandonment campaigns. We have scenarios that look whether a customer has been into one of our stores, and then if they are subscribed, we can send them more information about the products they have viewed. That wouldn't be possible without Bloomreach. Another scenario that Bloomreach is well suited for is price drop - we can alert users that an item they've viewed has dropped in price, and this has been a really successful campaign for us.
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.
The product recommendations engine allows for us to create a personalised experience for every customer across the 3m emails we send each month. This ensure that our customers remain connected to our brand.
The customer data platform attached to Bloomreach Composable Personalization Cloud provides an all-in-one solution for our business intelligence needs. Allowing up-to-date purchasing, behaviour, and engagement reporting from our email to website activity.
The ability to integrate with Meta and other paid ad formats allows for us to create a connected omnichannel experience for users, ensuring we are providing the right message, to the right person, at the right time, in the right place.
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 extremely satisfied with Bloomreach. It is a central and indispensable pillar of our personalization and data-driven marketing strategy. The platform provides us with unparalleled scalability across 27 countries and guarantees high availability and stable performance, even when working with an enormous volume of data.The fact that the platform is intuitive and allows a wide range of our teams (from CRM to UX) to work effectively with personalization significantly reduces our dependence on IT support and accelerates campaign deployment.Given the robustness of the architecture and the positive results we are generating across channels, renewing the contract is a logical step to ensure our future organic growth.
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.
In my time working with Bloomreach Commerce Experience Cloud, I always liked to work with it. It is crucial that you get support from experts from the beginning to show you how to work with the vast amount of options and activities to choose from. The learning curve is also well-rounded because of its user-friendly interface and highly skilled customer support.
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.
The platform is generally reliable - major outages are rare and most day-to-day campaign operations run without interruption. Where it dips: occasional slowdowns in the analytics dashboard during peak loads, and sometimes scenario executions get delayed without clear explanation. The real-time event processing is mostly solids. Overall uptime is strong - it is not something that keeps me up at night, but it is not flawless either.
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).
Performance in Bloomreach Content is quite good but you need to be ready. Your implementation should follow all the good practices (avoid crazy patterns) and the environment setup should be the right one. With all that, Bloomreach's performance is quite solid. Our usage makes use of complex queries and most of them are really quick. Only when you need something really complex and you aggregate queries that should be separated you would get slower results (but then again, that is not a good practice for any platform).
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.
The project team consistently delivers excellent collaboration and is always available whenever assistance is needed. Their responsiveness and commitment make working together smooth and efficient. Bloomreach support, which is included for free in the platform, can also be quite useful, especially for quick clarifications. However, the quality and speed of their responses can sometimes vary, depending on the issue.
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.
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%
Bloomreach is far superior than SFMC as that platform requires too much technical knowledge. Ometria is very good and I would say is quite similar to Bloomreach although I would say Ometria is a smaller company. Dotdigital is also very powerful but not more so than Bloomreach. This being said, Dotdigital and HubSpot does have telephone support which is amazing and something I would like to see from Bloomreach in future or at least shorter wait times for customer support live chat.
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.
there is an option of multiple projects per organisation, customers and assets can be copied across. Multiple sites can be managed in one project, different activities organized under initiatives. Splitting work into sensible units is therefore well possible. The billing is based on number of tracked and number of stored events, no package-based deals. It should therefore be well scalable from a small e-store to a large corporation.
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.
