> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/zoom-workplace/zoom-whiteboard/zoom-whiteboard-analytics-and-reporting.md).

# Analytics and Reporting

Review organizational patterns and prepare aggregate insights for reporting workflows.

Use Zoom Whiteboard analytics to understand adoption, collaboration, and activity trends across your organization.

### Usage and Engagement

#### <mark style="color:blue;">Monitor and analyze whiteboard usage and engagement</mark>

Administrators can access a **Whiteboard Admin Dashboard** through the Zoom Admin Portal to monitor usage metrics and engagement across their organization. The dashboard provides visibility into whiteboard creation rates, active collaborators, and overall engagement trends, enabling data-driven management of collaboration initiatives.

#### <mark style="color:blue;">Track participation and activity metrics</mark>

Whiteboard engagement analytics show user participation patterns such as editing frequency, object creation, and team collaboration density. Administrators can export aggregate analytics data for deeper review or integrate it into internal reporting systems for productivity tracking. Administrators can access Whiteboard usage analytics and dashboards through the Zoom Admin Portal for oversight of adoption and engagement trends, subject to applicable data privacy laws and [Zoom's Privacy Statement](https://www.zoom.com/en/trust/privacy/privacy-statement/).

{% hint style="info" %}
**Note**

Analytics data reflects aggregate collaboration activity and does not expose individual content or whiteboard data. Administrators can manage visibility through Zoom’s account-level privacy controls.
{% endhint %}

### Reporting

#### <mark style="color:blue;">Participation Reports track engagements between participants and contributors</mark>

Whiteboard owners and co-owners can generate participation reports to track engagement across whiteboarding sessions. Reports are available through the board activity log and history.

Each report includes:

* **Overview:** Aggregate metrics including total participants, number of active contributors, and total whiteboard actions
* **Participants:** A per-user breakdown distinguishing active contributors (users who made changes) from view-only participants (users who opened the board without taking action)
* **Analytics:** A timeline view of usage trends with configurable sort options

Tracked actions include adding objects, editing content, commenting, deleting items, and reactions—each with timestamps. This gives board owners and co-owners a picture of who's contributing and how, without requiring a separate analytics tool.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.zoom.com/zoom-workplace/zoom-whiteboard/zoom-whiteboard-analytics-and-reporting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
