Coveo Relevance Cloud vs LiftIgniter Real-time Personalization Platform

• 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

• It does a good job recommending content that is related to the current story a user is on.
• It does a good job not recommending content the user has already viewed.
• It does a good job being a recommendation engine for disparate sites with related content.

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

• Manually controlling certain undesired results is not straight forward and seems to often result in a lower CTR or conversion rates.
• The LI Dashboard has limited features.

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

• Increased time on site
• Decreased bounce rate
• 5-15% CTR for users which saw recommendations

Read full review