Closed Bug 1251317 Opened 7 years ago Closed 7 years ago
Probe to measure usage and activity of content notifications
- How many times notifications are triggered on signal - How many "subscriptions" devices we have (if possible) - How many users turned off the notification to decide that the feature is annoying people, not needed - How many times the browser was actually opened right after (within 1 day) receiving the trigger to see if this drives engagement -- not sure if we can measure that
Depends on: content-notifications
(In reply to Barbara Bermes [:barbara] from comment #0) > - How many times notifications are triggered on signal Should match what we do for Tab Queues, which has the same semantics. > - How many "subscriptions" devices we have (if possible) As stated (assuming we could define 'devices') this sounds like a histogram. We could restate this as: Add a probe for adding and removing a subscription. Then we can look at event data and track number of new subscriptions per week. > - How many users turned off the notification to decide that the feature is > annoying people, not needed Simple event probe on the "notifications settings" button of the Notification. Then we already track people flipping settings. So it's a funnel-problem: show-notification -> tap notification-settings -> flip pref to disable > - How many times the browser was actually opened right after (within 1 day) > receiving the trigger to see if this drives engagement -- not sure if we can > measure that We would track people tapping the notification to display the updated content in the browser. I assume that works a lot like Tab Queues and we should mimic the loadurls we do for that.
Assignee: nobody → s.kaspari
Status: NEW → ASSIGNED
Patch landed as part of bug 1241810. https://hg.mozilla.org/integration/fx-team/rev/84180ddf65a7
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.