added metrics reference

Author: guimachiavelli

docs.json

@@ -209,7 +209,8 @@
                   "learn/analytics/configure_analytics_events",
                   "learn/analytics/bind_events_user",
                   "learn/analytics/migrate_analytics_monitoring",
-                  "learn/analytics/events_endpoint"
+                  "learn/analytics/events_endpoint",
+                  "learn/analytics/analytics_metrics_reference"
                 ]
               },
               {

learn/analytics/analytics_metrics_reference.mdx

@@ -0,0 +1,56 @@
+---
+title: Analytics metrics reference
+description: This reference describes the metrics you can find in the Meilisearch Cloud analytics interface.
+---
+
+## Total searches
+
+Total number of searches made in the selected indexes during the specified period.
+
+## Total users
+
+Total number of users who performed a search in the selected indexes.
+
+Include the [user ID](/learn/analytics/bind_events_user) in your search request headers for the most accurate metrics. If search requests do not provide any user ID, the total amount of unique users will increase, as each request is assigned to a unique user ID.
+
+## No result rate
+
+Percentage of searches that did not return any results.
+
+## Click-through rate
+
+The ratio between the number of times users clicked on a result and the number of times Meilisearch showed that result. Since users will click on results that potentially match what they were looking for, a higher number indicates better relevancy.
+
+Meilisearch does not have access to this information by default. You must [configure your application to submit click events](/learn/analytics/configure_analytics_events) to Meilisearch if you want to track it in the Meilisearch Cloud interface.
+
+## Average click position
+
+The average list position of clicked search results. A lower number means users have clicked on the first search results and indicates good relevancy.
+
+Meilisearch does not have access to this information by default. You must [configure your application to submit click events](/learn/analytics/configure_analytics_events) to Meilisearch if you want to track it in the Meilisearch Cloud interface.
+
+## Conversion
+
+The percentage of searches resulting in a [conversion event](/learn/analytics/configure_analytics_events) in your application. Conversion events vary depending on your application and indicate a user has performed a specific desired action. For example, a conversion for an e-commerce website might mean a user has bought a product.
+
+You must explicitly configure your application to send conversion events when conditions are met.
+
+## Search requests
+
+Total number of search requests within the specified time period.
+
+## Search latency
+
+The amount of time between a user making a search request and Meilisearch Cloud returning search results. A lower number indicates users receive search results more quickly.
+
+## Most searched queries
+
+Most common query terms users have used while searching.
+
+## Searches without results
+
+Most common query terms that did not return any search results.
+
+## Countries with most searches
+
+List of countries that generate the largest amount of search requests.

learn/analytics/bind_events_user.mdx

@@ -7,7 +7,7 @@ description: This guide shows you how to manually differentiate users across sea
 import CodeSamplesAnalyticsEventBindSearch1 from '/snippets/samples/code_samples_analytics_event_bind_search_1.mdx';
 import CodeSamplesAnalyticsEventBindEvent1 from '/snippets/samples/code_samples_analytics_event_bind_event_1.mdx';
 
-This guide shows you how to to manually link analytics events to specific users.
+This guide shows you how to manually link analytics events to specific users.
 
 ## Requirements
 

learn/analytics/events_endpoint.mdx

@@ -1,6 +1,5 @@
 ---
 title: Analytics events endpoint
-sidebarTitle: Analytics events endpoint
 description: This reference describes /events, the endpoint you should use to submit analytics events to Meilisearch Cloud. It also describes the accepted event objects and the data you must include in them.
 ---
 

reference/api/overview.mdx

@@ -153,6 +153,12 @@ Responses will include a `metadata` object:
 | `primaryKey` | String  | Primary key field name, if index has a primary key         |
 | `remote`     | String  | Remote instance name, if request targets a remote instance |
 
+<Note>
+A search refers to a single HTTP search request. Every search request is assigned a `requestUid`. A query UID is a combination of `q` and `indexUid`.
+
+In the context of multi-search, for any given `searchUid` there may be multiple `queryUid` values.
+</Note>
+
 ## Request body
 
 The request body is data sent to the API. It is used with PUT, POST, and PATCH methods to create or update a resource. You must provide request bodies in JSON.