---
title: Coveo Usage Analytics in Sitecore
slug: '2234'
canonical_url: https://docs.coveo.com/en/2234/
collection: coveo-for-sitecore-v5
source_format: adoc
---
# Coveo Usage Analytics in Sitecore
> **Legacy feature**
>
> This article pertains to achieving relevance with the Coveo Hive framework.
> Coveo Hive is now in maintenance mode.
> 
> See [Achieve relevance](https://docs.coveo.com/en/n9qd0318/) for guidance on leveraging [Coveo Platform](https://docs.coveo.com/en/186/) relevance features with the Coveo Atomic library.

[.version.c4sc.c4sc-edition.pro-enterprise]
[Pro and Enterprise editions^,role=version-tag](https://www.coveo.com/en/pricing/sitecore)


[Coveo Analytics](https://docs.coveo.com/en/182/) let you track search analytics data for a Coveo-powered search page.
Various [events](https://docs.coveo.com/en/2949/) that occur within a search page (for example, `searches`, `clicks`) are logged in the [Coveo Platform](https://docs.coveo.com/en/186/).
Page `view` events in Sitecore website pages may also be logged.
All the recorded data can then be used to generate reports.

To log standard search page events in Sitecore, add the [**Coveo for Sitecore Analytics**](https://docs.coveo.com/en/2186/) rendering to your search interface.

To log `view` events in Sitecore, add the [**Coveo Page View Analytics**](https://docs.coveo.com/en/3013/) rendering on the given website page.

> **Important**
>
> 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](https://docs.coveo.com/en/n9ig0408/).

## Accessing Coveo UA reports

You must log in to the [Administration Console](https://platform.cloud.coveo.com/login) ([platform-ca](https://platform-ca.cloud.coveo.com/login) | [platform-eu](https://platform-eu.cloud.coveo.com/login) | [platform-au](https://platform-au.cloud.coveo.com/login)) to view your Coveo UA reports.

In the **Analytics** section of the main menu, select:

* [**Reports**](https://platform.cloud.coveo.com/admin/#/orgid/usage/reports/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/usage/reports/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/usage/reports/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/usage/reports/)) for an overview of all your analytics, in graph and chart form.
The second screenshot below shows the **Summary** report.

![Reports | Coveo](https://docs.coveo.com/en/assets/images/c4sc-v5/38703055.png)

{empty}

![Summary report | Coveo](https://docs.coveo.com/en/assets/images/c4sc-v5/38703026.png)

* [**Visit Browser**](https://platform.cloud.coveo.com/admin/#/orgid/usage/visit/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/usage/visit/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/usage/visit/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/usage/visit/)) for a detailed description of all events for each visit.
The example below shows John Doe's visit and some of its events.

![Visit Browser | Coveo](https://docs.coveo.com/en/assets/images/c4sc-v5/38703023.png)

To gain deeper knowledge and understanding of Coveo UA, see [Coveo Usage Analytics overview](https://docs.coveo.com/en/l3bf0598/).

## About Usage Analytics events

A usage analytics event is any user interaction with a search page, including queries, clicks, page views, and custom events (see [Events](https://docs.coveo.com/en/2949/)).

> **Important**
>
> The Coveo UA module only tracks events triggered within the `web` context.
> To track events triggered from another context, change the `database` property for the `coveoanalytics` site by creating a patch element in the `Coveo.SearchProvider.Custom.config` file.

Recording a search event relies on two elements: **Cause** and **Dimensions**.

* A **Cause** has a name and a type.
It's itself a **Dimension**.

An example of a cause would be `interfaceLoad` or `facetSelect`.

* A **Dimension** is a grouping of metadata key-value pairs principally exploited within the dashboards, reports, and explorers within the Coveo UA pages.

For examples of **Dimensions**, see [Usage analytics dimensions](https://docs.coveo.com/en/1904/).

## What's next?

You can now learn how to configure custom metadata for your analytics (see [Log custom metadata in Hive search interface usage analytics events](https://docs.coveo.com/en/2138/) and [Log view events](https://docs.coveo.com/en/2374/)).