1 person found this helpful
At a high-level, IMO ... you would just run a standard activity report with a place filter, see Using the V2 Jive Data Export Service (Analytics), and add in the restrictions on the specific content-types and object actions you want to include (including ACTIVITY_VIEW_COMMUNITY, which I believe you are correct is the View Overview Page). Once you've done that, you simply curate a list of all the Actor ID's name...etc. De-dup and you are solid.
I've added this to a new document we are starting here: Data Export Service (DES) - Common Queries (WIP) ... hoping to be able to share some exact queries soon.
Hope that helps for now.
Apologies for coming back to this so long after you posted your helpful comment. It's been some time since I was trying to solve this problem, but I believe the issue is that ACTIVITY_VIEW_COMMUNITY is an event that is registered not in the place itself, but in the place that contains it.
E.g., if I have a space "Space" and a subspace "subspace," where there are blog posts, discussions, etc., then those blog view events etc. will be registered in "subspace." And I'll see them if I do a place filter using "subspace." But views of subspace's overview page will actually be ACTIVITY_VIEW_COMMUNITY events in "space." Viewing the overview page of "subspace" doesn't seem to register an event in "subspace."