Analytics/Epics/Metric Definition Standardization

= Goals =

We need to standardize the metrics used across the organization for a variety of purposes. Ultimately we should expose these metrics through a schema but right now, we'll focus on basic metrics.

It is expected that this is a joint project between Research and Data and Development.

= Detailed Tracking Links =

Development (Mingle)

Research (Trello)

= Metrics Attributes =

Metrics should be:


 * understandable by lay person
 * easy to reproduce from data in the MediaWiki database
 * robust to changes in MediaWiki configuration (a metric doesn’t change if an admin toggles a project config to use a different option for countable pages)
 * consistent across projects (metric foo measures the same thing in Swahili end English Wikipedia)
 * stateless (historical data remains the same, regardless of when we compute it)
 * different from those based on legacy definition by a margin we’re comfortable with (when applicable)
 * computable at different time resolutions (daily, weekly, monthly)
 * documented -- consistent human and machine readable definitions.
 * accessible -- there should be an API for the foundation/community to access them.
 * verified -- processes for assuring data is correct

= Reader Metrics =

Reach

 * Daily Active Users/Daily Unique Users
 * Web
 * Mobile
 * Both Web/Mobile (de-duped)


 * Monthly Active Users/Monthly Uniques
 * Web
 * Mobile
 * Both Web/Mobile (de-duped)
 * Bots
 * API

Engagement

 * Page Views
 * Web
 * Mobile
 * Wikipedia Zero (is this different from Mobile?)


 * Sessions
 * Number of Sessions
 * Session Length
 * Mobile
 * Desktop


 * Time Spent (# Sessions * Session Length)

Retention

 * 1,3,7,14,30,60,90,360 days day retention
 * Mobile
 * Web

Source

 * Referrers

= Fundraising =
 * Number of Donations
 * Mobile
 * Web


 * Average Donation
 * Mobile
 * Web


 * Average Donation
 * Average Donation/User
 * Total Donations

= Editor Metrics =

An extensive treatment of these metrics is in this Epic.

= Users =

= Prioritized Use Cases =


 * 1) As a Developer, I want to know how to turn the definitions into software in a scalable manner
 * 2) As a Developer on Wikipedia Zero, I want to have a definition of a page view I can use to measure program engagement
 * 3) As a Developer on Wikipedia Web, I want to have a definition of a page view I can use to measure program engagement
 * 4) As a Developer on Wikipedia Mobile, I want to have a definition of a page view I can use to measure program engagement
 * 5) As a Manager and as the Community I want a page where these definitions are available in an easy to understand format.

= Non Prioritized Use Cases =


 * 1) As a Manager, Developers and the Community I want to know how many page views Wikipedia receives per article on on an hourly granularity.

= Implementation Details =

We'll need to work very closely with Erik Zachte on this as he currently has the documentation on what we are doing now.

Documentation for pages views is here but it is probably out of date.