RFC: New "install" and "update" pings
Alessio Placitelli
aplacitelli at mozilla.com
Wed Mar 8 14:26:31 UTC 2017
*tl;dr;* we're kicking off the work on two new ping types, the proposal is
down below and we're gladly accepting comments.
*Context*
Data Platform will be supporting Firefox Growth by working on reducing the
data reporting latency, allowing client teams to make decision and iterate
quickly.
Along with the initiative of sending the "shutdown" ping when Firefox shuts
down (bug 1336360), we're considering adding the following new pings:
*"Install" (aka "Activation") ping*
Sent when Firefox is launched right after its installation, on a new
profile. This ping will contain:
- The client_id
- The environment data (or a subset of the environment data).
Having this clear installation signal would be useful for funnel and churn
analysis, along with giving us a clearer picture of the "download to usage"
patterns. The work for this ping is tracked in bug 1120370.
In the current state, the "Install" ping would be sent right after the
"Data Choices" infobar is displayed, which is 60s into Firefox execution.
This *could *change in future releases as we will probably be dropping the
infobar and opening a tab instead.
*"Update" ping*Sent right after Firefox upgrades to a new version (i.e.
restarts after applying the update). It will contain:
- The client_id
- The previous installed version and channel
- The current installed version and channel
This will give us a clear signal of a version upgrade, helping to have a
quicker view on the version uptake of new Firefox releases. The work for
this ping is tracked in bug 1120372.
There's a discussion going on about sending this ping *before *the update
takes place and *after *it finishes, to quantify the problems in the update
process.
Alternatively, if we were able to detect failed updates when restarting
Firefox (under investigation), we could just be sending the "update" ping
once after an update attempt, regardless of its success, together with the
failure reason.
*Additional context*
https://docs.google.com/document/d/1NEOHfT4hBsmOmoK5M_wbsF7v-NihTtCybHe-sxs9Hgw/edit?ts=58b947d8#heading=h.byypvh46s2wo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/fhr-dev/attachments/20170308/64b1855e/attachment.html>
More information about the fhr-dev
mailing list