# Session Search

Browsee automatically captures all your user's sessions and indexes them for easy search

You can search session by

### User Actions

* *Urls* visited by users - Also works out of the box for SPA's like React, Angular, Vue.
* *Text* user clicks
* *CSS Selectors* of elements users click
* HTML *ID* of elements clicked
* *name* of form fields users edit

### User Experience Issues

* *Errors* - These are errors encountered by users in their sessions
  * Javascript Errors
  * Network Issues like slow ajax calls, 50x errors, etc.
  * Broken Links
* *Rage Clicks* - These are signs of users frustration

### Identify Call

* *User Id* - Provided in `identify` call
* *Tags* - Provided in `identify` call
* *name/email* - Provided in `identify` call
* *Custom Attributes* - Attributes other than the name, email, tags provided in `identify` call
* *Identified -* If a user was identified via an `identify` call

More about identify calls [here](/integration/api-calls/identify-call.md).

### Session Parameters

* *Session Duration*
* *Referral* - Domain from which the user landed
* *UTM Parameters* - source, medium, campaign, term, content. Picked from the session's first URL.

### Device Details

* Operating System
* Browser
* Device - Mobile, Desktop, etc.
* Country

### Search by URL

You can search by the URL or URL pattern that a user has visited. For searching by URL/URL pattern, you need to enter the path (i.e.) anything after your domain. So, for example, in the case of <https://browsee.io/login>, you just need to enter "/login" in the search box as shown below:

![Search for exact URL match](/files/-MQGHfNIL3vvwW2XZoDc)

For searching by URL pattern, you can change the dropdown to "Contains" instead of equals and you can look for any pattern like "session" or "product" etc as shown below:

![Search for a URL pattern](/files/-MQGHZ6Bhby4T1RT6uJ8)

### Search by "Clicked Element ID"

You can search your sessions by Element ID (commonly used in HTML, CSS elements).&#x20;

```css
<button type="button" id="submit">Sign Up</button>
```

&#x20;If you will just look at the button here, the ID of the button is "**submit**". You can simply search by this ID in your sessions as shown below:

![Search by Element ID](/files/-MLBwK-StODtSJ4Kynn2)

### Search by "Clicked Element Text"

You can search your sessions by simply searching based on the text of the clicked element.&#x20;

```css
<button type="button" id="submit">Sign Up</button>
```

&#x20;If you will just look at the button here, the text of the button is "**Sign Up**". You can simply search by this text in your sessions as shown below:

![Search by Clicked Element Text](/files/-MLBxUfwqCJdqvwcq3uO)

### Search by "Edited Form Field"

You can search your sessions by simply searching based on the name of the edited form field.

```css
<input type="text" placeholder="Email" name="email">
```

&#x20;If you will just look at the input field here, the name of the field is "**email**". You can simply search by this text ("email") in your sessions as shown below:

![Search by Edited Form Field](/files/-MLBxsgcvaGFGpKzc_Mj)

### Search by "Clicked Element Selector"

You can also search your sessions by CSS selectors (commonly used in HTML, CSS elements). You can use [Browsee Chrome Extension](https://chrome.google.com/webstore/detail/browsee-analytics/acojndadomohnjafbdclbonkohefnmhc?ref=producthunt) to identify the CSS selector of your element.

You can simply search by this ID in your sessions as shown below:

![](/files/-MLBwbDKx0GodR24p8bg)

### Search by User Attributes

You can send [attributes in Identify calls](https://docs.browsee.io/integration/api-calls/identify-call). Once, you will start sending us these user attributes, you can filter your sessions by those attributes.

You can search by user attributes as shown below:

You can even search by date type attributes:

&#x20;You can also [save it as a segment](https://docs.browsee.io/understand-your-users/circles) and [add it to your dashboard](https://docs.browsee.io/understand-your-users/configure-dashboard) or [daily summary emails](https://docs.browsee.io/understand-your-users/circle-analytics-and-alerts). You can even subscribe to these segments &#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.browsee.io/understand-your-users/session-search.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.