Coveo Relevance Cloud

Score7.1 out of 10

14 Reviews and Ratings

Community insights

TrustRadius Insights for Coveo Relevance Cloud are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Flexible and Customizable Platform: Users have found Qubit to be a highly flexible and customizable platform, allowing them to enhance the user experience beyond the regular deployment roadmap. Several users appreciate Qubit's capability to personalize the website for different customer segments based on their behavior, launch promotions, implement fixes, and conduct tests.

User-Friendly Search Engine: Coveo is described by users as an intuitive search engine that enables fast information retrieval from multiple sources. Many users highlight its easy implementation and use, as well as the excellent support provided by customer service.

Highly Configurable Search Experience: Users appreciate Coveo Relevance Cloud for its high configurability and flexibility in customizing the search experience for their users. They value the wide range of features and options available such as boosting, filtering, and personalization.

Reviews

4 Reviews

Frictionless Integration with Salesforce

Rating: 10 out of 10

Incentivized

December 23, 2021

Use Cases and Deployment Scope

In general, search and findability isn't the first thing when thinking of Salesforce. We have used Coveo Relevancy Cloud to build Customer Community for clients and integrated it into Knowledge Center Support. The platform performs as expected giving the end-user highly relevant personalized content depending on where we decide to show the results. Internally, we have used it as a platform to build customized applications. The developer toolset is solid and ever-expanding allowing us, as an ISV, to focus on the core functionality of the product we are building instead of worrying about the back-end platform.

Pros

Content Connectors
Out of the box UI Integration into Salesforce
Developer Toolset

Cons

Debugging information about failures in connectors

Likelihood to Recommend

Coveo Relevance Cloud is a great solution to implement into Salesforce to provide Knowledge-Centered Support, Enhancements to a Customer Community, to provide sales aids, or to complement your customized app in Salesforce.

Michael Cizmar

CEO (Chief Executive Officer) in Professional Services at MC+A (11-50 employees)

Vetted Review

4 years of experience

View profile

Does its job, but is lacking

Rating: 8 out of 10

Incentivized

June 14, 2019

Use Cases and Deployment Scope

Coveo is currently implemented within our company's ecosystem, which is a portal where employees can read about current company news, recent events, and access a number of tools provided for our day-to-day work. Many files are saved onto this portal, and employees can search within the portal to find what they need. This is where we use Coveo - they are our primary search engines within this portal. They help dig through our massive database of files.

Pros

Coveo is fast, search results come up quick (though it's not always great).
Not much complexity to run.
Coveo is implemented within our portal and doesn't require extra steps to use it.

Cons

Coveo does its job but is lacking.
The results displayed by Coveo are not always relevant.
The results displayed by Coveo are not sorted, nor is there an option to sort.
The results displayed by Coveo are not location-specific, so results not relevant to my area or country gets shown.

Likelihood to Recommend

Coveo is well-suited for larger companies that have a huge amount of files sitting its databases. For a company of more than 100K employees, Coveo does a nice job of sifting through massive piles of data. For example, if I wanted to find something about 401K matches, I could type that into the Coveo search bar on our portal and it would give me all the files in our system about investing in 401K in our company. The results don't take too long to come up as well.

Verified User

Team Lead in Professional Services (10,001+ employees)

Vetted Review

3 years of experience

A little pricy but not too shabby

Rating: 7 out of 10

Incentivized

August 5, 2014

Use Cases and Deployment Scope

We implemented Coveo facets and index capabilities for several web based applications that we built for our clients in Sitecore CMS. We primarily use this product to support search pages which can find and filter content in Sitecore and display results in a customized way.
This product is used by a few of our clients across widely different verticals. Our application developers use the product most heavily.

Pros

Searching a large set of documents is very fast
Support for faceted searching
Supports synonyms through an admin panel or via an external file
Out-of-box controls for rendering search, results, and faceting.
Customization allows for more flexible implementations
.NET hooks exist allowing code to be injected into its indexing process. This allows for more advanced taxonomy indexing (for example inspecting semantic information during indexing)
Items published via Sitecore are automatically indexed (within a minute or two of publish time)
Out-of-box support for ranking files attached to pages (PDFs, DOCs, etc) based on search term relevancy
Supports ranking certain file types above others (giving PDFs more weight than DOCs, etc)
Out-of-box support for crawling web pages from multiple sources. Each source can be configured with different crawl frequencies.
Coveo 7 introduces a JavaScript search interface in conjunction with a new REST API that you can use as an alternative to the out-of-the-box Coveo .NET search interfaces. This is also customizable and even supports templating engines like mustache and underscore.
They have a StackOverflow-like forum where you can get assistance from the community: https://answers.coveo.com/ .

Cons

It would be great if Coveo 6 allowed you to rebuild indexes from a certain subtree instead of needing to rebuild the entire tree to see changes. This functionality was added in Coveo 7 and is very useful.
In Coveo 6, integration with Sitecore is more difficult than one would expect. This integration is much improved in Coveo 7.
I have seen cases where an exception thrown when crawling a specific document will cause the indexing to stop completely. I believe this only happens in implementations using custom faceting but it could be handled more efficiently if the trouble document was skipped and the indexing could continue.
Relevancy ranking editor is good but not as powerful as GSA. GSA offers a self-learning scorer which automatically analyzes user behavior and the specific links that users click on for specific queries to fine tune relevance and scoring.
We've ran into issues on multiple clients with Sitecore items being indexed multiple times in Sitecore 7 and Coveo 7. The fix Coveo suggested was to upgrade our Sitecore version and Coveo but unfortunately this didn't resolve our issue. After months of testing we were finally able to resolve this by implementing our own CoveoItemCrawler to get around the issue (based on https://developers.coveo.com/display/public/SC201404/Items+in+the+Same+Language+Gets+Indexed+Multiple+Times;jsessionid=3C1A2AE33540E0A0B8BB52BA3A64AF70).
Integration with RabbitMQ in Coveo 7 seems error prone. We often see the error "The AMQP operation was interrupted" and on occasion, need to restart the Coveo service to get this operating again. In some extreme cases, we have also had to restart the server because of issues when attempting to restart the Coveo service.

Likelihood to Recommend

Coveo is well suited to crawling large collections of sitecore items and organizing content based off of templates and folder structures. Facets allow you to group related content regardless of their position in the tree which is a very useful feature for most search implementations. The price can be pretty expensive as in some cases, you may have to pay for each document which is indexed. The price/features tradeoff is probably the biggest decision to make.

Rondel Ward

Web Developer in Research & Development at Velir (51-200 employees)

Vetted Review

1 year of experience

Coveo Enterprise Review

Rating: 7 out of 10

Incentivized

July 18, 2014

Use Cases and Deployment Scope

Coveo was used at my previous organization as its enterprise search platform and customer facing search. My program focus was on internal search, where we leveraged Coveo to index disparate data sources across the enterprise to allow users one central place to search for information. We were able to embed Coveo into multiple systems so the search experience was consistent across these applications.

Pros

Good library of connectors to enterprise repositories including MS SharePoint, Exchange, Confluence. OOTB using the Open Connector API administrators were fairly easily be able to index content repositories.
Good security integration with existing repositories.

Cons

UI changes were cumbersome and timely to make changes to based on business requirements and user feedback. We were not able to optimize in the UI due to the constraints.
Analytics in the version we had were very poor. UI was built in Silverlight with no exportable version to be able to perform further analysis of data. Many product suggestions around additional metrics needed.
We struggled around data ranking and relevance due to the amount of unstructured data that we were indexing. This caused user adoption issues. This service and guidance was something that we were never really able to get from Coveo with my time using the product. The relevance controls were very simplistic and did not give us much control.

Likelihood to Recommend

Make sure you have a roadmap of systems that you plan to integrate with. Custom connectors should be factored in. Highly suggest reviewing their analytics and insights engine - this area of the product was very weak when we were using it.

Lauren Jones, PMP

Project Manager at Slalom Consulting (10,001+ employees)

Vetted Review

3 years of experience

Loading Reviews List....

A little pricy but not too shabby

Rating: 7 out of 10

Incentivized

August 5, 2014

Use Cases and Deployment Scope

Pros

Searching a large set of documents is very fast
Support for faceted searching
Supports synonyms through an admin panel or via an external file
Out-of-box controls for rendering search, results, and faceting.
Customization allows for more flexible implementations
.NET hooks exist allowing code to be injected into its indexing process. This allows for more advanced taxonomy indexing (for example inspecting semantic information during indexing)
Items published via Sitecore are automatically indexed (within a minute or two of publish time)
Out-of-box support for ranking files attached to pages (PDFs, DOCs, etc) based on search term relevancy
Supports ranking certain file types above others (giving PDFs more weight than DOCs, etc)
Out-of-box support for crawling web pages from multiple sources. Each source can be configured with different crawl frequencies.
Coveo 7 introduces a JavaScript search interface in conjunction with a new REST API that you can use as an alternative to the out-of-the-box Coveo .NET search interfaces. This is also customizable and even supports templating engines like mustache and underscore.
They have a StackOverflow-like forum where you can get assistance from the community: https://answers.coveo.com/ .

Cons

It would be great if Coveo 6 allowed you to rebuild indexes from a certain subtree instead of needing to rebuild the entire tree to see changes. This functionality was added in Coveo 7 and is very useful.
In Coveo 6, integration with Sitecore is more difficult than one would expect. This integration is much improved in Coveo 7.
I have seen cases where an exception thrown when crawling a specific document will cause the indexing to stop completely. I believe this only happens in implementations using custom faceting but it could be handled more efficiently if the trouble document was skipped and the indexing could continue.
Relevancy ranking editor is good but not as powerful as GSA. GSA offers a self-learning scorer which automatically analyzes user behavior and the specific links that users click on for specific queries to fine tune relevance and scoring.
We've ran into issues on multiple clients with Sitecore items being indexed multiple times in Sitecore 7 and Coveo 7. The fix Coveo suggested was to upgrade our Sitecore version and Coveo but unfortunately this didn't resolve our issue. After months of testing we were finally able to resolve this by implementing our own CoveoItemCrawler to get around the issue (based on https://developers.coveo.com/display/public/SC201404/Items+in+the+Same+Language+Gets+Indexed+Multiple+Times;jsessionid=3C1A2AE33540E0A0B8BB52BA3A64AF70).
Integration with RabbitMQ in Coveo 7 seems error prone. We often see the error "The AMQP operation was interrupted" and on occasion, need to restart the Coveo service to get this operating again. In some extreme cases, we have also had to restart the server because of issues when attempting to restart the Coveo service.

Likelihood to Recommend

Rondel Ward

Web Developer in Research & Development at Velir (51-200 employees)

Vetted Review

1 year of experience