Bloomreach personalizes the e-commerce experience. Its data engine unifies real-time customer and product data so businesses understand what customers really want. By connecting that understanding to every channel, the e-commerce experience becomes limitless — reflecting a changing customer as they shop. Amplified by the speed and scale of Loomi, Bloomreach's AI for e-commerce, this creates endless new paths to purchase. Bloomreach products include:
N/A
Drupal
Score 8.2 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.
Bloomreach has great support. So when you feel a bit lost or stuck on a problem, there is always somebody to help you out with your problem. Not just in a chat, but also on zoom call where you can explain or show your problem. Also they always check if the problem is solved the other day and if everything is working as I need.
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
All in one. We have experience working with other CDP/Marketing suites and it is really difficult to connect their different modules. Bloomreach Engagement has been built to be a single product which makes everything easy to use
Fast and real-time. Other platforms struggle with getting real-time volumes or segmenting based on real-time events, that is not the case with Bloomreach Engagement
GCP partnership. Being deployed over GCP and having BigQuery as raw data export makes really easy to expand and connect with existing stacks
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
While Importing the offline data, sometimes the auto detection is failed to detect the csv file
While we import with wrong mapping, even after pressing escape before the import starts, its not cancelling the import. it start running. It would be great if it stops the import
it would be great if we receive email for successfully finished imports too
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
So far, Hippo is our ideal tool given its use of open standards which helps us to have a clear overview of what's coming next in the future Hippo releases. We are very confident in the future-readiness of the product
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.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
99% of the time the site is available for when we need to use. With any cloud based software there will be occasion that there is an outage but this is communicated effectively and dealt with quickly. This has never got in the way of what we need to do in our day to day work and wouldn't be thought of as a problem
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).
The search API is very fast (150ms), even considering we have nearly 2 million products in our catalog. The console pages where you do your configuration, add ranking rules and synonyms are sometimes a bit slower to load, but your customer would not notice any of that. The reports pages are also not the fastest, but definitely okay
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.
When I get through to support they are absolutely amazing but I think sometimes the wait can be too long. From experience I also know HubSpot and Dotdigital allow for live calls or call-backs which gives you that extra layer of support and satisfaction. That alone would have taken this score to a 9.
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 a really easy to use platform compared to other CRM systems and allow faster integration to the other data sources. It allowed deduping services and the ammonization feature for data protection is really easy to set up which fields contain personal information and therefore remove the data when a customer request it.
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
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.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
