--- title: Get started slug: '1769' canonical_url: https://docs.coveo.com/en/1769/ collection: coveo-analytics source_format: adoc --- # Get started [Coveo Analytics](https://docs.coveo.com/en/182/) can be a game changer as it not only lets you measure and maximize your search solution adoption, but it also feeds [Coveo Machine Learning (Coveo ML)](https://docs.coveo.com/en/188/) features with [data](https://docs.coveo.com/en/259/) that can significantly improve your user experience. This article focuses on how to get going on your Coveo Analytics journey. **To get started with Coveo Analytics** . Get familiar with the [Coveo Analytics concepts](https://docs.coveo.com/en/1670/). . Ensure that you're a [member](https://docs.coveo.com/en/2873/) of a [group](https://docs.coveo.com/en/202/) with the required [privileges](https://docs.coveo.com/en/228/) to access and make changes in the [Coveo Administration Console](https://docs.coveo.com/en/183/) **Analytics** pages (see [Manage privileges](https://docs.coveo.com/en/3151/)). . Ensure that the Coveo front-end products you use push standard search-related [events](https://docs.coveo.com/en/260/) and metadata. -- > **Important** > > We strongly recommend that all new Commerce implementations use the [Event Protocol](https://docs.coveo.com/en/o1n91230/) to log events. > The [Event Protocol](https://docs.coveo.com/en/o9je0592/) and [Coveo Relay library](https://docs.coveo.com/en/o9je0322/) are generally available for Commerce. > > However, they're in closed beta for Coveo for Service, Website, and Workplace implementations. > If you're interested in using the Event Protocol and Relay library for these implementations, contact your customer success manager (CSM). -- ** Coveo for Salesforce By default, Coveo for Salesforce search components automatically push standard search-related Coveo Analytics events and [dimensions](https://docs.coveo.com/en/258/) to your [Coveo organization](https://docs.coveo.com/en/185/). You have nothing to do. ** Coveo for Sitecore 5 The Coveo Analytics module is enabled by default in a Coveo-powered Search Page. Therefore, no configuration is needed to capture search page [events](https://docs.coveo.com/en/2949/). ** [Coveo Atomic library](https://docs.coveo.com/en/lcdf0264/) When used correctly, Atomic components take care of logging standard search-related Coveo Analytics events for you. No additional configuration required. ** [Coveo Headless library](https://docs.coveo.com/en/lcdf0493/) When used correctly, Headless controllers take care of logging standard search-related Coveo Analytics events for you. No additional configuration required. ** [Coveo JavaScript Search Framework](https://docs.coveo.com/en/187/) standalone [search interfaces](https://docs.coveo.com/en/2741/) A standalone Coveo JavaScript Search Framework search interface must simply contain the [`Analytics`](https://coveo.github.io/search-ui/components/analytics.html) component with minimal configuration to automatically push all default search events to Coveo Analytics for your [Coveo organization](https://docs.coveo.com/en/185/). ** Coveo [hosted search page](https://docs.coveo.com/en/2866/) An administrator can [configure a hosted search page](https://docs.coveo.com/en/1656/) to send standard search-related Coveo Analytics data to a Coveo organization when performing the first time configuration. . View your Coveo Analytics data. You can view the Coveo Analytics data pushed from your Coveo products in different ways: ** Review default [reports](https://docs.coveo.com/en/266/) and create new ones (see [Reports](https://docs.coveo.com/en/1674/)). ** [Review individual user visits from the Visit Browser](https://docs.coveo.com/en/1964/). ** Export and analyze your data with your preferred tool (see [Manage raw data](https://docs.coveo.com/en/1856/)). . Leverage your Coveo Analytics data. ** [Take advantage of Coveo Analytics](https://docs.coveo.com/en/1584/) to maximize your search solution adoption. ** [Take advantage of Coveo ML features](https://docs.coveo.com/en/3372/) that feed on Coveo Analytics. . Consider adding custom metadata. After working with default events and dimensions, you may want to also gather information specific to your environment. A developer can do that by adding code to push custom metadata to your search-related events or even custom events with custom metadata. > **Important** > > Custom data can only be leveraged when using the UA Protocol. > If you're using the [Event Protocol](https://docs.coveo.com/en/o3r90189/), keep in mind that custom fields have been replaced by predefined events and dimensions. > To learn more about the available protocols, see [Track usage analytics](https://docs.coveo.com/en/ncd90215/). .. Push custom events and metadata (developer task). *** In Coveo for Salesforce, see [Send context information in Salesforce Lightning](https://docs.coveo.com/en/3290/) *** In Coveo for Sitecore, see [Adding custom Coveo Analytics metadata](https://docs.coveo.com/en/2138/) *** In a Coveo Atomic search page, see [Usage analytics](https://docs.coveo.com/en/atomic/latest/usage/atomic-usage-analytics/) *** In a Coveo Headless search page, see [Usage analytics](https://docs.coveo.com/en/headless/latest/usage/headless-usage-analytics/) *** In a Coveo JavaScript Search Framework search page, see [Send your own search, click, or custom events](https://docs.coveo.com/en/365#send-your-own-ua-events) .. Create matching custom dimensions (administrator task). In the Coveo Administration Console, you must [create a custom dimension for each custom metadata](https://docs.coveo.com/en/1522/) to make them available in the [Visit Browser](https://docs.coveo.com/en/274/) as well as in [dashboards](https://docs.coveo.com/en/256/) and [explorers](https://docs.coveo.com/en/261/).