AB Tasty vs Coveo Relevance Cloud

• Customer-focused. Over the past year, AB Tasty has worked with us to overcome many obstacles (e.g. tracking hurdles, ITP issues, etc.). The team always finds a solution in a timely manner to ensure we're able to execute on experiments.
• Reliability. One of the biggest hurdles earlier this year were the ITP regulations set out by Apple. Over 40% of our ad traffic was Safari users. AB Tasty was using 3rd party cookies but quickly migrated over to a local session storage solution that circumvented the issue.

Read full review

• 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

• Sometimes the platform is a little glitchy and requires a refresh.
• Would be great to be able to see the experiments and projects on a timeline with their status and main result to have an immediate view of ongoing and completed projects.
• Email notification for when an experiment reaches a certain confidence level.

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

• Since we use AB tasty our conversion rates have significantly increased on the Watch pages.
• We can report positive comments about the evolutions of our interfaces, from our expert users. And so improved customer satisfaction.
• The solution allows us to validate or invalidate without taking major risk while gaining in reactivity, our proposals relook pages.
• Commitment rates are much higher, multiplied by 2 or 3, when we implement customizations that are relevant. These customizations are very relevant insofar as we are governed by the seasonality of events as a media site.

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