Closed
Bug 1273216
Opened 8 years ago
Closed 6 years ago
How well are sync users retained?
Categories
(Cloud Services Graveyard :: Server: Sync, defect, P3)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dcoates, Assigned: adavis)
References
Details
(Whiteboard: [sync-metrics])
Before we can ask how we can improve retention we need to know what our current retention is. I made a prototype cohort chart [1] that shows new user retention over a 10 day period (with a bug on the last day). Does that type of artifact capture what we want to know? What time frames make sense to keep track of? I think daily retention for the first week, then weekly for the first few months sounds like a good place to start. [1] https://sql.telemetry.mozilla.org/queries/246#399
Updated•8 years ago
|
Priority: -- → P1
Reporter | ||
Updated•8 years ago
|
Component: Sync → Server: Sync
Product: Firefox → Cloud Services
Reporter | ||
Updated•8 years ago
|
Whiteboard: [sync-metrics]
Updated•8 years ago
|
Priority: P1 → P2
Updated•8 years ago
|
Priority: P2 → P3
Reporter | ||
Updated•8 years ago
|
Assignee: dcoates → nobody
Updated•8 years ago
|
Assignee: nobody → adavis
Flags: needinfo?(adavis)
Assignee | ||
Comment 1•8 years ago
|
||
We can probably piggy back on FxA for this retention data: https://sql.telemetry.mozilla.org/dashboard/fxa-retention We are working on improving our definition of multi-device users and are also working with new data so that chart will be replaced soon. Rfk is trying out the new data here: https://sql.telemetry.mozilla.org/queries/1309#2276 https://sql.telemetry.mozilla.org/queries/1310#2278
Flags: needinfo?(adavis)
Comment 2•6 years ago
|
||
We have a pretty good handle on our retention metrics now, closing this out.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•