Coveo Analytics overview

This is for:

In this article

Leading practices
Ad blocker impact on Coveo Analytics data
What’s next?

Coveo Analytics™ is a service that collects and stores data from your Coveo search solution. This data powers Coveo Machine Learning (Coveo ML), supports standard and advanced reporting, and improves overall relevance. It helps you understand how users interact with your search and content experiences, giving you the data you need to optimize relevance and user experience.

To send data to Coveo Analytics, use the Event Protocol. This protocol is a streamlined standard for collecting and sending analytics events from your search solution to Coveo. Compared to the legacy Coveo UA Protocol, the Event Protocol uses the Relay library and simplifies event tracking by reducing the number of events logged client-side.

After you start sending events, you can analyze user activity across different Coveo interfaces.

Leading practices

Prioritize sending events with the Event Protocol when implementing or upgrading to take advantage of its streamlined design and performance.
Understand Coveo Analytics concepts and how they provide the foundation for capturing and analyzing data in your Coveo-powered solution.
Discover the available tools and reports to monitor and measure your Coveo Analytics data. For example:
- Review default reports and customize new ones.
- Use the Visit Browser page to review individual user visits.
- Use the Data Health (platform-ca | platform-eu | platform-au) page to monitor the health of your organization.

Ad blocker impact on Coveo Analytics data

Coveo Analytics is designed to improve your search experience on a designated search hub and therefore doesn’t follow users across other websites. However, certain internet filter lists may still contain references to Coveo files or analytics endpoints due to a broad "tracking" categorization.

Using either a native or a third-party ad blocker which refers to these filter lists can result in Coveo’s JavaScript files or outgoing analytics requests being blocked. As a result, in this scenario, user events in the search interface wouldn’t be sent to Coveo Analytics. For information on how to ensure that all requests are sent to Coveo Analytics, see When to use a reverse proxy.

What’s next?

Learn about Coveo Analytics concepts and how they work together to measure data in your Coveo-powered solution.