Usage Analytics

This is for:

Developer
In this article

Administrators can leverage recorded Coveo Usage Analytics (Coveo UA) data to evaluate how users interact with a search interface, identify content gaps, and improve relevancy by generating and examining dashboards and reports within the Coveo Administration Console (see Coveo Usage Analytics overview). Coveo Machine Learning (Coveo ML) features also require UA data to function.

Since version 2.78.0, Coveo Atomic supports two tracking protocols: the Coveo UA Protocol and the new Event Protocol (EP).

Event Protocol is a new standard for sending analytics events to Coveo.

It simplifies event tracking by reducing the number of events you need to send to Coveo. For instance, you no longer need to send any search events as they’re logged server-side when you make a request to the Search API.

The protocol also streamlines the event payload, requiring fewer fields. Such streamlining results in a more efficient and less error-prone event tracking process, yielding better machine learning models and usage analytics reports.

Coveo UA vs. EP

In the upcoming Atomic V3 release, the Event Protocol will be the default tracking protocol, as it already is with the Commerce engine. In the meantime, you can already use EP with Atomic by setting the Engine analyticsMode property to next at initialization, such as in the following example.

const searchInterface = document.querySelector('atomic-search-interface');

await searchInterface.initialize({
    // ...
    analytics: {analyticsMode: 'next', trackingId: 'sports'},
});
// ...

Conversely, to stick with Coveo UA, set the analytics.analyticsMode property to legacy.

const searchInterface = document.querySelector('atomic-search-interface');

await searchInterface.initialize({
    // ...
    analytics: {analyticsMode: 'legacy'},
});
// ...

To determine whether you should migrate to EP, see Migrate to Event Protocol.