Coveo AI-Relevance Platform: Enterprise AI Search and Answers

My main use case for Coveo was to index the search results on our search pages like insights, listings, articles, stories, and other content.

One specific example of how Coveo worked for one of our search pages is when we had an external database managed by another team. We used to import those database items into a Sitecore master database, and while those items were getting published, they would also get indexed in Coveo, allowing us to search for specific items using their item ID or listing name, which would then appear in the search results managed by Coveo.

I faced some challenges regarding the accuracy of the search results with Coveo. For instance, if we searched for properties, listings would appear based on the property names, but the search accuracy wasn't always perfect. Suggestions in Coveo, such as office spaces, would yield popular office options that were cost-effective.

Coveo positively impacted my organization because the majority of our users who visit our website primarily use the search pages, making it a major functionality of our site.

I definitely noticed an increase in user satisfaction and improved search accuracy as a result of using Coveo.

The best feature Coveo offers is that items imported into the master database of Sitecore get indexed in Coveo very quickly, probably under a minute, allowing those items to be visible on the search page promptly.

The speed of Coveo's indexing helped our business users in many ways, specifically by ensuring their business campaigns and client expectations weren't negatively impacted due to slow search results.

The integration of Coveo with Sitecore is very good, particularly regarding implementation, customization, widgets, maps, and facets.

I believe Coveo can be improved by integrating artificial intelligence features. For example, if I type 'office spaces' looking for cheap and average sizes, improving AI could provide better search results based on user search history.

I have been using Coveo for the last 3.9 years, and recently we have replaced Coveo search with a Sitecore search in our project.

Coveo has never experienced downtime or issues in my experience.

Coveo is definitely scalable and can handle large volumes of data and users.

I reached out to Coveo's customer support many times, and it was one of the best experiences I had with their support team. I would rate the customer support as a nine on a scale of one to ten.

We are currently using Sitecore search in place of Coveo, which we recently replaced.

I do not have metrics related to return on investment with Coveo currently.

I didn't work on the licensing part of Coveo because I was an employee and not the manager.

Coveo was the first option in my mind before making a choice.

The quick indexing into the search results is the best scenario I faced with Coveo. In terms of accuracy and reliability of output, I believe Coveo is probably the best in market scenarios. Coveo is deployed in my organization as software as a service and integrates with my code base directly. I am not sure about Coveo's governance and security regarding its AI capabilities. I would rate Coveo an eight on a scale of one to ten.

Coveo's main use case revolves around content indexing and search integration, primarily when working with Sitecore as a CMS implementation.

In our Sitecore CMS implementation, we have very large content volumes, and Coveo helped us significantly with relevance through the use of indexing, query pipelines, and security features. Relevance was the most valuable feature for us. We were able to determine what content was shown to users and which was not, so Coveo provided substantial value from a relevance perspective.

From a business perspective, Coveo's biggest value is having more control over how users discover content, including relevance, ranking, personalization, and analytics, which can help improve the search experience without requiring a developer to change application code for every small adjustment. The exact value obviously depends on how well the organization configures and uses those capabilities.

Before moving to Coveo, we had metrics of user clicks around two million, but after we went live with Coveo, user clicks and all view analytics jumped up over 3.5 million, which was a significant upgrade after implementing Coveo.

In my view, the best feature that Coveo offers is relevance, which is one of the strongest areas. You have more control than you would typically get with a basic search implementation, particularly through query pipelines and ranking configuration. The important thing is that good relevance still requires proper configuration and understanding of your content, so I would not expect the platform to solve every relevance problem automatically.

I find query pipelines particularly useful because they give you a way to influence search behavior based on the context of the query without having to pull that logic into your application. For example, you can apply different ranking on query behavior depending on the situation, which provides a good separation between the application and search configuration.

Recently, I have been exposed to working with Coveo Atomic while working on the headless Sitecore implementation, and I appreciate the Atomic library because it provides reusable search components, so you don't have to build every part of the search interface from scratch. It makes the front-end integration faster while still allowing the developer to customize the experience when needed.

The main area I would improve is the learning curve because there are many concepts and configuration options, and understanding how indexing, query pipelines, security, and all those pieces work together requires experience. Coveo's onboarding experience could be simpler, especially for developers using the platform for the first time, and I believe that improvement on the documentation is also needed because while Coveo has extensive documentation, it is sometimes difficult to find exactly what you need.

As a developer, when trying to find something regarding how to do indexing, I have to read the documentation, but if there were screenshots showing how it can be done, it would make a developer's life simpler. Additionally, including code examples would greatly enhance the experience for developers.

I have been using Coveo mainly in enterprise search implementation, particularly in Sitecore environments, so I have been working with Coveo for the last five to six years.

From an enterprise perspective, scalability is one reason we consider a platform Coveo because we don't have to build and maintain the underlying search infrastructure ourselves, and the platform is designed for large content environments. My direct experience is more focused on implementation and integration, but I haven't seen scalability become a major limitation.

I recommend starting with search requirements rather than starting with product features. Understand your content sources, security model, and relevance.

So far, I haven't touched Coveo's AI-powered solutions, so I may not be able to comment on that because my experience is mostly with integrating Coveo, but not with the AI-powered solution models. I haven't used those AI features much, so I cannot provide insight on the accuracy and reliability of output.

I would rate Coveo an eight out of ten. I choose this rating because the platform is powerful, has strong relevance, and enterprise capabilities, but I deduct a couple of points mainly due to the learning curve and some areas that can take time to understand when implementing Coveo for the first time.

My main use case for Coveo is the search page. I use Coveo for my search page by creating sources in Coveo cloud organization and then providing it with data from our website and then displaying that search result on the search page.

Coveo has impacted my organization positively, as the search has been very good; the search terms and fuzzy search have all become very effective. I don't have particular data regarding specific outcomes or metrics at this time.

One thing that stands out to me about using Coveo for this process is that, as it is a cloud platform, it is very easy to integrate with your website as compared to other search options available.

The best features Coveo offers are the machine learning models and Coveo API. What I like about the machine learning models is that they are very easy to integrate; you just need to create some settings in the cloud organization, and then when you start using the search, it automatically learns from those searches and provides auto-suggestion in the search box.

Regarding Coveo's AI capabilities, I think its governance and security are good; as it is a cloud-based platform, the security is already very good as it uses SSO or login features. The accuracy and reliability of output from Coveo comes when the machine learning models learn from the searches that are done on your live site, so it becomes better over time, and I think those are reliable.

In terms of integration capabilities with other platforms or tools I use, I think it is pretty good; integration is straightforward. I have done it with Sitecore as well, and it provides out-of-the-box packages to integrate it, so it is very easy. I would describe the user interface and overall user experience with Coveo as very good.

I think Coveo can be improved by providing a sandbox for developers, even if you are not part of an organization, and the API configurations can be made a bit easier because there are a lot of options right now which confuses users. If I had to rate Coveo's flexibility regarding customization for my specific needs, I think it would be six out of ten.

I have been using Coveo for two years.

I think Coveo is stable.

I think Coveo's scalability is good.

The customer support for Coveo is very good.

I have used Solr before Coveo, and we switched to Coveo to utilize its AI capabilities.

Coveo is deployed in my organization as a SaaS-based software, so you don't need to deploy it; it comes by default on a cloud and it basically will provide you an organization so you can log in and then work with Coveo.

I can't say I have seen a return on investment with Coveo; I don't have these metrics.

I was not part of the pricing and licensing experience as it is handled by my organization, so I'm not aware.

Before choosing Coveo, we did not evaluate other options.

I would rate Coveo an eight out of ten. I chose eight out of ten because, as this is a cloud-based platform, there are some limitations, but overall it's a good tool.

Coveo already has a very good e-learning platform with multiple courses to learn and certifications to achieve, so it is very good in terms of the learning curve for new users or developers working with it. The documentation and resources available for Coveo are helpful, and even if you are a new learner, you can go through the documentation and it covers everything related to Coveo.

As far as I have used it, Coveo's performance and speed with large data sets is pretty good. I would advise others looking into using Coveo that it's a great product; just start looking into the documentation and utilize it well so your search page becomes better.

Our main use case for Coveo is to retrieve data efficiently. Before using Coveo, we stored this data in Salesforce itself, which took longer. We migrated our database to Coveo.

A specific example of how we use Coveo to retrieve and store data is related to our website, which functions as a doctor's website. Previously, we stored all data related to our doctors' content in Salesforce directly. When a doctor searches for it on our website or opens our record page, content pages, or content landing pages, content loading time took around 300 milliseconds. While not a major difference, in terms of user experience, it matters. After migrating to Coveo, it took less than 10 milliseconds to load all this data. This is our main use case, and we also have other use cases, such as content recommendation to our doctors based on trending content and personalized content.

Regarding the content recommendation use case, Coveo helps us personalize content for doctors with an ML-related feature. We send every detail of the doctor's viewing of pages to Coveo directly with the help of Google Analytics. First, we send the data from Salesforce to GA once a doctor views any particular content, and GA sends all this data to Coveo to train our ML models. With the help of those ML models, we see what the trending content is currently. Our doctors are specialized in 12 to 13 different specialties. Based on their specialties, we recommend content directly on the dashboard pages and on the content detail pages.

The best features Coveo offers include content recommendation, which is one of the best features. Additionally, the retrieval of data takes less time. It has moved from 300 milliseconds from our Salesforce data retrieval to less than 10 milliseconds in our Coveo retrieval. This is one of the other best features. The best thing is that we do not need to make an API callout for every communication between Salesforce and Coveo. I believe we are using headless communication, which is considerably faster. These are the best features I have observed.

Coveo has positively impacted my organization primarily by reducing the waiting time from 300 milliseconds to 10 milliseconds. Coveo also provides us very high data storage. We store our Salesforce records directly into Coveo as well. It syncs, and it takes around one hour to have a sync between Salesforce and Coveo.

Besides the improved speed and data storage, I have noticed increased productivity. Productivity has increased. The improvement is good, but I do not have the exact metrics of those details.

Coveo almost fulfills all my use cases, so I do not have any other recommendations or suggestions for Coveo.

One other suggestion is that as of now, the sync between our Salesforce and Coveo is one hour. I know we can make it real-time also. I do not know much about it, but I think it costs higher if we make it real-time. I would say that could be one of the improved features. It can give us more satisfaction if it is a real-time sync.

I have been using Coveo for a year.

Support is very good with Coveo.

It was great working with a product such as Coveo and integrating that product with our Salesforce. The experience has been good. I would rate this review a 9.

I used Coveo for content indexing and content search from AEM, and I have used it for multiple languages. The content was available in English language and Chinese language, so our requirement was to index the content and then search the content from Coveo.

Coveo has a push API which indexes the content with a certain structure and JSON payload for the page properties that exist in AEM pages. For example, a page title, page description, page tags, and metadata properties from the page are indexed in Coveo with the help of Coveo push API. There are certain request headers such as UTF-8 encoding. We wrote an HTTP client which makes calls to Coveo push API to index the content. To search the content, we used the Coveo endpoint and the page ID as the path, basically the page path as a resource to pull the content from Coveo.

We used Coveo for multiple languages with English language content and Chinese language content. We faced challenges initially because we had not added UTF encoding in the header, so the Chinese content was not properly indexed and instead showed question marks. We added the header with UTF-8 encoding, and after invoking the same API, we were successfully able to index the Chinese content. We fixed this issue and successfully indexed and fetched the Chinese content from Coveo.

Coveo is an enterprise-grade search and index platform that can be integrated with any CMS platform; in our case, it was Adobe Experience Manager. Since it is API-based, Coveo can also be used in other CMS platforms.

We did not face challenges in the integration process with Adobe Experience Manager specifically. We went to Coveo platform, reviewed the API integration methods, and learned how to pass the key and authentication methods in the API. We configured the OSGi configurations, which is typically how AEM supports any kind of configurations. We used the OSGi configurations in AEM and configured these API endpoints and the authentication methods, OAuth tokens, and other security measures. We invoked that API in our code base; in our code, we have OSGi services and Sling Servlets which are invoking Coveo's APIs.

Coveo is scalable and I have not seen any latency issue. The content immediately reflects the moment you index it, and in a couple of minutes, it is reflecting on the Coveo server. It is easy to use, easy to navigate, and you can easily find your content which is indexed on Coveo platform. Coveo is a specialized platform in the field of indexing and searching and is a known search platform. We seamlessly integrated and benefited, especially because indexing the content was taking too much time when we were indexing to other platforms such as Solr. However, in Coveo, we have not faced any latency issue and we were quickly able to index the content and search the content.

Coveo is easy to integrate and it hardly takes a few lines of code that we need to write. There are not many complex configurations we have to write for integration. A small configuration for the API endpoint, the API payload, and the authentication methods allows us to write a few lines of code for an HTTP client to invoke these APIs. It is easy to integrate and we can easily maintain it. If there are any changes in the future, we can easily make these changes.

Coveo can improve by supporting a few more languages. For example, we have tested with English and Chinese and a bit of French. I think Coveo can come up with indexing and searching with non-native languages apart from these known languages.

When we have to scroll down to search for particular pages, maybe they can provide easier navigation and links to find content, either with the help of page paths or another method. We have seen that if we have multiple pages or many pages published to Coveo to index, then it is time-consuming to scroll down and see the content, especially if it is indexed properly.

I have used Coveo for more than two years.

Coveo is deployed in our organization on a public cloud with API integrations and authentication methods, and we call this publicly hosted Coveo platform on the cloud.

We have used AWS, if I remember correctly, because it was a long time ago, almost more than two to three years back now.

There was a separate team actually accessing Coveo console and they were aware of that; we were using those APIs and the configurations as a vendor.

If others are looking into using Coveo, I would advise that if they have a use case for scalable solutions for enterprise-wide search capability or indexing content, then Coveo is the right choice.

I would rate Coveo a seven out of ten.

My main use case for Coveo is the search functionality that it provides on our website, which is heavily integrated with our content management system, enabling indexing of our content coming directly out of Sitecore, helping visitors discover content.

In the commercial real estate domain, we operate applications that allow listing agents or property agents to list properties for sale or lease. Once they create a property listing, they push out the data to the content management system, which immediately triggers Coveo APIs to index all the pushed content, populating the search UI that visitors use to search and discover listings and other content.

Coveo's primary usage is how it integrates with our marketing technology platform through its search functionality.

One of the best features that Coveo offers is the AI-enabled query suggestions feature, which looks at user query patterns and suggests relevant queries when users revisit the site, driving engagement.

AI-enabled query suggestions help users return more frequently and build trust in the search capabilities our site offers, allowing us to drive content towards users based on popular queries. Coveo offers a lot of analytics, including reporting on the most used queries and search relevance, which helped us consolidate various search hubs to improve end-user experience.

Coveo has helped build trust among users, although we still have a lot to improve for the overall search experience. We measure trust or improvement in user experience through engagement metrics, looking at website visit frequency, users' success in finding what they're looking for, click-through rates, and how those convert into leads.

Coveo could be improved by simplifying its configuration and setup, as it has a lot of dependencies on Coveo expertise, making it less intuitive.

I have been using Coveo for the last one and a half years.

Coveo is stable; the indexing is reliable, and we can see the fallouts after indexing runs.

I have not seen Coveo being scaled significantly during the last one and a half years, with only a few configurational tweaks made.

Customer support has been adequate; we do not involve them too much.

This is my first experience with a search platform, and I have not used a different solution previously.

In a general sense, we are not seeing a remarkable return on investment because maintaining Coveo for our search functionality is costly, and we have to balance investments in search versus other areas.

I rate it at six mainly due to the complexity of setting up Coveo independently and its considerable expense as a product.

Those were not things I was personally involved in, but I heard feedback about how expensive it was to use Coveo, particularly regarding API calls.

Coveo is deployed in a private cloud in our organization. I am not really sure specifically which cloud provider that is for our private cloud deployment. Anyone using Coveo should be aware that customizations will involve more work whenever changes or improvements are made. I would rate Coveo a six out of ten based on my experience.

My main use case for Coveo is that I use it as a search engine for my websites.

A quick specific example of how I use Coveo as a search engine for my websites is that we mostly used it for article pages; for example, if we need to sort a latest article, we send the entire article data to Coveo, which filters it for us and gives the exact result based on the rules we provided for Coveo. We have N number of customizations and rules for Coveo, so based on these rules, Coveo sorts out the data.

Coveo provides a search engine experience that is superior when compared to the other search engines available in the market as of now.

The best features Coveo offers include customization; for example, if you are working on regional search and you have an issue with needing to customize the date format for Coveo results for one particular regional site, you can customize it using date formats in Coveo. These kinds of customizations are not offered in other search engines in the market, which is where Coveo provides more customization features.

Coveo has positively impacted my organization by helping us achieve client requirements in a better way.

Coveo can improve based on the rules we have provided in our CMS platform; in my case, we are using a CMS platform integrated with Coveo, so the rules we are providing, called Coveo rules, generate the data.

I chose eight out of ten because we have some limitations, such as when we share heavy data, where a large number of data takes more time for Coveo to process; that is one area where Coveo needs to improve, but apart from that, it is good.

Coveo is already doing well, and I have no additional suggestions at this time, but if there are any in the future, I will definitely let you know.

I have used Coveo for more than two years.

I have already mentioned that the customer support is very good; when we reach out to the customer support team, the way they answer our questions and follow up is really well, so on a scale of ten, I will definitely give ten for this customer experience.

Before Coveo, we usually used an alternative solution.

From the perspective of pricing, setup cost, and licensing, you can use their help to set up Coveo, and I did not face any issues while setting it up.

I have seen a return on investment; it is a one-time implementation once we set it up, and we do not need employees to work on Coveo as we can automate it, so overall, it is good.

Before choosing Coveo, we evaluated other options; we usually used the Sitecore search engine before Coveo, but compared to Sitecore, Coveo is working well and giving better results, which is why we switched.

My advice for others looking into using Coveo is that I would definitely suggest them to go with Coveo; if they are looking for any search engine, I will definitely recommend Coveo.

Coveo is a good search engine when compared to others.

Coveo is performing well, and I have no additional thoughts before we wrap up. I would give Coveo an overall rating of eight out of ten.

My main use case for Coveo involves working on SAP Commerce technology where we built an e-commerce solution for one of our clients who faced issues while performing smart product searches on the site. Coveo provides AI-driven search results and proper recommendations based on customer interaction and context, which is very beneficial for us because it improves our order conversion rate, allowing customers to find the exact products they want and see similar products, greatly increasing upselling.

A specific example of how Coveo helped solve the smart search issue for our client is that it offers personalized recommendations based on customer interaction rather than global recommendations. We send an event to Coveo, and based on that event for a particular user, Coveo sends personalized recommendations, which is crucial as customers searching for products receive recommendations based on what other similar users have purchased. Coveo's flexibility allows us to create recommendations based on strategies like recently viewed or most purchased products, and it integrates easily with SAP Commerce, making it straightforward for us to index all products in Coveo, which uses a machine learning model. We can configure a search result via a query configuration pipeline, which adds to the flexibility and intuitiveness of using Coveo as it continually updates with new features like real-time facet management that requires no technical knowledge to implement.

Coveo greatly helps our customers, as we use it not only for product search but also for content search. Its indexing capabilities are versatile, utilizing various approaches like pull or push methods, and its AI model effectively responds to user interactions. Coveo enables us to configure all aspects of the search page, from facet ordering and priorities to sorting criteria, which can be done easily through the customer merchandising hub, enhancing workflow efficiency and increasing customer satisfaction as users receive relevant search results effortlessly.

The best features Coveo offers include how easily a customer or client can manage their products. We indexed around 70,000 products in Coveo, creating a tailored pipeline for search, listing, and recommendations, which grants us full control over what is displayed in search results. Additionally, all customer interactions are captured through events using either out-of-the-box libraries or custom events, allowing Coveo to provide personalized search results that significantly improve user experience. Even on the order confirmation page, Coveo suggests complementary products based on order history, facilitating upselling and addressing customers' needs seamlessly.

We use Coveo's search pipelines and event tracking features, which stand out due to their unique query pipeline structure that allows customization of search results. Coveo typically provides three pipelines: search query, listing query, and recommendation query pipelines. This structure enables us to implement synonyms and keyword redirection while managing filtering logic to enhance user searches and provide a seamless experience. Coveo also supports pre- and post-conversion processes during indexing, giving us the ability to tailor the search results effectively and allowing clients to boost or bury specific products easily. For event tracking, Coveo offers smooth integration with Google Tag Manager to capture ongoing events effortlessly, and their support for SAP Commerce integration streamlines the overall process.

Coveo is recognized as a trusted partner with SAP, and its effective indexing process coupled with multiple integration sources allows us to enhance the customer experience continuously while offering insightful analytics on user behavior that inform our strategies to improve product relevancy and conversion rates.

One area of improvement for Coveo is the size limitation concerning response results. Specifically, when grouping various variants under a parent product, the number of variations that can be displayed is restricted, which we mitigate through infinite loading techniques. Enhancing the response size capacity would be beneficial, although the newly introduced facet manager improves the configuration process, its limitation of 30 pin facets is somewhat restrictive, although it is a manageable performance consideration.

While the documentation is mostly adequate, I believe it can be improved further. Certain valuable insights provided by the PS team are not always captured in the documentation, which can be a hurdle for new users during the integration process.

I have been using Coveo for the past one year and above.

Coveo is stable with minimal downtime in my experience. While occasional issues arise, their excellent support team resolves them quickly based on priority, ensuring smooth operations.

Coveo's scalability is adept, allowing for growth aligned with the chosen plan and tier. With the ability to upgrade, higher tiers can support increased processing needs, reducing indexing time as product volumes grow.

Customer support is fantastic. I appreciate how they engage with us by asking the right questions and providing timely resolutions and updates, ensuring excellent overall support from both customer service and the PS team.

Previously, we used Solr, a standard SAP Commerce feature, but we switched to Coveo because of its limitations, which SAP itself recommended we overcome by integrating Coveo for a more effective solution.

We see an increase in conversion rates due to Coveo, but the primary benefit is the analytics it provides, enabling our clients to understand customer behavior better. They can now monitor events and identify profitable opportunities by accessing detailed metrics through the dashboard, ensuring they have clear visibility into their performance with ongoing support from Coveo's team.

Coveo is deployed in our organization through their provision of dedicated non-production and production tenants, where we utilize various sources for different environments, including QA, development, and production, ensuring smooth operational processes across the board.

We have seen a return on investment through Coveo, reflected in measurable growth in both product and content searches, which allows customers to easily find relevant information and products, enhancing their experience and providing valuable insights for our clients on customer behavior and conversion metrics.

Regarding pricing, Coveo's dictionary feature allows us to control prices dynamically according to the customer, location, or store, making it adaptable to varying business needs. We also utilize the dictionary for stock availability. Setup costs and licensing entail a fixed number of hours for PS team support during integration, alongside a plan based on API call volumes.

Coveo positively impacts our organization by resolving the personalization issue we faced with our previous solution, Solr, by enabling customers to find the right product at the right time based on their interests.

Coveo is stable with minimal downtime. While occasional issues arise, their excellent support team resolves them quickly based on priority, ensuring smooth operations.

Coveo's scalability is adept, allowing for growth aligned with the chosen plan and tier. With the ability to upgrade, higher tiers can support increased processing needs, reducing indexing time as product volumes grow.

One area of improvement for Coveo is the size limitation concerning response results. Specifically, when grouping various variants under a parent product, the number of variations that can be displayed is restricted, which we mitigate through infinite loading techniques. Enhancing the response size capacity would be beneficial, although the newly introduced facet manager improves the configuration process, its limitation of 30 pin facets is somewhat restrictive, although it is a manageable performance consideration.

While the documentation is mostly adequate, I believe it can be improved further. Certain valuable insights provided by the PS team are not always captured in the documentation, which can be a hurdle for new users during the integration process.

My advice for those considering Coveo is to choose it if they are looking for enhanced, personalized search results that can significantly improve user satisfaction. I rated this review an 8 out of 10.