Jive and Page Views

Version 11

    Jive Software currently has two different models for metering site activity:


    • User Views
    • Page Views


    Be sure to review your Jive Pricing Schedule document to determine which model applies to your community.


    Both metering types are measured at the web server layer, but the models differ in what types of views you are billed for.  Here's the breakdown of differences:


    View TypeUser Views Model
    Page Views Model
    Bot viewsNOT METERED


    The User Views model focuses solely on human interactions, which is measured by user views when a person is engaging on your Jive community via a browser or mobile device.  API views and bot views are not counted with this model.


    Continue reading for more details and understanding of the different view types and how we make these measurements.


    How is Metering Activity Measured?


    We've established that customers are metered on site activity, but what does that mean?


    If you are a User Views metered customer, your billing is solely metered on User Views

    • User Views:
      • Any "page" load in Jive.  Page loads serve up “HTML/Text” by the Apache webserver.

    If you are a Page Views metered customer, your billing is metered on User Views + API Views + Bot Views

    • User Views:
      • Any "page" load in Jive.  Page loads serve up “HTML/Text” by the Apache webserver.
    • “API”-Initiated Views:
      • Any AJAX/JSON call within the Jive web application to the Jive server, such as an Inbox view of content or an Activity Stream load.
      • Any native API call from an application to Jive's APIs, including Jive applications like mobile apps, Jive Anywhere, Jive For Outlook, and so on.
    • Bot-Initiated Views:
      • Any page load due to a search engine crawler or other bot. Known malicious bots are excluded.


    How Is Metering Activity Counted?

    As Jive embraces the latest web standards for creating a rich end-user experience, the notion of a single web page as something that can be loaded and then counted has become less well-defined. Take for instance, the Activity Stream. As you scroll through the latest activity, you will find that you are never able to reach the bottom of the list - as the scroll bar approaches the bottom of your browser window, more and more results are loaded automatically creating an endless scrolling effect. As you click to interact with individual activity entries, the full content is loaded  inline. Without loading a single new "page", you can browse and interact with content continuously. These effects are made possible by a technology known as AJAX. To view new content, it is no longer necessary to navigate to a discrete stand-alone web page. The browser requests the content behind the scenes and displays it without refreshing the entire page. Jive measures all this activity at the web server layer, as described below.


    Jive counts page loads by searching through the different kinds of load events recorded in your Jive instance webserver logs, which capture every single load event in your Jive Community.  This is the most comprehensive way to assess the usage of a customer community.

    JCA is the system which Jive uses to manage all customer instances.  Every day, the JCA system will run a parser script that combs through the webserver logs of each instance. JCA stores aggregate counts (userviews, apiviews, botviews and other data) in a table called JCA Stats.  Depending on your instance type, this data may be visible to customers in the JCA customer portal, but if not, you will see this data in the Monthly Hosting Reports that are sent to your Jive Community group.


    It's important to note that even though the web server logs (weblogs) capture all activity, certain kinds of load events are filtered out by the parser script and thus are never counted as a page load:

    • Image loads
    • All loads from a list of known, malicious bots (*see list below)
    • All loads from blacklisted IP addresses
    • All loads from Jive monitoring systems, like Resonata


    Finally, API loads are only counted as 1/6 of a page load. It takes six API load events to increment a single API view count.


    Why Does Jive Count Metering Activity This Way?

    As described above, browsers are employing new ways of serving content to users, and the page load approach used by traditional web reporting tools is becoming less relevant. Today, a single "page" might consist of a number of CSS files, JavaScript files, images, html and content retrieved and rendered asynchronously (behind the scenes).  What's more, certain interactions that take place on a web page, such as liking, rating, commenting, and so on, can't be recorded by common web analytics tools. However, these operations still place a burden on the server while providing value to end users.  Thus, instrumenting the activity at the web server level provides a more accurate view of the actual load that the server is undergoing and correlates more closely with the value users are deriving from the usage of the tool.


    Community Manager Reports (CMR)


    What is a view in CMR?

    CMR stands for Community Manager Reports, and is the interface available to community managers and other administrators in a customer instance. CMR views are counts of content views in CMR that give customers an understanding of the health and usage of their community.

    It's important to understand the differences between JCA page loads and and not expect your CMR counts and reports to match 1:1 with your Monthly Hosted Report.


    To review: Views in CMR are NOT used to metering usage and should NOT be compared against page load counts for that purpose.  As you will see below, they have significant differences.

    How are CMR views counted?

    Unlike page loads, which try to capture all Jive application load activity, CMR Views focus solely on the 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 native iOS app to load the content (one API call)
    • A V3 API call that loads that content (one API call)


    What Does Metering Activity Count That CMR Does Not?

    • Metering Activity includes all user-initiated page loads beyond just content views and content overview pages. (Any event for which the URL changes in the app.) These include:
      • All stream pages
      • Main load of Inbox
      • Search pages
      • Browse pages
      • Second, third, etc pages of comments
      • Preferences pages
      • CMR pages
    • Metering Activity includes all API loads beyond just those that load content, including:
      • Calls to load more stream events
      • Calls to load your inbox count
      • "More like this" sidebar calls
      • Loads of impact metrics
      • Popovers generated when you make a decision, save drafts, and so on


    Google Analytics

    You may have access to Google Analytics. This might lead you to compare your Google Analytics count results against the page load counts in your Monthly Hosted Report, and even against CMR statistics.



    How Are Google Analytics Views Counted?

    First, it’s important to note that Jive's Google Analytics capability wasn’t designed to be a page view counter, but instead was developed to give you access to richer metadata around customer activity on your site.

    Second, the GA plugin in Jive was written 6 years ago and is very simplistic. While it allows you to access richer metadata, as a page view counter, it only counts the footers of certain pages.  As part of our larger efforts to improve our analytics, we’re working on updating our plugin. but Currently, though, this plugin does not provide a relevant measure of load that can be meaningfully compared to either JCA page loads or CMR counts.


    Why Does Google Analytics Report Lower Page View Counts Than Jive?

    As described above, Google Analytics and similar tools use a different method of counting pages than Jive's reporting. These tools typically work by embedding JavaScript within the code of each page to be counted. When a page tagged in this manner is loaded in a browser, the JavaScript fires off a request to the server of the analytics tool, indicating that the page has been "viewed."


    However, this approach can miss a lot of activity:

    • Because this reporting method requires JavaScript in order to function, any browser that doesn't have JavaScript enabled will fail to register a page view.
    • Search bots will fail to trigger page views, since they do not invoke JavaScript. (Instead, they mimic a user with JavaScript disabled.)
    • Any content that is requested asynchronously (via AJAX or the Jive Mobile Module, for example) will not register a view.
    • Finally, as mentioned above, the Jive GA implementation doesn't fire on every page footer.

    Given these caveats, you can expect your Google Analytics numbers to be lower (even significantly lower, depending on your Jive version - newer versions leverage AJAX/API calls more) than your JCA or Monthly Hosting Report numbers.



    Does Metering Activity Include Views Caused by Bots?

    Bots (also known as robots, web crawlers, search engine spiders, etc.) play an important role in the Internet ecosystem. They are responsible for crawling public sites and building indexes of content for use by internet search engines.


    From a server load perspective, bots put just as much load on a server as humans do. What a community owner gets in return for the cost of allowing bots to crawl a community is improved search rankings that can help advance the goals of the community (whether that be increased brand awareness/affinity, more efficient social support, etc.).


    If you are a Page View Metered customer and you do not wish to pay for bot traffic, you can file a case with Jive Hosting to provide a breakdown of the specific bots crawling your site, and the number of views they are causing. You can then elect to place a robots.txt file on your installation that will ask bots not to crawl the site. Be advised that not all bots heed this file, however. There may always be some amount of bot traffic on a public site. In extreme cases, it is possible to block a specific bot altogether by applying what's called an Apache rule. You can request this by filing a case with Jive Support. 


    Alternatively, moving to User Views metering will eliminate the need to monitor bot and API views. With User Views, you are not billed for any bot traffic.


    But bots appear to constitute 50% or more of my overall metered traffic!

    This is normal, and can vary from community to community based on the site layout and the content of the specific community. As mentioned above, it is possible to tune the percentage of traffic caused by bots by adjusting the robots.txt file. If this fails to achieve the desired effect, you can always block a specific bot at the Apache layer, as described above.


    For more information about Jive and site activity measurement, please contact your Jive Sales representative.