Coveo Relevance Cloud vs Webtrends Optimize

• 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.

Read full review

• Intuitive test set-up makes for a low learning curve.
• Ability to create custom data tables which enable exporting of visitor level data for more in-depth analysis outside of the Webtrends Optimize platform.
• Visual Editor WYSIWYG interface enables non-technical users to easily execute basic tests.

Read full review

• 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.

Read full review

• The cost is a factor. When you're trying to save money, particularly as a startup (a lot of our clients are up-and-comers) it has to be seen as an investment...but the cost to implement the system is fairly large.
• There's a bit of a steep learning curve, you can't just dive into the program.
• It's not impossible but it's not as easy as snapping your fingers to easily implement the program cross-platform.

Read full review

• Quick to find things in a massive database when needed.
• Results need to be more concise - sometimes we spend more time looking for the right file than if we were to just search amongst our own networks instead.
• Coveo is not always the most useful but does its job when general information is needed.

Read full review

• So far we haven't seen an ROI that we can accurately measure due to only running a couple of tests that haven't resulted in direct, site wide changes. However, we have learnt a lot about how to set up the right processes and documentation.

Read full review