Gather reporting in ExploreAbgeschlossen
There is a few information about the Guide usage, that is currently not available in the predefined Explore Dashboard. It would be interesting to add more capabilities to the Guide dashboard in Explore, to understand better the KB usage, the most consulted articles, deflection details, etc.
Many thanks for sharing your primer needs on community reporting, this is beyond valuable for us to prioritize the right metrics and attributes for the upcoming dashboard.
Let me share the good news, the community dataset is currently in the pipeline and we plan to release it in Explore in Q1 next year. Our minimum goal is to bring parity with the data in Insights, moreover, we're currently exploring what additional information we can include in the new dataset. I'll update this thread once I can share more details.
We really appreciate your contribution!
Thanks for posting this request, feedback like this is very helpful. I have some good news, getting more Guide data into Explore is my top priority, and have just started the process. I don't have dates just yet, but will circle back here once we have a concrete timeline to share.
In the meantime, I'd love to hear more on your goals with Guide data and how it might help you and your team. The more information the better, as it helps us deliver more powerful dashboards.
I have a few suggestions of what we'd like to see:
- page views
- time spent on each page (how long was it open)
- how many single users viewed the page (if signed in)
- link clicks from the page (we do a lot of hyperlinking articles to each other)
- search terms entered in our knowledge base
- which articles were clicked in relation to which search terms
That should be enough to go on for the moment :)
Some of this stuff is in Insights, which is being retired! This makes me sad but I can see that Explore is a really great new tool - it's just too support ticket-focused for our documentation team to leverage at present.
That should be enough to go on for a bit :)
Hi @... - a year on, is there any update on this? We've just launched our community on Zendesk and are finding reporting really, really painful. With the launch of Explore, we've lost the little data we had and the only solution seems to be to build something manual using the API.
To add to @...'s post above, the things I need are:
- How many users are following each topic, and who they are
- How many users logged into the community
- Which users have been most active
- Which users have not been active (and therefore need to be re-engaged)
- Most popular content / discussions / people in the Community
- Which users have what badges
- How many users have a profile picture
- For all of the above to be exportable, for the purpose of email campaigns
These are all really basic metrics that every community platform I've used in my career offer.
Hi @..., is there an update on the release timeline for the Gather dataset in Explore?
I just wanted to see if the release date for this dataset has firmed up at all, and if it will be available soon as a beta test if we can opt-in. We have a team that could really use more detailed reporting on a topic that we are using for product suggestions.
Hi Ben Fulton,
The plan hasn't changed, we're planning to release the dataset and dashboard towards the end of this quarter. The release will be a GA, no opt in necessary.
Hi Orsolya Forster,
Any update on the release of this dataset now that the quarter has closed?
We're working on the finishing touches, the dashboard rollout is expected to start in a few weeks.
Hey Orsolya Forster, excited to have found this thread! We're building our community forum and suffer from data as well. I felt it'll super helpful to be able to see the most active users. Would be great if the coming dashboard can cover that part!
Happy to share that we started rolling out the community dashboard and dataset yesterday. By May 25, the new reporting will be available for all customers. For more details, you can check the announcement. With this note, I'm marking this thread "Complete".
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.