Open Bug 1621520 Opened 9 months ago Updated 3 months ago

Use event telemetry for LoginManagerChild._fillForm

Categories

(Toolkit :: Password Manager, task, P2)

task

Tracking

()

Tracking Status
firefox76 --- affected

People

(Reporter: MattN, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [passwords:telemetry])

User Story

Some questions we can't currently answer:
* What proportion of users are seeing a login form autofilled on page load (without user interaction) in a given day/week/month?
* What proportion of users used the login context vs. autocomplete menu items to fill a form by day/week/month?
* What proportion of fills with recipes succeed vs. fills without recipes?
* What proportion of forms were filled? (Currently _fillForm can be called multiple times e.g. on the faceook.com registration form)

Right now we have a pwmgr_form_autofill_result histogram but since there are so many arguments to this function and ways that it can be invoked, it makes it hard to extract meaning from the data e.g. separating autofill on page load vs. autofill from autocomplete vs. autofill from the context menu (this probe is only recorded for autofill without user interaction currently but that means we don't know anything about fills via the context menu or autocomplete which this bug should fix). Even more importantly is that currently we can only record one reason for not autofilling but ideally we would want to know all of the reason since fixing that one may not be enough to get that form to then autofill. With event telemetry we can record more of this info in "extra" arguments on the event.

My main concern would be that the volume of events would be too high but we can check that.

No longer blocks: 1619851
User Story: (updated)
Flags: needinfo?(MattN+bmo)
Flags: needinfo?(mozilla+bmo)
You need to log in before you can comment on or make changes to this bug.