> For the complete documentation index, see [llms.txt](https://docs.browsee.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.browsee.io/understand-your-users/session-search/user-attributes.md).

# User Attributes

### Search by "User ID"

You can search your sessions with:

1. **User ID that is given by Browsee** - Browsee gives each of your users a 16-digit user ID, which you can use to search all the other sessions for that user. This means if the user is using the same machine and the same Browser, we will identify all these sessions with a 16-digit user ID. However, if the same user is coming from a different device or browser, we will not be able to recognize them. 
2. **User ID sent by you using an Identify Call** - You can also identify your users with any Personal Identifiable Information (PID) like name, email, phone, or database ID, and then you can look for that PID to watch all the session recordings of that particular user. [Read here on how to send identify calls to Browsee.](/integration/api-calls/identify-call.md)

![](/files/gjlhSGp2xeZ5ffCVOE0g)

### Search by "Tags"

You can send tags to Browsee like "Paid", "In Trial", "Signed Up", "Logged In", etc. and then you can search your session recordings by these tags. [Read here about how can you send tags to Browsee](https://docs.browsee.io/integration/api-calls/identify-call). 

![](/files/VW8uFHd5E7KUqMJWtIwF)

### Search by "Referred By"

You can filter your session recordings by referrals in order to understand why some of the referrals are not performing well. 

![](/files/HGnnOGzMiBrJc45s7cFQ)

### Search by "Browser"

Sometimes, people see a higher bounce on a particular browser and it is hard to figure out a reason. You can filter your session recordings by any browser and watch a few sessions in order to get some insights.

![](/files/LvaBIcXuX2GzEtSadlDt)

### Search by "City" or "Country"

If you have users across geographies, it is important to understand the behavior of people from different places in order to better understand their problems. You can also filter your sessions in Browsee by city or country.

![](/files/1DiajhXhcJG6tTRVr9Pm)

### Search by "Screen Width & Height or screen resolution"

Facing higher drop from certain screen resolution? Don't wonder anymore. To get more insights, you can filter the session recordings by that particular resolution.

![](/files/VvZKCuxTjjA0nQfzALp6)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.