> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/reference/product/workforce-productivity/app-and-url-tracking.md).

# App & URL Tracking

## Overview

We360.ai tracks application and URL usage to provide organizations with clear visibility into how time is being spent across different digital tools. This feature helps teams identify their most utilized platforms and measure focus time accurately.

## Supported Platforms

* **Desktop Agent**: Fully supported on Windows, macOS, and Linux — including **Citrix, RDP, and VDI environments**. The desktop app passively watches the active window title and records the application or domain URL in focus.
* **Chrome Extension**: A dedicated Chrome Extension is available for enhanced browser-level URL tracking and productivity insights.

## How it Works

1. **Focus Capture**: The agent detects which application or website is currently active on the user's screen.
2. **Per-Second Measurement**: It records the duration the application or URL remains in focus with **per-second granularity**, ensuring precise time accounting even for rapid task-switching.
3. **Analytics**: The tracking data is aggregated and displayed on the We360.ai dashboard, allowing administrators and managers to view usage reports and activity percentages per user or team.

## Productivity Classifications

To make the data actionable, administrators can categorize different applications and URLs based on their organization's specific needs. For example, a design tool might be categorized as "Productive" for a design team, while a social media website might be marked as "Unproductive". These classifications power the overall productivity score for each employee.


---

# 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.we360.ai/reference/product/workforce-productivity/app-and-url-tracking.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.