> 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/automatic-session-tags/high-engagement.md).

# High Engagement

For makers it is extremely important to understand what features Engaged Users are loving on the website. Browsee also tags `Engaged Sessions`to help you identify the users that love your features and products.

#### How is High Engagement Determined ?

Engagement is computed from user activity. Typically, interacting with the page, scrolling and browsing will be considered engaged activity.

For example whenever a user clicks on a button, we start a timer of engaged activity, if the user continues to interact with the page, the timer continues to run. However, if we notice inactivity or idle behavior, the engagement timer runs out and we stop counting the time into engaged activity.

Sessions with engaged time above a certain threshold are marked as high engagement.


---

# 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/automatic-session-tags/high-engagement.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.