Closed Bug 909317 Opened 11 years ago Closed 1 year ago

[story] As a Mozilla Product Manager, I want to track how many users are using sync across which devices, and how many devices each user is syncing to their account so that I can continuously track and improve Sync's engagement and utility.

Categories

(Tracking Graveyard :: Firefox Sync, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: deb, Unassigned)

References

Details

(Whiteboard: [qa+])

As a Mozilla Product Manager, I would like to know how many users are using sync across which devices, and how many devices each user is syncing to their account.
Blocks: 909322
Whiteboard: [qa+]
Summary: [story] Feature usage metrics → [story] As a Mozilla Product Manager, I would like to know how many users are using sync across which devices, and how many devices each user is syncing to their account.
Added the benefit, "so I can continuously track and improve Sync's engagement and utility."
Summary: [story] As a Mozilla Product Manager, I would like to know how many users are using sync across which devices, and how many devices each user is syncing to their account. → [story] As a Mozilla Product Manager, I would like to know how many users are using sync across which devices, and how many devices each user is syncing to their account so that I can continuously track and improve Sync's engagement and utility.
Summary: [story] As a Mozilla Product Manager, I would like to know how many users are using sync across which devices, and how many devices each user is syncing to their account so that I can continuously track and improve Sync's engagement and utility. → [story] As a Mozilla Product Manager, I want to track how many users are using sync across which devices, and how many devices each user is syncing to their account so that I can continuously track and improve Sync's engagement and utility.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
Product: Tracking → Tracking Graveyard
You need to log in before you can comment on or make changes to this bug.