Cookie Compliance

Coveo’s Hosted Services leverages user tracking to provide core features of Coveo. While the use of cookies or other trackers may be limited to facilitate compliance with privacy legislation, some tracking is used to enhance the Platform’s services.

A commonly used cookie is the Visitor ID, which is a random and unique value that is generated when a user visits the search site for the first time. It mustn’t be confused with the Visit ID, which represents a single visit and doesn’t have an associated cookie. The Visitor ID is also distinct from the Client ID. If you set a Client ID when logging usage analytics events, it takes precedence over the Visitor ID, and therefore a tracking cookie isn’t set.

Although the Visitor ID cookie can help the Platform to function, it may not always be reliable since certain browsers block third-party cookies. For more information about the differences between the Visitor ID cookie, the Visit ID, and the Client ID, see Client ID, Visitor ID, and Visit ID Dimensions.

Opt-out Configuration

Coveo Usage Analytics can be configured to grant users the ability to opt out of cookies and other identifiers.

When users opt out, Administrators should disable Usage Analytics. The JavaScript Search Framework has three functions allowing Administrators to activate or disable Usage Analytics, as well as clear local session information from the browser.

Cookie Features Visitor ID Visit ID Client ID
Unique across different visits for the same user No Yes No
Unique across different users on the same browser No Yes No
Unique across different accounts for the same user No Yes No
Is entirely managed by the UA service No Yes No
Expires 365 Days (Depends on implementation) After 30 minutes of inactivity 365 Days (Depends on implementation)
Can be specified in requests to UA Yes No Yes
What's Next for Me?