# Page view reports vs topic view reports

**URL:** https://meta.discourse.org/t/page-view-reports-vs-topic-view-reports/218246
**Category:** Data & reporting
**Created:** [February 15, 2022, 2:22pm UTC](https://meta.discourse.org/t/page-view-reports-vs-topic-view-reports/218246 "2022-02-15T14:22:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ganncamp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ganncamp/32/106199_2.png) [@ganncamp](https://meta.discourse.org/u/ganncamp)
#### Post date: [February 15, 2022, 2:22pm UTC](https://meta.discourse.org/t/page-view-reports-vs-topic-view-reports/218246/1 "2022-02-15T14:22:44Z")

</div>

Hi,

We’re starting to look at the built-in reporting, and find the page view reporting on the admin dashboard interesting. However, I guess that’s _all_ pageviews? So including search results, the `/category` page, `/new`, `/latest` &etc?

We see a real distinction to be made in navigation pageviews, versus consumption-of-content pageviews, i.e. thread views.

From an instance admin standpoint I see the usefulness of the current Consolidated Pageviews graph.

And as a community manager, I have a desire for a second stacked bar graph: Consolidated Threadviews, showing Logged in users and Anonymous users (but not Crawlers).

Or is the share of navigation pageviews typically so small that it generally doesn’t matter?