---
title: Review user visits with the Visit Browser
slug: '1964'
canonical_url: https://docs.coveo.com/en/1964/
collection: coveo-analytics
source_format: adoc
---
# Review user visits with the Visit Browser
You can use the [**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/)) page to review user visits for your Coveo search solution.
A _user [visit](https://docs.coveo.com/en/271/)_ is also known as a _user session_, and represents the period in which a user remains active on a site.

You can also use this page for various purposes, including validating an implementation from a quality assurance perspective, or making sure that [search](https://docs.coveo.com/en/2949#search-performsearch), [click](https://docs.coveo.com/en/2949#click-documentview), and [custom](https://docs.coveo.com/en/2949#custom-customevent) [events](https://docs.coveo.com/en/260/) are logged properly.
It also provides a way to select visits that meet certain criteria (for example, visits in which a [case deflection](https://docs.coveo.com/en/2911/) occurred), and review the events, in order of occurrence, for each visit.

By default, the **Visit Browser** page shows 50 visits per page and 250 events per visit.
However, all events that occurred in the visits are available when you [export the visit data](#export-visit-data-that-meet-your-criteria) (see [Data exports](https://docs.coveo.com/en/2810/)).

> **Notes**
>
> * You can't remove events from a visit.
> However, you can filter out visits and events before you export the visit data.
> 
> * The **Visit Browser** page is updated live to show the latest visits.

## Review search usage data by date interval

On the [**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/)) page, you can switch from the current selected date interval (last week, month...) to the previous period or next period by clicking
icon:chevron-left[alt=chevron-left,width=16] and
icon:chevron-right[alt=chevron-right,width=16] respectively in the upper-right corner.

> **Notes**
>
> * You can select a period that's incomplete (for example, the current month), in which case your date range selection will always include the latest available visits until the period ends (for example, the first day of the following month).
>  
> For example, you're reviewing data per **Month** and want to see how visits are trending for the first two weeks of the current month, so you click the right arrow.
> 
> * The date range can't exceed 365 days.

Alternatively, you can click the box containing the actual date range to access the **Report Period** dialog, and then [select the date range](https://docs.coveo.com/en/1704/) you want to review.

![Report period | Coveo](https://docs.coveo.com/en/assets/images/coveo-analytics/report-period-date-picker.png)

## Add visit filters

There are several ways to filter out irrelevant visits and to keep only those you want to review.
You can add inclusion and exclusion filters, or a combination of both.
When you only add exclusion filters, all visits are shown, except those containing an event that meets your criteria.

> **Note**
>
> [[PermissionFilters]][permission filters](https://docs.coveo.com/en/265/) act as inclusion filters if at least one event during a user visit matches the filter.
> Therefore, it's not recommended to use [permission filters](https://docs.coveo.com/en/1917/) to filter out user visits.
> 
> For example, the permission filter `Custom Event Value is not Case Deflection` will still show visits in which a case deflection occurs if another custom event was performed during those visits.
> Therefore, you should instead use [exclusion filters](#add-exclusion-filters) to filter out visits containing specific events.

### Add inclusion filters

. On the [**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/)) page, when you want to add an inclusion filter, click **an event** under **Show visits containing**, and then select one of four event categories (**an event**, **a search event**, **a click event**, or **a custom event**).

. Click icon:filter-add-2[alt=filter-add-2,width=16] to access the dialog to [add global dimension filters](https://docs.coveo.com/en/1675/), and then select the criteria you want.

![Global dimension filter with custom event | Coveo](https://docs.coveo.com/en/assets/images/coveo-analytics/global-dimension-filter-custom-event.png)

Once created, the filter appears in the top bar under **Show visits containing** and only the user visits meeting your criteria appear.

> **Note**
>
> Under **Show visits containing**, when you add a filter with a negative operator (for example, **is not** or **doesn't contain**), the filter acts as an exclusion filter rather than an inclusion filter.
> 
> For example, you want to review visits that contains events of users that aren't from New York with the following filter: `an event` where `City is not New York`.
> Therefore, all visits from New York users will be excluded.

### Add exclusion filters

. [[Exclude]] On the [**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/)) page, select the **Exclude visits containing** checkbox.

. Click **an event**, and then select between four event categories (**an event**, **a search event**, **a click event**, or **a custom event**).

. Click icon:filter-add-2[alt=filter-add-2,width=16] to access the dialog to [add global dimension filters](https://docs.coveo.com/en/1675/), and then select the criteria you want.

**Examples**

* To analyze user sessions containing a specific user query that doesn't contain a support case, select the checkbox to add the following filter:

![Exclusion filter with checkbox selected | Coveo](https://docs.coveo.com/en/assets/images/coveo-analytics/exclusion-filter-checkbox.png)

* To determine the site visit activities of a user who never uses the search bar, you'll need to exclude all visits containing a user query.

Once created, the filter appears in the top bar under **Exclude visits containing** and only the user visits meeting your criteria appear.

### Add multiple filters

You can add filters to apply on multiple event categories by clicking **And at least** and following the same steps as adding inclusion or exclusion filters.
Once created, the visits that appear will then match the multiple parameters.

**Example**

You want to browse user visits in which an [item](https://docs.coveo.com/en/210/) was opened and a case deflection occurred.

![Filters within the Visit Browser | Coveo](https://docs.coveo.com/en/assets/images/coveo-analytics/filter-example-case-deflection.png)

> **Note**
>
> When adding multiple filters to a single event category, the `AND` operator is used.

### Hide events

. When you want to discard events from remaining visits, select the **Hide events** checkbox, and then click icon:filter-add-2[alt=filter-add-2,width=16] to [add global dimension filters](https://docs.coveo.com/en/1675/).

**Example**

You want to focus solely on search events returning results to see, over a visit, whether users are clicking results.
Therefore, you remove search events without results by adding the following filter: `Has Results is False`.

. You can add alternative filters by clicking **Or where**.
Events matching one of these filters will be hidden.

![Hide events in the Visit Browser with Event Cause options | Coveo](https://docs.coveo.com/en/assets/images/coveo-analytics/visit-browser-panel-with-two-hidden-events.png)

Once created, the filters appears under **Hide Events**, and the events meeting your criteria are excluded.

> **Note**
>
> If a visit only has one event and this event is filtered out, the visit will be hidden as well.

## Leading practices

Consider the following leading practices when inspecting visits using the **Visit Browser**.

### Use a short time interval and leverage filters

When you open the **Visit Browser**, notice it filters the data based on the last day of data.
This provides you with a sample of fresh visits to start with.

Before you increase the time interval, narrow down the visits to what you're looking for by using filters.
Once the number of visits are reduced to single digits, start extending the time interval gradually, until you get the required number of visits.
Ideally, you should extend it up to a week, as the more you extend the time interval, the longer it takes to get results in the **Visit Browser**.

If you're interested in getting more visits, use the calendar arrows to move to the previous or next period.
This will provide you with a set of completely different visits.

### Bookmark your webpage

Once you're done establishing filters, you can bookmark the web page, or copy and paste the URL in the place of your choice to be able to later access the same state of the **Visit Browser** page.

### Using named filters

You can add a named filter with the current filters on a line:

* At the right-end of the bar, click [dots], and then select **Save filter as** or **Save filters as**.

* In the **Save as a Named Filter** dialog, in the first input, enter a meaningful **Filter name**, and then click **Save**.

* The named filter is now applied to the user visits.
For more information, see [Manage named filters](https://docs.coveo.com/en/1990/).

### Remove all filters

You can remove all the filters on a line, at the right end of the row, by clicking [dots], and then selecting **Remove filter** or **Remove all filters**.

> **Note**
>
> The **Visit Browser** is a tool provided to explore the visits and events, without requiring any programming or scripting, hence it comes with its limits.
> 
> If you have knowledge of programming or scripting languages, it's possible to explore the same raw events with Snowflake (see [Manage raw data](https://docs.coveo.com/en/1856/)).
> The [Build visit cards](https://docs.coveo.com/en/n3vf0441/) article explains SQL query patterns used by the **Visit Browser** to generate the same results.
> This could be used as starting point, from which you can fully customize your own personal tool.

## Browse user visits

. On the [**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/)) page, after setting the date interval and adding filters, click a visit row to view all events that occurred in this particular visit.

. Click an event row to view available information on this event, such as [dimension](https://docs.coveo.com/en/258/) values and the response time (see [Dimensions](https://docs.coveo.com/en/1904/) and [Reference](https://docs.coveo.com/en/1964#reference)).

> **Notes**
>
> * You can sort events in a visit by **Order** and **Time**.
> 
> * You can check that events are logged properly by ensuring the [metadata](https://docs.coveo.com/en/218/) of each event is complete and valid.

## [[Export]]Export visit data that meet your criteria

. On the [**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/)) page, click ![Export icon | Coveo](coveo-analytics/export.png) in the upper-right corner.

> **Note**
>
> If the Export visit data using current filters icon is grayed and unresponsive, you don't have the [required privileges](#required-privileges) to perform this action.

. In the **Export Estimate** dialog that appears and shows the number of events to be contained in the export, click **Add an Export**.

The export is created and available for download on the **Data Exports** tab of the [**Raw Data**](https://platform.cloud.coveo.com/admin/#/orgid/usage/raw-data/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/usage/raw-data/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/usage/raw-data/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/usage/raw-data/)) page.

> **Note**
>
> When the export contains more than 3 millions events, the events are sorted randomly rather than by date and time.

.. In the navigation bar on the left, under **Analytics**, select **Raw Data**, and then select the **Data Exports** tab.

.. On the [**Data Exports**](https://platform.cloud.coveo.com/admin/#/orgid/usage/raw-data/data-exports/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/usage/raw-data/data-exports/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/usage/raw-data/data-exports/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/usage/raw-data/data-exports/)) page, click the newly created export, and then click **Download** in the Action bar to retrieve the ZIP file.

> **Note**
>
> After the visit data has been exported, the order of the columns may be rearranged in a spreadsheet in which the corresponding CSV file has been imported.

## Review a visit with more than 250 events

To review a single visit containing more than 250 events, you must export the visit data as follows:

. On the [**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/)) page, click a visit containing more than 250 events.

. Under the 250th event, click **Create**.

. In the **Export Estimate** dialog that appears, check the **Use Dimension Display Names** box if you want the export to show the dimension names as they appear in Coveo Analytics [reports](https://docs.coveo.com/en/266/) (for example, "Origin 1 (Page/Hub)").

> **Note**
>
> By default, exports show the dimension API names, for example, `originLevel1`.

. In the navigation bar on the left, under **Analytics**, select **Raw Data**, and then select the **Data Exports** tab.

. Click the newly created export, and then click **Download** in the Action bar to retrieve the ZIP file. The export contains all missing events.

## Reference

The body of the [**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/)) page is essentially a table listing all the visits that match specific criteria.

> **Note**
>
> When no values are returned for a given field, `n/a` is shown in the column row.

### Start date column

Indicates the date and the hour when the user performed their first event on the search interface.

### Visit duration column

Indicates the time between the first and last event performed by a user during a visit (based on the event [visit ID](https://docs.coveo.com/en/272/)).

> **Notes**
>
> * When hovering the column value, you can see the start and end time of the user visit.
> 
> * An `n/a` value means that the related visit only contained one event, therefore preventing [Coveo Analytics](https://docs.coveo.com/en/182/) to calculate the actual visit duration.

### User name column

Indicates the user's display name, if they were authenticated to the search interface when they performed the event.

### Location column

Indicates, when available, the country, province/state, and city from which the user performed the event, based on their IP address.

> **Note**
>
> The location of the user can be `n/a` when Coveo isn't able to parse the user IP and determine the location of the user.
> For example, this can happen when the IP is invalid or it's not parsed properly.

### Browser column

Indicates, when available, the web browser name and version with which the user performed the event.
This information is extracted from the HTTP user agent identification.

> **Note**
>
> The browser of the user can be `n/a`, when the user is a custom bot or a crawler, for example.

### Event count column

Indicates the number of events that occurred in the visit.

### Visit row

When expanding a visit row, the **All Visit Events** table columns indicate general information about each performed event:

#### Order

Indicates the rank of the event.

#### Time

Indicates the time at which the event was performed

> **Note**
>
> In the **Visit Browser**, events are displayed in your time zone.

#### User name

Indicates when the user is authenticated to the search interface, the display name of the user that performed the event

#### Type

Indicates the type of the event, which can be **Click**, **Search**, or the name identifying the custom event or its category

> **Note**
>
> (For custom events only) You can use the Type values when filtering on the Event Type dimension.

#### Cause

Indicates (for click and search events only) the name of the [search or click event cause](https://docs.coveo.com/en/2948#click-event-cause) and [Search Cause](https://docs.coveo.com/en/2948#search-event-cause).

#### Details

* For search events, the details indicate the query text entered by the user in the search box (if any), or the selected facet value and the underlying advanced query expression.

* For click events, the details indicate the title and URL of the item on which the user performed the click.

* For custom events, the details indicate the name of the custom event cause.

> **Note**
>
> You can use the **Details** values when filtering on the Event Value dimension.

#### Event row

When expanding an event row, you can see all the [dimensions](https://docs.coveo.com/en/1904/) and their values passed along with the performed event indicating the context of the recorded event.

## Required privileges

The following table indicates the required [privileges](https://docs.coveo.com/en/228/) to view and to edit elements of the [**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/)) page.

[cols="3",options="header"]
|===
|Action     |Service - Domain   |Required access level

|View user visits
a|
Analytics - Analytics data

Analytics - Dimensions

Analytics - Named filters

Analytics - Permission filters

Organization - Organization
|View

.2+|Export visit data
a|
Analytics - Analytics data

Analytics - Dimensions

Analytics - Named filters

Analytics - Permission filters

Organization - Organization
|View

|Analytics - Data exports
|Edit
|===