Skip to content
This repository has been archived by the owner on Sep 4, 2023. It is now read-only.

Add telemetry for outbound translation #43

Closed
eu9ene opened this issue Jan 21, 2022 · 6 comments · Fixed by #112
Closed

Add telemetry for outbound translation #43

eu9ene opened this issue Jan 21, 2022 · 6 comments · Fixed by #112
Assignees
Labels
outbound-translation Issues and Requests for outbound translation
Milestone

Comments

@eu9ene
Copy link
Collaborator

eu9ene commented Jan 21, 2022

when it's stable

@eu9ene eu9ene mentioned this issue Jan 21, 2022
@andrenatal andrenatal added the outbound-translation Issues and Requests for outbound translation label Jan 26, 2022
@andrenatal
Copy link
Contributor

Closed in favor of #54

@andrenatal
Copy link
Contributor

Actually is better to decouple this and implement after #54 has landed

@andrenatal andrenatal reopened this Jan 27, 2022
@andrenatal andrenatal added this to the W2 milestone Feb 10, 2022
@andrenatal
Copy link
Contributor

We need to know from @kpu and the UI team what are the metrics to be captured here.

@ChrisBurnsOneOne
Copy link

Desirable telemetry would be :

Elapsed time plugin was used
Character count of source text
No. of edits to all text boxes (i.e. no of "clicked in and out" of the text boxes)
System or OS language in use
Geographical location of the user
mouse clicks per plugin session
Which plugin functions were activated or deactivated by the user during the session

@eu9ene
Copy link
Collaborator Author

eu9ene commented Feb 17, 2022

@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?

@ChrisBurnsOneOne
Copy link

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 :
Elapsed time plugin was used
Character count of source text
No. of edits to all text boxes (i.e. no of "clicked in and out" of the text boxes)
mouse clicks per plugin session
Which plugin functions were activated or deactivated by the user during the session (I would add here, "if at all")

  • are all intended as basic measures of user engagement / use of the plugin. It would also be good to get the actual translated text, but that would undoubtedly obviously be much too intrusive.

For the remaining two :
System or OS language in use
Geographical location of the user

-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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outbound-translation Issues and Requests for outbound translation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants