From what I can tell, the JiveViewCount table stores the total views that shows on the thread (for example, this thread is showing 38 views right now). I would imagine this includes views for anytime the thread gets hit. Here is a SQL query I use to pull back a "thread inventory" for our moderator team so they can see at a glance what threads exist in their areas.
select jivemessage.threadid, jivemessage.userid, jivecommunity.name as "Space",jivemessage.subject, to_timestamp(jivemessage.creationdate/1000) as "creationdate",jivethreadlatest.messagecount, jiveviewcount.viewcount
left join jivethreadlatest on jivethreadlatest.threadid = jivemessage.threadid
left join jiveviewcount on jiveviewcount.objectid = jivemessage.threadid
left join jivecommunity on jivecommunity.communityid = jivemessage.containerid
where jivemessage.parentmessageid is null and jiveviewcount.objecttype = '1' and jivemessage.containertype = '14'
order by jiveviewcount.viewcount desc
I haven't seen anything in the tables so far that would lead me to believe that you can isolate just the root message (which is the message identified as the thread)
Google Analytics or the like would be the best bet.