Su has put together a telemetry requirements doc for password import autocomplete suggestion: https://docs.google.com/document/d/1_q3RgyBY-2xJgdkyI3HAnooDtAMl-aM-Oq1vyFSFXJ8 With the new designs and triggering conditions from bug 1618311 comment 4 notably only showing the import suggestion when the user doesn't have a saved login for the site and within 7 days profile age… I think a implementation for control and experiment branch is for when autocomplete is deciding what to show (e.g., user has focused a login field), we can report event telemetry with 2 numbers: - how many saved logins firefox would show - how many import suggestions could be shown (i.e., number of other browsers with saved login) Where control branch never actually shows the import suggestion and import branch decides to show if no saved logins and profile age <1week. Su, are those 2 values sufficient for analysis (in addition to import suggestion and import wizard interaction)? Is there a good way to send a pair of values for an event -- json/js array, e.g., [0,1] for 0 saved logins for this site and 1 browser has saved login and after import or user saved login: [1,1]? I would think two separate event telemetry with saved=0 importable=1 might be harder to associate with each other ??
Bug 1628849 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Su has put together a telemetry requirements doc for password import autocomplete suggestion: https://docs.google.com/document/d/1_q3RgyBY-2xJgdkyI3HAnooDtAMl-aM-Oq1vyFSFXJ8 With the new designs and triggering conditions from bug 1618311 comment 4 notably only showing the import suggestion when the user doesn't have a saved login for the site and within 7 days profile age… I think a implementation for control and experiment branch is for when autocomplete is deciding what to show (e.g., user has focused a login field), we can report event telemetry with 2 numbers: - how many saved logins firefox would show - how many import suggestions could be shown (i.e., number of other browsers with saved login) Where control branch never actually shows the import suggestion and import branch decides to show if no saved logins and profile age <1week. Su, are those 2 values sufficient for analysis (in addition to import suggestion and import wizard interaction)? Is there a good way to send a pair of values for an event -- json/js array, e.g., [0,1] for 0 saved logins for this site and 1 browser has saved login; and after import or user saved login: [1,1]? I would think two separate event telemetry with saved=0 importable=1 might be harder to associate with each other ??