Analytics/Pageviews/Stories

User goes to Vital Signs for Pageviews per project
As an executive, product manager, researcher, community member...

I can quickly view daily Pageviews per project in Vital Signs;

so I can monitor the projects.


 * Details
 * daily sums
 * per project (wiki)
 * includes all namespaces
 * crawler traffic is excluded (per the webstatscollector definition)
 * with a breakdown distinguishing hits to the desktop or mobile sites
 * this data is public

User analyzes Pageview generators
As a product manager, researcher, analyst...

I can slice and dice who is generating Pageviews and visualize it;

so I can inform my project decisions.


 * Details
 * available in a cube / DW, visualized using a BI tool.
 * daily or monthly sums (perhaps the BI tool can aggregate by month)
 * data can be sliced by
 * Crawler (Yes/No)
 * Project, Country,
 * Target Site {desktop, mobile, API, Zero},
 * Device (Android, iPhone, ... other) (this list should be limited and cheap to implement)
 * User-Agent (sanitized and limited list)
 * this data is private initially and could be made public later if there are no privacy issues
 * includes pages across all namespaces

User analyzes Pageview hotspots
As a trouble shooter, community member, admin...

I can rank Pageviews per page;

so I can see what readers are paying attention to.


 * Details
 * available in a cube / DW, visualized using a BI tool.
 * for all pages in all namespaces
 * daily counts (
 * Pageview counts for each page
 * Dimensions:
 * Crawler, Country, Target Site, User Agent, Device