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
Elasticsearch
Score 8.6 out of 10
N/A
Elasticsearch is an enterprise search tool from Elastic in Mountain View, California.
$16
per month
Pricing
Bloomreach Composable Personalization Cloud
Elasticsearch
Editions & Modules
No answers on this topic
Standard
$16.00
per month
Gold
$19.00
per month
Platinum
$22.00
per month
Enterprise
Contact Sales
Offerings
Pricing Offerings
Bloomreach Composable Personalization Cloud
Elasticsearch
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Required
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.
DUe to AI based algo. Elastic search is just a search based platform and it doesnt provide the feature bloomreach experience provides with content management which is completely cloud based. Also bloomreach merchadizing tools and SEO solutions keep them apart from the other …
Automatization has Bloomreach Commerce Experience Cloud on very high level, we are able to set up over 20 different fully automatized long term campaigns that require very few adjustments over time and we are working on more and more. Also segmentations is on amazing level. I never worked with such an accurate level of customer segmentation. Where I think Bloomreach Commerce Experience Cloud could be better is reporting, some detailed lookups for me are difficult to set even as a data analyst. I hoped Loome would help me with that, but since Notino has so many custom adjustments, Loome does not work very well with them.
Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.
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
As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.
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
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
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.
To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
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
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
There is always somebody available for help. Their answers and tips are on spot, or when they don't know the answer they will make sure to get the answer somewhere. Everybody is always checking if I got my answer or if my problem solved. I really appreciate that. Thank you!
We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
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.
As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
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.
We have had great luck with implementing Elasticsearch for our search and analytics use cases.
While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
