Closed
Bug 1257511
Opened 9 years ago
Closed 9 years ago
Capture Engagement Ratio definition / documentation
Categories
(Cloud Services :: Metrics: Product Metrics, defect, P1)
Cloud Services
Metrics: Product Metrics
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mreid, Assigned: rweiss)
Details
The details from Bug 1240849 should be documented with the official KPI definitions
Updated•9 years ago
|
Component: Metrics: Pipeline → Metrics: Product Metrics
Assignee | ||
Comment 1•9 years ago
|
||
I'm owning documentation. I'll follow up with :dzeber.
Assignee: nobody → rweiss
Assignee | ||
Updated•9 years ago
|
Priority: -- → P1
Assignee | ||
Comment 2•9 years ago
|
||
Data glossary available here: https://docs.google.com/document/d/1Fdq2uq5W2M4iesROcq3v5yYYFdLDzYOxjR-SxK3CYZ4/edit?ts=56fc57cb
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 3•9 years ago
|
||
I've made a couple of updates to the doc.
I rephrased the definitions of active from "on date d" to "during a time period", as I think this makes the intention more clear. In particular, Type 1 Active is supposed to refer to the most recent observed activity during the entire time period, not on specific dates. However, this doesn't change the meaning or computation of the DAU/MAU metrics.
I also added a short discussion on the difference between Type 1 and Type 2 active, which summarizes bug 1240849, comment 18. This is mainly intended for future reference when we/others wonder why we have two definitions of "active". The central point here is that this only matters for segments that can change, like version, and the decision of which to use should be made on a product-by-product basis.
You need to log in
before you can comment on or make changes to this bug.
Description
•