Analytics/Archive/Editor Engagement Vital Signs

= Goals =

The Editor Engagement program is a top strategic priority for the foundation and has many individual initiatives. However we do not have a dashboard that provides consistent, explorable, timely data on this program which makes it difficult and time-consuming for implementors to understand the impact of their changes. A consistent dashboard would also help normalize results across products and other aspects of the program which are difficult to compare at this time.

The goal of this project is implementing such a dashboard.

= Users =

= Prioritized Use Cases =

Non functional requirements

 * 1) All dashboards should be updated daily.
 * 2) Once we have signoff on the basic issues described below, all issues with dashboards should be addressed within 2 "business" days of the problem reports.
 * 3) Data be retained indefinitely

= Metrics =

A note on mobile v. desktop. We don't want a straight breakdown of every metric on mobile v. desktop because sometimes the metric won't make sense. For example, active editors isn't something that we want to differentiate mobile v. desktop at this time.

Granularity

 * Daily
 * Monthly

New Users

 * Registrations
 * Mobile
 * Desktop

Activation

 * Live accounts (?)
 * First time editors
 * 5+ Edits
 * Sessions
 * Number
 * Average Length

Community

 * Active Users
 * 1+ Edits
 * 5+ Edits
 * 100+ Edits
 * Bots
 * 1+ Edits
 * 5+ Edits
 * 100+ Edits

Contributions

 * Edits
 * Mobile
 * Desktop
 * Uploads
 * Mobile
 * Desktop

Curation

 * Reverts
 * Deletions

Content

 * New Pages
 * Totals Pages

= 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