CommunityOne has released a new version of its analytics dashboard, with a major focus on clarity, better community insights, and improved performance. The update refreshes how the dashboard is laid out, what metrics are shown, and how teams interpret member activity.
Below is a structured breakdown of what changed and why it matters for monitoring community health and growth.
What’s new in CommunityOne analytics: simplified dashboard and layout
CommunityOne describes this as the biggest analytics update made in over two years. The redesign follows a “less is more” approach by removing complex or redundant charts and making the interface easier to read.
Instead of forcing users to interpret dense visuals, the team also adds clearer chart annotations—so it’s easier to understand how to read what’s on the page.
The dashboard layout is also “prettier” and more focused on the actions teams typically want to take, rather than presenting only raw information.
New tabs and chart annotations to support engagement and setup actions
To make analytics more action-oriented, the update introduces new navigation tabs.
Rather than keeping all analytics views in one place, CommunityOne adds tabs designed to support specific tasks—such as:
- Engagement
- Service setup
In addition, CommunityOne annotates many charts directly in the UI. This is intended to reduce confusion and improve interpretation, especially when charts are not self-explanatory.
KPI updates: removed metrics and new weekly/monthly growth R
Alongside the redesign, CommunityOne updates its KPI set. Some older KPIs are removed, while more relevant growth indicators are added.
A key example highlighted in the update is adding weekly and monthly growth R for Discord. These additions help teams track momentum across shorter time horizons (weekly and monthly), rather than relying only on older or less targeted indicators.
The overall goal is clearer reporting: show the metrics that better connect activity and growth to the community’s current state.
Bot detection analytics: identifying likely bot accounts and why
CommunityOne’s analytics now includes bot detection analytics that aims to answer two questions:
- Who looks like a bot?
- Why does the analytics think they are a bot?
The update doesn’t just flag likely bot accounts—it also explains the reasoning using additional KPIs. The transcript emphasizes that you can see “not only who is the bot but why we think that they are [a] bot account,” supported by extra signals.
This matters because community managers often need to understand whether suspicious accounts are simply inactive or actually exhibit patterns associated with automation.
Social reach and member health: average social reach plus Fallen Angels/Rising Star
Beyond bots, CommunityOne introduces new ways to interpret member engagement and relationship-building inside the community.
New metric: social reach
CommunityOne adds a social reach metric designed to measure how connected members are within the community. It uses average social reach to quantify engagement and estimate the likelihood of members forming connections (described in the transcript as friend-forming potential).
New concepts: Fallen Angels and Rising Star
To help teams spot changes in momentum, CommunityOne introduces two membership status concepts:
- Fallen Angels: members losing interest
- Rising Star: members gaining momentum
These labels are intended to make retention and ongoing community health monitoring more practical. For example, the Fallen Angels concept prompts teams to check in with members who may be falling off.
Taken together, social reach plus these membership status concepts give a more actionable view of who may be drifting away and who is actively building traction.
Performance and support improvements: faster backend, run rate changes, better error guidance
CommunityOne also updates the analytics infrastructure to improve performance and reliability as usage grew.
The transcript notes that the “run rate” is now described as about one-tenth of what it was before. This reflects backend and scalability adjustments made for larger communities and projects.
In addition, the update includes better error guidance. When something goes wrong, users receive more guidance—specifically mentioned are issues related to Discord permissions and email permission problems, along with more direction for resolving them.
Finally, CommunityOne continues to offer a free analytics version and encourages viewers to use the analytics and join its Discord for feedback.
Quick recap: the main changes in this analytics update
- Simpler dashboard layout following a “less is more” approach
- New tabs designed around actions like Engagement and Service setup
- Annotated charts to help users interpret analytics more easily
- Updated KPIs, including weekly and monthly Discord growth R
- Bot detection analytics that explains why an account appears bot-like
- New social reach metric using average social reach to estimate engagement and connection potential
- Member health concepts: Fallen Angels and Rising Star
- Improved performance and backend reliability, including run rate adjustments
- Better error guidance for permission-related issues
Conclusion
CommunityOne’s analytics update streamlines the dashboard for readability, adds action-focused navigation, and refreshes the KPI set with metrics like weekly/monthly Discord growth R. It also expands community insights with bot detection reasoning, a social reach metric based on average social reach, and member health status concepts (Fallen Angels and Rising Star). The release also improves backend performance and offers more helpful error guidance when permission issues occur.
