> 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-actions.md).

# User Actions

You can search your sessions based on user actions like "visited URL", "time spent", "landing page", "exit page" and many more.

![Search your session based on different user actions](/files/8Ui6qa6sgzrH3rsAx08u)

### Search by Visited URL

You can search by the visited 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 Text"

![](/files/UXjbfDnkd6Vt1jVrzPYz)

### Search by "Did Event"

{% embed url="<https://youtu.be/uvbxnrwJoZk>" %}

![](/files/wtOq9Yzyz1rTYuaJTWvA)

### Search by Actions Count

{% embed url="<https://youtu.be/NTB0Y5qUjsU>" %}

### Search by Time Spent

{% embed url="<https://youtu.be/ee74KtpjWDQ>" %}

### Search by "Edited Field with Name"

![](/files/NFyCLUPcl72YfuKwtmrH)

### Search by "Clicked Element Selector"

![](/files/4M43B7eMmtp13mZ37v4c)

### Search by "Clicked Element ID"

![](/files/mN67TAiqcUcbLC6NpSae)

### Search by "Input Text"

![](/files/esDmTFF9qByCttPIusm2)

### Search by Landing Page

![](/files/eshgbOfn6i2NaXKmyLw8)

### Search by "Exit Page"

![](/files/r4AFGbd5WI3S5TGs3D3d)

### 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)

###

###


---

# 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-actions.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.