You can monitor activity data for your community using in the Reporting dashboard in Support. Statistics include the number of posts created, how many users have viewed posts, and the total number of votes, subscriptions, and comments.
Viewing community activity for your Help Center
You can view community analytics for your Help Center in the Reporting dashboard in Support.
To view community data
- In Support, click the Reporting icon () in the sidebar, then click the Community tab.
The Posts dataset is open by default.
- If you have multiple brands, click the All brands drop-down menu, then select a brand if you want to see data for that brand only.
All brands is selected by default, and includes the combined activity of the communities in all of your Help Centers.
- Click the Reporting period drop-down menu, then select an option if you want to change the reporting time frame.
Select Custom to enter a specific start and end date.
- Click any of the five datasets at the top to drill down.
Each dataset displays a graph of daily activity and a table, below the graph, of top posts for that dataset. Datasets include:
- Posts is the total number of new posts created in the community during the reporting period.
- Views is the total number of views for posts in the community during the reporting period, including internal agent views.
- Net Votes is the difference of all the positive and negative votes on all posts in the community during the reporting period.
- Subscriptions is the total number of user subscriptions for topics and posts in the community during the reporting period.
- Comments is the total number of comments on posts in the community during the reporting period.
- Hover your mouse over a node to see the total number for that day.
Following up on community data
Community statistics give you insight into which questions customers are most interested in. You can then take action based on this information.
For example, you can track the posts that are most and least popular, or have the most comments, to understand more about the subject. You can then review the post to see if there is some follow up action required, for example, whether this area requires a knowledge base article to explain the subject in more detail, or a ticket needs to be raised to request a new feature.