Closed
Bug 1204608
Opened 9 years ago
Closed 8 years ago
Need Push and Notifications metrics probes to support KPI
Categories
(Core :: DOM: Notifications, defect)
Core
DOM: Notifications
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox43 | --- | affected |
People
(Reporter: edwong, Unassigned)
References
()
Details
Meta bug of sorts. We need to make sure any client code gets landed in understand success of Push and Notifications project.
Reporter | ||
Comment 1•9 years ago
|
||
NI: product - we need to figure out what questions we want to ask from Push Notification ASAP - if we need to land code for Fx42 or Fx43.
Flags: needinfo?(wmaggs)
Flags: needinfo?(rweiss)
Reporter | ||
Updated•9 years ago
|
Updated•9 years ago
|
Comment 3•9 years ago
|
||
Key KPIs for 44:
% of users who see a permissions prompt that grant permission (good to know in general, but useless unless we have at least some per site.
% of notifications that are seen by a user that are interacted with
Flags: needinfo?(wmaggs)
Reporter | ||
Comment 4•9 years ago
|
||
Ian sent email on this a while ago:
- Number of Push API subscription requests that fail in the client (server offline, client offline, something else happens)
- Denominator: number of Push API subscription requests total
- Number of Push messages that fail with an error (an exception or timeout in the service worker, or the service worker being killed before completion)
- Denominator: number of Push messages
- Stats around the permission dialogs (click throughs, rejections, maybe neither accepting nor denying but navigating away). Maybe this already exists.
- How often people tweak the permissions later, and to what end
- Stats around popup notifications.
- Number of popups
- How often people click any of the different parts of the popup (what parts there are depends on the result of UX)
- There might be something about how the popup onclick is implemented. Does it fail back to the default action? Does it open a new page? Focus an existing page? Apparently do nothing? This one might be a little harder, as it's action at a distance.
Reporter | ||
Comment 5•9 years ago
|
||
I think the KPI of the feature is:
primary:
* percent users who disable the feature completely over time - this value is the ultimate signal that I don't like this feature.
secondary:
* percent of sites blocked vs total sites that prompted permission dialog over time - if the percent is high, their general perception and experience of the feature is negative.
we could also A/B test different display duration times against the secondary KPI.
Comment hidden (obsolete) |
Comment 7•9 years ago
|
||
I think we will get a lot of these metrics from bug 1207089 and then we can add push-specific ones on top.
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment 10•9 years ago
|
||
We should add Do Not Disturb probes too
Comment 11•9 years ago
|
||
Kit and I discussed the probes and clarified some in https://public.etherpad-mozilla.org/p/notification-telemetry
Updated•9 years ago
|
Comment 12•8 years ago
|
||
I think we can close this out and file follow-up bugs for any additional probes that we may need.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•