Viewing Counts on the Pages Not Matching With Analytics

Overview

Customers may notice that Page Views (PV) on single pages do not match with the Page Views displayed on the Analytics page. This is expected behavior since the two numbers have a different meaning.

This article summarizes the following topics:

• Why Are These Numbers Different?
• What Is a CMR View?
• How Are CMR Views Counted?
• What Are Some of the Functions That Page Views (Hosting Reports) Count That CMR Views Do Not Count?

Information

Why Are These Numbers Different?

• For one, the views on the blog are stored in the Application database, whereas CMR is located in the Data Warehouse (DW) section of the Analytics database.
• CMR does not track all Page Views, e.g., bot views are not tracked as CMR is designed to show you the health of your community. As a result, it only shows information about users.
• The raw views shown on the blog itself are reflective of guest users, API views, bots, etc. which are not filtered into the CMR equation.

 Back to top

What Is a CMR View?

• CMR stands for Community Manager Reports, and this is the interface available to community managers and other administrators in a customer's instance.
• CMR Views are counts of content views in CMR that provide the customer with an understanding of the health and usage of their community.

Back to top

How Are CMR Views Counted?

Unlike Page Views which try to capture all Jive application load activities, CMR Views focuses solely on a load of content:

• Documents

• Discussions

• Blog posts

• Status updates

• Polls

• Videos

• Ideas

• Group overview page

• Space overview pages

• Project overview pages

CMR Views are incremented based on the following content load events:

• A load of the content detail page (one PV)

• A view-more link in a stream that loads that content (one API call)

• An inbox view of that content (one API call)

• A call from Jive Anywhere to load the content (one API call)

• A call from Outlook connector to view the content in Jview (one API call)

• A call from the mobile web to load the content (one API call)

• A call from the native iOS app to load the content (one API call)

• A V3 API call that loads that content (one API call)

Back to top

What Are Some of the Functions That Page Views (Hosting Reports) Count That CMR Views Do Not Count?

• Page Views count all user-initiated page loads beyond just content views and content overview pages - basically, anytime the URL changes in the app:
  
  
  • All stream pages
  • Inbox: CMR does not count the main load of the inbox, but the views of the content via inbox do get counted - so CMR views increase as you use it.
  • Search pages
  • Browse pages
  • Second, third, etc. pages of comments
  • Preferences pages
  • Members pages of groups
  • CMR pages

   

• Page Views count all API loads beyond just those that load content:
  
  
  • Calls to load more stream events
  • Load your inbox count
  • 'More like this' sidebar calls
  • A load of impact metrics
  • Pop-over when you make a decision, save drafts, etc. 

   

• Page Views count bot loads, but CMR does not count bot loads.
  
  

 Back to top

Reference

You can check this document that details some of the CMR differences: Jive and Page Views.