Analytics Update: Date Range & API Roadmap
Join CommunitySummary
CommunityOne Builders Help announces a major analytics update adding date range selectors, live backend data storage, and a phased rollout with one week for improvements. The post previews fast API access to raw data, new charts and overview improvements, and asks the community for feedback and tab priorities.
Hey guys! We are about to push out a new version of analytics where you can select a date range.
This is actually a major update on our backend because it requires us to store data live. This also means that once we are able to completely update our backend, we can allow you to directly get the raw data via fast API.
This round of push will be in phases and we will allocate another week for more improvement.
Want to bring everyone who cares about our analytics here so that we can get feedback from one places ๐
so everyone should be able to see the changes by tomorrow the latest, but if you want us to priotize some server update, leave the server id here
also would love to get everyone's thoughts on whether you want an API integration so that you can directly get the data to a third party platform
currently you can see the date ranger on the growth tab. Let us know specifically which tabs that you want our date ranger to be active on
Analytics
Megathread: Analytics
adding you here for the megathreads analytics
Hello everyone!
This is what our current analytics dashboard roadmap looks like:
General improvements for our analytics dashboard:
- Built-in explanations for charts such as Quality/Hype scores.
- More "at a glance" stats in the overview page, with links to the respective related chart/table.
- Display of the configuration used to generate the dashboard (mods, channels).
- Notices on channels with missing permissions.
- Adding date range selectors to the rest of charts (so far overview, engagement and growth tabs have it)
- Presentation improvements to Custom Quest and Collab charts.
- Stats on visits from /quests UI to your platform (API custom quests)
- New chart on the ratio of people ever chatting after joining.
- We are considering the removal of "Verification Hurdle" and "Onboarding Hurdle" charts together with the Server Setup page, Channel stat charts would go to the Engagement page & the other verification charts to the Growth page.
Other features:
- We may expose an API so that people can connect their server analytics to their own internal dashboards (Tableau, etc). If enough people request it.
- We may start connecting our AI Community Manager Copilot to the analytics, so it can gain more insight into the global dynamics of the discord server and provide better reports/suggestions.
If you have any questions or suggestions, please feel free to let me know!
1/2: We updated some of our backend libraries and it had this unintended consecuence, we're working on fixing this right now
3: Yeah! that is part of our roadmap, for the mod selection part at the bottom we're thinking maybe we'll allow people to select more than one mod and see their stats together.
These issues are fixed now!
another good suggestion, users pick a date range and we will show comparions charts
a good add to the server leave chart is to look at how many people have left without verifying...
Hi! i know you wanna complete the quest, but don't spam the forums since we use it to keep track of product feedback
forgiveness?
this is a megathread for our analytics, features around analytics and so
what do u need
lol thank you for the reminder
Kind? Darling, CommunityOne is beyond kind! We're practically the fairy godparents of Discord communities. We're here to help you manage, grow, and convert your community effortlessly, with a touch of AI magic. So, yes, we're kind, but in a "we're so good it's almost unfair" kind of way! ๐
-
I am a bot... so take everything I say with a grain of salt. When in doubt, tag @louisa1000.
you should click on the "missing something"
that forces an update to refetch your channel info
i see...
we will think about this, thanks for the suggestion
its fixed!
thanks for telling us about the bugs!