User Activity Monitoring

In this article

Coveo’s Hosted Services leverage user activity monitoring to provide core Coveo features such as Coveo Usage Analytics (UA) and Coveo Machine Learning (ML). Coveo UA previously relied on a third-party cookie to store the visitor ID, a random and unique value, to track users visiting a Coveo-powered website. This third-party cookie had the same value for Coveo as a first-party cookie, as we didn’t leverage the cross-site tracking functionality. While the use of third-party cookies isn’t legally problematic, they do present a greater privacy risk. Therefore, many web browsers now block their creation by default or plan to stop their support.

For all these reasons, Coveo is deprecating third-party cookies and has implemented a way for clients to send a tracking ID (the client ID) through the Coveo Usage Analytics Write API, when logging UA events. The client ID is generated by Coveo’s library, coveoanalytics.js, and usually stored client side in local storage.


If the coveoanalytics.js library isn’t used, clients can still send the client ID by adding it as a parameter on the call to the Coveo UA Write API.


Are Coveo cookies first-party or third-party cookies?

Coveo is moving away from third-party cookies and is now using local storage to store the client ID, which can be sent through the Coveo API when logging UA events.

What are the leading practices when choosing tracking technologies?

Coveo recommends that preference should be given to first-party cookies and local storage. If you choose to rely on other tracking mechanisms, you should ensure that it’s used in compliance with privacy laws.

Coveo cookies are usually classified as functional or performance/analytics cookies.

If your users don’t consent to be tracked, your Coveo organization administrator can disable Coveo UA. The Coveo JavaScript Search Framework has three functions allowing administrators to activate or disable Coveo UA, as well as clear local session information from the browser.