Admin Analytics
Admin Analytics
Section titled “Admin Analytics”Use admin analytics when you need to understand how the workspace is being used over time. This page is about recurring patterns such as adoption, participation, follow-up behavior, and reliability trends, not only one-off incidents.
Before you start
Section titled “Before you start”- Decide which decisions the analytics review should support: rollout expansion, support staffing, training, or policy changes.
- Compare metrics across a consistent time range so short-term noise does not drive long-term defaults.
- Validate metric definitions before using them for leadership or customer reporting.
Questions this page should help answer
Section titled “Questions this page should help answer”- Who is using the platform and how often.
- Which meeting types are generating the most recap and search traffic.
- Where quality regressions or support hotspots are appearing.
Recommended review areas
Section titled “Recommended review areas”- Some signals still live in feature-specific surfaces such as recap, search, or network diagnostics.
- Combine product usage with network and support signals when you want the cause, not only the symptom.
- Separate rollout questions such as “who adopted the workflow” from incident questions such as “who experienced degraded meetings.”
Troubleshooting
Section titled “Troubleshooting”The analytics trend conflicts with what support is hearing
Section titled “The analytics trend conflicts with what support is hearing”- Check whether the reporting window matches the period of the reported incidents.
- Review network diagnostics and support cases before changing product defaults.
- Confirm that pilot users, guests, and internal teams are not being grouped together in a misleading way.