---
title: Debug tracking issues
slug: n1pd0092
canonical_url: https://docs.coveo.com/en/n1pd0092/
collection: coveo-analytics
source_format: adoc
---
# Debug tracking issues
To confirm that data tracking is correctly implemented, verify the following items, assuming that you're using the latest version of the [Coveo UA library](https://docs.coveo.com/en/1818/):

. Open a Coveo-powered search page.

. Open your web browser's developer tools.

> **Note**
>
> The examples in this article use the **Google Chrome** developer tools.
> For browser-specific information, see:
> 
> * [Google Chrome](https://developers.google.com/web/tools/chrome-devtools/open)
> 
> * [Mozilla Firefox](https://developer.mozilla.org/en-US/docs/Tools)
> 
> * [Safari](https://support.apple.com/en-ca/guide/safari/sfri20948/mac)

. On the **Application** tab of your developer tools, check whether there's an identifier in [local storage](https://docs.coveo.com/en/mbeh0288/) with the attribute name `{visitorId}`.
Cookies and local storage are typically found under a separate tab (for example, **Local Storage**).

For example:

![Identifier in developer tool](https://docs.coveo.com/en/assets/images/coveo-analytics/identifier-dev-tools.png)

. Verify that the same identifier has been stored in a local cookie with the attribute name `coveo_visitorId`, and that it's scoped to the top-level domain of the main page.
In the following example, the `+https://search.cloud.coveo.com+` search page is used, therefore the top-level domain is `.coveo.com`.

![Identifier stored in local cookie shown in browser developer tools](https://docs.coveo.com/en/assets/images/coveo-analytics/identifier-local-cookie.png)

> **Note**
>
> If you notice that you have the visitor cookie on `analytics.cloud.coveo.com`, you can ignore it.
> This is a [legacy third-party-cookie](https://docs.coveo.com/en/m54b9238/) set by [Coveo Analytics](https://docs.coveo.com/en/182/).
> 
> For example:
> 
> ![Visitor cookie in developer tool](:https://docs.coveo.com/en/assets/images/coveo-analytics/visitor-cookie-dev-tools.png)

. On the **Network** tab, verify whether this same identifier is being set on calls.

* When inspecting calls to the search API endpoint (`rest/search/v2`), the same identifier should be visible under `analytics.clientId` or `visitorId`.

![Network panel showing identifier calls in browser developer tools](https://docs.coveo.com/en/assets/images/coveo-analytics/identifier-calls-v2.png)

* When inspecting calls to the analytics API endpoints (`rest/ua/v15/analytics`), the same identifier should be visible under `cid` for the collect endpoint, or under `cliendId` in the payload or the URL `visitorId` parameter for other endpoints.

![Network panel showing identifier calls in browser developer tools](coveo-analytics/identifier-calls-v15.png)