Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Coveo for Sitecore Comparisonv4.1 1v4.0 1v3.0
Active Development(tick)(error)(error)
Coveo for Sitecore Hive Framework(tick)(error)(error)
Machine Learning
Sc_edition
cloudtrue
versionPro and Enterprise
(tick)(tick)(error)
Cloud Index
Sc_edition
cloudtrue
versionPro and Enterprise
(tick)(tick)(error)
On-premises Index(tick)(tick)(tick)
Coveo Usage Analytics
Sc_edition
versionPro and Enterprise
(tick)(tick)(tick)
JavaScript Search Framework

2.0+ (for Coveo for Sitecore Hive)

1.0+ (for the legacy Coveo for Sitecore components)

1.0+0.9
Release cycle~6 weeks~3 months

On request only

...

Usage Analytics and Coveo Machine Learning

AnchorTableNote1TableNote11See Editions & Pricing for all the features.If you are familiar with Coveo for Sitecore 3, you know that Usage Analytics were introduced in this version, but you still had to configure it and contact the Professional Services to initialize your organization. With version 4 and Cloud indexing,  the Usage Analytics feature is enabled by default right out of the box (see Coveo Usage Analytics). Furthermore, Coveo for Sitecore 4 enables you to leverage the precious analytics and feed them to Coveo Machine Learning (Coveo ML), Coveo's artificial intelligence powered service that analyzes search behavior patterns to increase the relevancy of the  Coveo search results (see Getting Started with Coveo Machine Learning).

Cloud IndexingIndexing 

Coveo for Sitecore 4 offers the possibility to have your indexes hosted in the Coveo Cloud platform (see Understanding the Architecture of Coveo for Sitecore - Cloud). Migrating to a cloud-based index brings many advantages:

(tick) Less software: you do not need to install Coveo Enterprise Search (CES) nor the Coveo Search API. No Now, there is no need to deal with the Admin Service and RabbitMQ anymore.

...

...

The Coveo for Sitecore Hive components allow you to create search pages by adding the components you want directly form the Sitecore Experience Editor (see Integrating Coveo for Sitecore Hive in a WebsiteUI Framework).

Modularity

Instead of using a single component that strives to do everything, the search page is now split in many smaller pieces, each one representing a Coveo for Sitecore Hive component. Each component has a single responsibility and exposes displays its specific options.

You can thus move components around much more easily from the Experience Editor.

...

In previous Coveo for Sitecore releases, the website styling was tightly coupled to the search component view. A developer had to duplicate the search components to create their own view, mostly because of styling needs.

...

Leveraging Data Sources brings many benefits:

  • Decouples It decouples the component settings from the component itself, making it easier to share a common set of parameter values between many components.
  • Merges It merges field values through standard item inheritance. In other words, you can have a Data Source that only sets a field value and inherits values for all the other fields.
  • Supports It supports local and shared Data Sources. When the Data Source item is defined as a child of the page, it is considered a local Data Source. The other alternative is to store the Data Store item elsewhere in the content tree. In such case, it is considered a shared Data Source.
    As the name states, many components can reference the same Data Source item.
  • Supports It supports Sitecore branches to create pre-configured search-driven pages.

...

The Coveo Hive components are designed with HTML caching in mind. Most of the components are "cached by Data Source," which is ideal. In order to achieve that, the rendered HTML depends solely on the Data Source parameter values. With a given set of parameters, the HTML is always the same regardless of of the current visitor, or the page it is bound to, or the current visitor.

There is one special component that makes HTML caching work for the others: the context component. Its purpose is to render all the non-cacheable information for the other components. The context HTML markup cannot be cached because it varies on many contextual factors such as the current item, the visitor, etc. Once the page is served, all the cached components can then access the context on the client-side and do their work.

...

To help you transition from 3.0, you can review the documentation about configuration file differences and the steps you need to undertake to adapt search pages, search components and layouts to JavaScript Search Framework V1  (see Upgrading from Coveo for Sitecore 3.0 to Coveo for Sitecore 4.0). Take a look at the Supported Sitecore Versions and Dependencies to make sure your setup is fully compatible with Coveo for Sitecore 4