--- title: Metrics slug: '2041' canonical_url: https://docs.coveo.com/en/2041/ collection: coveo-analytics source_format: adoc --- # Metrics A metric is a numerical value that reflects key [data](https://docs.coveo.com/en/259/) in your [Coveo Analytics reports](https://docs.coveo.com/en/266/). Metrics help you measure and analyze performance by calculating data from [events](https://docs.coveo.com/en/2949/) for the specified [dimensions](https://docs.coveo.com/en/258/) and [result filters](https://docs.coveo.com/en/2740/). In the [Coveo Administration Console](https://docs.coveo.com/en/183/), metrics are based on recorded events and can appear as trends over time, summary indicators, or detailed values in reports. The following image is that of a **Summary** [dashboard](https://docs.coveo.com/en/256/) composed of [report cards](https://docs.coveo.com/en/267/) that display various metrics: ![Metric cards | Coveo Platform](https://docs.coveo.com/en/assets/images/coveo-analytics/metric-dashboard-example.png) > **Note** > > For some metrics, a high value is good, and for others, a high value can reveal a relevance issue (see [Review implementation successes and issues with metrics](https://docs.coveo.com/en/1725/)). The available metrics grouped by event category and in alphabetical order are: ## Click metrics Click metrics measure user interactions with search results, such as how often they click and where. ### Average Click Rank This metric measures the average position of clicked [items](https://docs.coveo.com/en/210/) in the search results for the specified [dimensions](https://docs.coveo.com/en/258/) and [result filters](https://docs.coveo.com/en/2740/). Its value is greater or equal to 1. Lower values are better. A value of 1 would mean that users always open the first item in the search results list. > **Note** > > Setting goals based on the **Average Click Rank** metric isn't recommended for commerce solutions. > When shopping online, customers tend to browse through results to see the available products. **Example** The selected dimension is **Country** and users from **Spain** have an **Average Click Rank** value significantly higher than users from other countries. This may indicate poorer content or relevance for content available in Spanish. ![Average Click Rank | Coveo Platform](https://docs.coveo.com/en/assets/images/coveo-analytics/average-click-rank.png) > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#click-rank). ### Click Event Count This metric represents the total number of clicks. In a metric card, in a [dashboard](https://docs.coveo.com/en/256/) without filters, the Click Event Count is the sum of all click events (see [Click Event Cause](https://docs.coveo.com/en/2948#click-event-cause)). > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#click-count). ### Click Rank Maximum This metric represents the highest-ranked position of a clicked item in the search results. ### Click Rank Minimum This metric represents the lowest-ranked position of a clicked item in the search results. ### Click Rank Sum This metric represents the sum of the positions of all clicked items in the search results. ### Search Event Clickthrough (%) This metric represents the percentage of search events with one or more clicked search results. Its value is between 0 and 100. A higher value indicates better search results. To determine the clickthrough percentage, the [**Search Events With Clicks**](https://docs.coveo.com/en/2041#search-events-with-clicks) and [**Search Events Counts**](https://docs.coveo.com/en/2041#search-event-count) metrics are used. The formula used to calculate the **Search Events Clickthrough %** is: `(Search Events With Clicks / Search Events Count) * 100` > **Note** > > The clickthrough rate metric is affected by every search [event](https://docs.coveo.com/en/260/), but not all [queries](https://docs.coveo.com/en/231/). > For instance, when a [facet](https://docs.coveo.com/en/198/) value is selected or deselected, it triggers both a search event and a query to the Search API, hence considered in the calculation. > However, navigating between search result pages by clicking a page number triggers a query but not a search event, hence not considered in the calculation. > > For example, a search event followed by a click on two facets, and then a click on a result, leads to a clickthrough rate of 33.33% (`1/3*100`). > If you do the same search event but use the page numbers to navigate to the desired result, the clickthrough would be 100% (`1/1*100`). ### Manual Search Event Count This metric represents the total number of queries performed by users (using the search box). In [Coveo Analytics](https://docs.coveo.com/en/182/), a manual search is defined as a search where the **Search Cause** dimension contains one of the following values: * `didyoumeanAutomatic` * `didyoumeanClick` * `searchboxSubmit` * `searchboxAsYouType` * `omniboxSearch` * `omniboxAnalytics` * `omniboxFromLink` * `omniboxField` * `searchFromLink` > **Notes** > > * User query refinements are excluded. > > * The search cause of the related event must be manual for a query to count. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#manual-search-event-count). ### Search Events With Clicks This metric represents the total number of queries resulting in one or more clicks in a search result. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#search-event-with-clicks). ### Search Event Count This metric represents the total number of queries. In a metric card, in a dashboard without filters, the Search Event Count is the sum of all search events (see [Search Event Cause](https://docs.coveo.com/en/2948#search-event-cause)). > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#search-count). ### Relevance Index / Relevance Index (Legacy) This metric is calculated with a formula based on the **Search Event Clickthrough** and the **Average Click Rank** metrics to highlight ranking issues. Its value is between 0 and 1. Higher values are better. More frequently submitted queries with clicks on results farther in the search results list yield to a lower value (see [Relevance Index metric](https://docs.coveo.com/en/3318/)). Sorting by this value in descending order brings to the surface the most important potential relevance issues on which an administrator or an analytics manager can focus. **Example** When the **Country** dimension is selected and **Germany** has the lowest value for this metric, relevance issue for users from Germany should be investigated. ![Relevance Index | Coveo Platform](https://docs.coveo.com/en/assets/images/coveo-platform/relevance-index.png) ### Refined Search Event Count This metric represents the number of query refinements done by users (facets, interface change, etc.). > **Note** > > The search cause for the related event must be manual for a query to be counted. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#refined-search-event-count). ### Unique [Click Dimension Name] This metric represents the number of unique dimension values (see [Click dimensions](https://docs.coveo.com/en/2948#click-dimensions)). **Example** The Unique Click Cause metric is the number of unique click causes that triggered an event in the [search interface](https://docs.coveo.com/en/2741/) to be recorded. ## Search metrics Search metrics focus on user queries and search result performance. ### Average Number of Results This metric measures the average number of results returned by the search interface. ### Average Response Time (ms) This metric measures the average time in milliseconds the search interface took to return results. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#average-response-time). ### Average Search Query Word Count This metric measures the average number of words in queries. It's calculated based on the total number of words in a query expression, without removing [stop words](https://docs.coveo.com/en/3406/). > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#average-search-query-word-count). ### Search Event Clickthrough (%) This metric represents the percentage of search events with one or more clicked search results. Its value is between 0 and 100. A higher value indicates better search results. To determine the clickthrough percentage, the [**Search Events With Clicks**](https://docs.coveo.com/en/2041#search-events-with-clicks) and [**Search Events Counts**](https://docs.coveo.com/en/2041#search-event-count) metrics are used. The formula used to calculate the **Search Events Clickthrough %** is: `(Search Events With Clicks / Search Events Count) * 100` > **Note** > > The clickthrough rate metric is affected by every search [event](https://docs.coveo.com/en/260/), but not all [queries](https://docs.coveo.com/en/231/). > For instance, when a [facet](https://docs.coveo.com/en/198/) value is selected or deselected, it triggers both a search event and a query to the Search API, hence considered in the calculation. > However, navigating between search result pages by clicking a page number triggers a query but not a search event, hence not considered in the calculation. > > For example, a search event followed by a click on two facets, and then a click on a result, leads to a clickthrough rate of 33.33% (`1/3*100`). > If you do the same search event but use the page numbers to navigate to the desired result, the clickthrough would be 100% (`1/1*100`). ### Manual Search Event Count This metric represents the total number of queries performed by users (using the search box). In [Coveo Analytics](https://docs.coveo.com/en/182/), a manual search is defined as a search where the **Search Cause** dimension contains one of the following values: * `didyoumeanAutomatic` * `didyoumeanClick` * `searchboxSubmit` * `searchboxAsYouType` * `omniboxSearch` * `omniboxAnalytics` * `omniboxFromLink` * `omniboxField` * `searchFromLink` > **Notes** > > * User query refinements are excluded. > > * The search cause of the related event must be manual for a query to count. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#manual-search-event-count). ### Number of Results Maximum This metric represents the maximum number of results returned by the search interface for the specified dimensions and filters. ### Number of Results Minimum This metric represents the minimum number of results returned by the search interface given the specified dimensions and filters. ### Number of Results Sum This metric is the total number of results returned by the search interface for the specified dimensions and filters. ### Search Event Count This metric is the total number of queries for the specified dimensions and filters. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#search-count). ### Refined Search Event Count This metric is the number of query refinements done by users (facet, interface change, etc.) for the specified dimensions and filters. > **Note** > > The search cause of the related event must be manual for a query to count. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#refined-search-event-count). ### Response Time (ms) Maximum This metric represents the maximum time, in milliseconds, that the search interface took to return results for the specified dimensions and filters. ### Response Time (ms) Minimum This metric represents the shortest time, in milliseconds, that the search interface took to return results for the specified dimensions and filters. ### Response Time (ms) Sum This metric is the total time in milliseconds the search interface took to return results for the specified dimensions and filters. ### Unique [Search Dimension Name] This metric is the number of unique dimension values for the specified dimensions and filters (see [Search dimensions](https://docs.coveo.com/en/2948#search-dimensions)). **Example** The **Unique User Query** metric is the number of unique queries entered by users in the search box for the specified criteria. If ten people perform the same exact query (for example, `wireless headphones`), this query is counted as one in the **Unique User Query** metric. ## Custom metrics Custom metrics allow you to track unique behaviors or data points relevant to your implementation. > **Note** > > Custom data can only be leveraged when using the UA Protocol. > If your Coveo implementation uses the [Event Protocol](https://docs.coveo.com/en/o3r90189/), custom dimensions and metrics shouldn't be added to a report since they won't function as expected. ### Attach to Case Count This metric is the total number of times agents attached a result to a case (`caseAttach` event) for the specified dimensions and filters. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#attach-to-case-count). ### Custom Event Count This metric is the total number of custom events for the specified dimensions and filters. In a metric card, in a dashboard without filters, the Custom Event Count is the sum of all custom events (see [(Custom) Event Type](https://docs.coveo.com/en/2948#custom-event-type)). > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#custom-event-count). ### Unique [Custom Dimension Name] This metric is the number of unique dimension value for the specified dimensions and filters (see [Search dimensions](https://docs.coveo.com/en/2948#search-dimensions)). **Example** The Unique Custom Event Value metric is the number of unique values saved for a custom event performed in a search interface, for the specified criteria. ## All event type (click, search, and custom) metrics ### Unique [All Event Type Dimension Name] This metric is the number of unique dimension value for the specified dimensions and filters (see [Search dimensions](https://docs.coveo.com/en/2948#search-dimensions)). **Example** The Unique City metric is the number of unique cities from which a user performed an event, based on the IP address, for the specified criteria. ### Unique Client ID This metric measures the number of unique [client IDs](https://docs.coveo.com/en/lbjf0131/) that perform a query for the selected filters and dimensions (see [What's the client ID](https://docs.coveo.com/en/masb0234/)). ### Unique User IP This metric measures the number of unique IP addresses. Sometimes, different users can share the same IP address. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#unique-user-ip). ### Unique User ID This metric measures the number of unique [user IDs](https://docs.coveo.com/en/268/) that execute a query using the selected filters and dimensions (see [User ID](https://docs.coveo.com/en/2948#user-id)). > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#unique-user-id). ### Unique Visitor ID This metric measures the number of unique visitors. A [visitor ID](https://docs.coveo.com/en/273/) is based on persistent cookies, so a visitor keeps the same ID as long as they use the same browser and never clear the browser cookies. The visitor ID is a generated random sequence and doesn't allow to personally identify an anonymous user. > **Note** > > [Third-party cookies will eventually be deprecated](https://docs.coveo.com/en/m54b9238/), therefore use the [**Unique Client ID**](#unique-client-id) metric instead. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#unique-visitor-id). ### Visit Clickthrough (%) This metric measures the number of [visits](https://docs.coveo.com/en/271/) with at least one click divided by the total number of visits. > **Note** > > This metric is only available when adding visit metric cards (see [Add Visit metric cards](https://docs.coveo.com/en/1563/)). > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#visit-click-through). ### Visit Count This metric measures the number of visits regardless of unique IP addresses and user names. Visits are determined by time-based cookies. A visit ends after 30 minutes of inactivity. ### Visits With Clicks This metric measures the number of visits with at least one click. > **Note** > > This metric is only available when adding visit metric cards (see [Add Visit metric cards](https://docs.coveo.com/en/1563/)). > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#visits-with-click). ### Visits With Manual Search Events This metric measures the number of visits with at least one query performed by a user using the search box. > **Notes** > > * This metric is only available when adding visit metric cards (see [Add Visit metric cards](https://docs.coveo.com/en/1563/)). > > * User query refinements are excluded. > **Tip** > > For the related SQL expression that can be added to a query in the Snowflake reader account, see [SQL expressions reference](https://docs.coveo.com/en/mcge0079#visit-with-manual-search-events).