Open Bug 1824034 Opened 2 years ago Updated 1 year ago

explicitly count migrations started by about:welcome, rather than relying on newtab annotation

Categories

(Firefox :: Messaging System, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: dmosedale, Unassigned)

References

(Blocks 1 open bug)

Details

Najla and Ed were interested in telemetry that could answer the question "of the X% of users who had import checked in the about:welcome screen that started the migration, what percentage actually imported data".

A straightforward way to make this possible would be to allow it to be specified as a parameter to the SHOW_MIGRATION_WIZARD SpecialMessageAction.

This would involve adding an ABOUT_WELCOME entrypoint to MigrationUtils.MIGRATION_ENTRYPOINTS and then teaching the SHOW_MIGRATION_WIZARD SpecialMessageAction (and schema) about a data object with an entrypoint property, so that users of the action could pass in MigrationUtils.MIGRATION_ENTRYPOINTS.ABOUT_WELCOME, and finally updating about:welcome to do so

To completely support the use case described, we will need to verify that this telemetry can be analyzed together with the telemetry about data import completion.

See Also: → 1824010
Iteration: 113.1 - Mar 13 - Mar 24 → 113.2 - Mar 27 - Apr 7
Assignee: nobody → dmosedale

Note that the existing FX_MIGRATION_ENTRY_POINT histogram has reached its limit of 10 possible entrypoint values. Adding ABOUT_WELCOME will add another.

However, I have good news! In bug 1822692, I landed a new histogram, FX_MIGRATION_ENTRY_POINT_CATEGORICAL, which is a categorical histogram which defaults to having a maximum of 50 values.

We're using FX_MIGRATION_ENTRY_POINT and FX_MIGRATION_ENTRY_POINT_CATEGORICAL simultaneously right now to ensure a smooth transition from one metric to the other. We might want to alert data science to this, but I suggest adding your new entrypoint, and expecting those to enter the UNKNOWN bucket on the old histogram.

Ed pointed out that at the moment, the SHOW_MIGRATION_WIZARD SpecialMessageAction is only used by about:welcome, and that special message action is currently the only user of the NEWTAB entrypoint, which means that using the existing migration wizard and assuming that no one else (including experiments) starts to use those things, we can get that data for the general case right now.

This is fragile. I think this wants to be dealt with in the way Mike proposes so that we can actually use the data this way in an ongoing manner. I suspect we want to do this as part of the switch to the new migration wizard. Nadja, do you have an idea when you'd like to do this sort of analysis?

Flags: needinfo?(nbulous)
Summary: teach telemetry to notice migrations started by about:welcome → explicitly count migrations started by about:welcome, rather than relying on newtab annotation
Iteration: 113.2 - Mar 27 - Apr 7 → 114.1 - Apr 10 - Apr 21
Iteration: 114.1 - Apr 10 - Apr 21 → ---
Priority: -- → P3
Assignee: dmosedale → nobody

I think it would be valuable for about:welcome experiments in general, especially now that we're started to try to provide contextual flows based on whether a user is new or continuing. Is this something that we can pick up for Fx116?

Flags: needinfo?(nbulous)

Removing priority to consider for 116 in the next triage meeting.

Priority: P3 → --
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.