I am regularly trying to improve the story that I tell our current and prospective users as well as my senior leaders. I find that metrics and analysis is a full-time job.

One question that came up today was repeat visits to a given piece of content.

A few questions:

When we look at the view count of a record, does this track each time it is clicked on rather than unique users viewing it? (so if 10 of us visit it twice, the view count would be 20 or would it be 10?)

If the former, is there a metric that tells me how many of those views are from the same person? And what story does that metric tell us? It's hard to know the reason for the repeat view.

I could come back because the content helped me the last time I read it

If I'm the author, I may come back to perform an action (move, edit, feature it, etc.)

I could come back because there are new comments to read

Probably other scenarios of why I'm returning

Are any metrics captured if people are "viewing" the content from the overview page? So they see the update there and never actually visit the record itself (this question actually applies to view counts in general and not just repeat views)

We built an add-on (using QlikView) that sits on top of Jive's analytics database that allows you to get to extreme levels of granularity. It allows you to see any activity that Jive tracks in literally seconds (at a user, group, document, project, blog, etc. level....along with what happened on a particular data, time frame, etc.) It also shows you what a user did with each piece of content and we can easily get to unique views.

Happy to chat more if you are interested. We have a few Jive customers using our in-depth analysis now who can also speak to the details.

They are total views, not unique views. Another story to consider is the author coming back to the document to see how many views it got... and increasing the count each time.

I have not seen the new Impact metrics available in the Cloud version, and coming in Jive 7, but I am hopeful they will give us a much better understanding of the visibility any piece of content has gotten.

And don't forget that anyone who gets the content delivered via email can consume it that way, without any view being registered by Jive. And if it is short content that can be read in the activity stream without expanding it to preview it there, then it won't get counted as a view if consumed that way, either.