Unified Telemetry/Status reports/TopLineKPI's/Pocket
From MozillaWiki
Contents
Top Line KPI status report for Pocket January 16, 2015
Overall Project Health
Last week: Green
This week: Green
Exec Summary
- Met with Pocket contact to understand process of data drops. Next steps are to define active users, work with ops on data handover and then move to visualization tasks.
Project summary
- Project in Green as no known blockers exist
Project Deliverables
- Define active user
- Create justification doc explaining the above
- Dashboard Populated with production data
| Step | State | Owner | Timeline for resolution |
|---|---|---|---|
| Define active user | In progress | Rebecca/Team | day/month |
| Create justification Doc | Open | Rebecca | day/month |
| Populate dashboard with data | Open | Rebecca | day/month |
Accomplished for Last Period
- Met with Kenny from pocket.
What we get today:
- fx_referral = users that signed up for Pocket with an email address after having been referred from Firefox integration, and have not later connected an FxA verified account
- fxa_verified = users that logged into Pocket with an FxA account (regardless of whether the account already existed as a normal email account)
- total = fx_referral + fxa_verified
What we need:
- Daily Users
- Sum of the previous 30 days (for feb 1 - count of unique users on feb 1 + last 29 days)
- Frequency of data drop:
Planned for Next Period
- understand Ops needs for .csv file and iteration
- understand definition of use
Risks and items to retire
- Understand definition of use
- follow up with Bryan Clarke: do we want the most tolerant definition of use
- examples -
- desktop ff launches web pocket). If at some point there was a FF, does the count as active?
- someone uses an extension, then later uses a web app - does that count?
- where does pocket place the .csv, and do the increment an old one or create a new one? Follow up with ops.
