> For the complete documentation index, see [llms.txt](https://guides.mangoapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.mangoapps.com/admin-guide/analytics/home-dashboard.md). # Home Dashboard ### Overview Dashboard analytics provide administrators with comprehensive insights into dashboard performance through two distinct analytics layers. These views track engagement across web and mobile platforms, offering a data-driven look at how users interact with company-wide communication hubs.
{% hint style="info" %} **What do we mean by "Dashboard"?** In the case of Dashboard analytics, "dashboards" refer to admin-managed "Home" pages rather than user-customized variants, ensuring data reflects official company communications. {% endhint %} *** ### Overall Dashboard Analytics For a broader perspective, the Overall Dashboard Analytics view (located under **Admin → Analytics → Dashboards**) provides an aggregated look at performance across the entire domain. * **Aggregated Performance**: This view summarizes the ratio of active to total dashboards and plots a collective view trend. These metrics account for both active and inactive dashboards to provide a full historical context. * **Engagement Benchmarking**: The Dashboard Engagement Table allows admins to compare different dashboards side-by-side. The table identifies audiences, last publication dates, and total views, making it easy to see which dashboards are driving the most employee engagement. * **Data Integrity**: Analytics data remains consistent even as your organization evolves. Historical views and clicks from deleted users are preserved in all trends, and metrics from deleted dashboards remain included in aggregated totals to ensure long-term reporting accuracy. *** ### Per-Dashboard Insights Administrators can access detailed performance data directly from any admin-configured dashboard. * **Summary & Trends**: Dashboard analytics track all-time **Total Views** and **Total Clicks**, including interactions from widgets that have since been removed. A dual-line trend chart displays engagement patterns over time, with granularity that automatically adjusts from days to months based on the selected reporting period. * **Link Engagement**: A detailed table tracks clicks on all internal links within Quick Link and Rich Text-based widgets. This data includes a platform-level breakdown (Web vs. Mobile Native) and is filterable, searchable, and exportable for offline analysis. * **Click Maps**: A visual overlay displays the all-time click distribution across active widgets. This map allows admins to see exactly where users are clicking on both web and mobile layouts, helping to optimize dashboard design and content placement.
--- # 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://guides.mangoapps.com/admin-guide/analytics/home-dashboard.md?ask=&goal= ``` `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.