Let's crowd source the gaps we are finding between old (CMR) and new (Community Analytics) reports. I'm sure we all are using them in slightly different ways, so things that are problems for one might not be problems for others. However, we are also likely to run into some things that are common shortcomings. Please help to fill in the table below. And consider adding comments to indicate use cases - WHY these shortcomings or gaps will be problematic for you.
|Reporting feature||Top level or Place level||Gap||Customer Comments||Customers to whom this is important||Product team notes|
Include Subspaces checkbox
There is now no way to collect data for a whole "collection" of spaces.
Example Use Case: We move archived content to limited access subspaces so that we can maintain analytics and history. It will be much harder to include these analytics moving forward.
Carbon Black Use Case: Departments have a main space with subspaces for subdepartments or teams. Not being able to pull a consolidated list is a show stopper for me.
Add filter options - to allow filtering on custom profile fields
|Top level and Place level||Can't see differences in how different parts of the company interact with the overall site or specific places within it.||This was a hard won option added into CMR to assist customers in providing the kinds of reporting that executives demand of community managers. The loss of this filtering capability negates much of the value of the existing reports because a significant level of detail is missing in terms of how individual companies define themselves and thus want to report based on.|
User-to-user interactions - custom profile filtering (CMR)
(See Department Interactions in Community Analytics)
|Top Level||Can only see at Department level in Community Analytics. CMR allowed filtering using custom profile fields as well|
This was a hard won option added into CMR to assist customers in providing the kinds of reporting that executives demand of community managers. The loss of this filtering capability negates much of the value of the existing reports because a significant level of detail is missing in terms of how individual companies define themselves and thus want to report based on.
Logicalis Use Case: As a global company, we woud like to improve the interactions between specialists that belong to different geographies, and for such we must be able to see the graph showing interactions between countries.
|Content Leaderboard||Place Level||There is currently no replacement for this report.||This report has been used to identity the pieces of content that generated relevant increases on the number of views in a certain place.|
|Top Content/Places (Under Community Usage Dashboard)||Top level||"Hidden Content" and "Hidden Place" for many of the results, even for Full Access admins. In CMR we could see the full list regardless of whether they were private/hidden.|
We can't report properly if we can't see half the items on the Top Content and Places leaderboards.
|Top Content||Top level||CSV is seriously lacking in information compared to the community manager reports. CSV only shows top 20, compared to top 1000 and no information on author, place, content type or place type. (CSV examples provided in next set of tables, for comparison purposes)||Because only top 20 by like, view, share etc are available, no easy way to compare the most viewed piece of content in a space with the most liked, since they don't always show up in the same top 20, and there's no way to make sure the content is in the same space for comparison. We use this report to determine a huge amount of comms strategy, making sure we meet benchmarks, checking for successful implementation of programs|
|Questions - Average Response Times||Top level and place level||No report to determine the average length of time from when a question is posted to its eventual marking as answered|
We use this report heavily to measure how our departments are doing in terms of answering questions in a timely manner. This info is regularly reported to department heads and execs, both as a site-wide number and each department space individually
In the comparison report, this was listed as an external feature, but we used it frequently in our internal instance.
Commvault uses this report as a way to report personal metrics around answer platform questions to enable employees using the community.
|Top Successful search Queries||Top level||No replacement report||This report was used on a monthly basis to help teams determine tags and promoted search results to focus on for the month.|
CSV Report Comparison
Images pasted in are the CSV downloads, not the actual charts shown inside the interface