-
Notifications
You must be signed in to change notification settings - Fork 49
Add telemetry for outbound translation #43
Comments
Closed in favor of #54 |
Actually is better to decouple this and implement after #54 has landed |
We need to know from @kpu and the UI team what are the metrics to be captured here. |
Desirable telemetry would be : Elapsed time plugin was used |
@ChrisBurnsOneOne thank you for providing the metrics! Just to make sure we're on the same page, could you please formulate questions that you want to answer using these metrics? |
The plugin has a limited amount of functionality which the user can truly interact with and it serves no purpose to them (or us) to deactivate or otherwise downgrade those functions. To truly run an experiment we need to compare user experiences in a highly controlled and systematic way. Since we can't really do this because such functionality was never designed to exist in the plugin from the outset, even with tailored, multiple versions of the plugin for comparison with each other, really, all we're left with is surveying user engagement. So :
For the remaining two : -We may gain some insights into "more popular" translations based on inferences about the language the user is familiar with. It's e.g. very unlikely someone would be using an OS system language pack other than their native language. |
when it's stable
The text was updated successfully, but these errors were encountered: