# Time Spent Average Time Spent represents the average time live users spend actively engaging with a page. ### **How We Track Time Spent** We measure "Time Spent" as the total time a user actively spends on a page. A page is considered **active** when it is open on the user's device and they are engaging with it. Engagement includes actions such as scrolling, moving the mouse, clicking an element, or typing—anything that indicates the user is still present and interacting. If no activity is detected for **60 seconds**, the timer pauses until the user resumes interaction. This ensures that Time Spent reflects actual engagement rather than just the time a page remains open in a background tab. ### **How Different User Actions Affect Time Spent** * **Switching Tabs** → If a user navigates to another tab or program while keeping your site open (that is, your website is still open on another tab but is not active), time spent is **paused** until they return to the page. * **Closing the Page** → Time spent **stops** when the user exits the page. * **Reopening a Closed Page** → If the user returns to the page later, a **new session** starts, and time spent resets. * **Refreshing the Page** → A refresh restarts the time spent count. ### **Why Time Spent Matters** Time spent is a strong indicator of **content quality and user interest**: * High time spent suggests users find the content valuable and engaging. * Low time spent may indicate a need for more engaging elements, improved readability, or a better user experience. If you see any discrepancy in time measurements, please contact us on , and our team will investigate and assist you. --- # 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://govisibl.gitbook.io/help-docs/metrics/time-spent.md?ask= ``` 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.