This bug adds additional telemetry including:
* When a translation is requested, including to/from languages
* When a translation is successful
* When a translation fails
* Whether or not the translations engine is supported
Differential Revision: https://phabricator.services.mozilla.com/D206048
This patch:
* Moves the Nimbus exposure event to occur when an entry point could be shown
* Before it was sending the event when the dialog was opened
* Adds Translations.offer_event Telemetry
* Refactors Event.translation_action to Translations.action, because we will
be adding more telemetry under the Translations umbrella
Differential Revision: https://phabricator.services.mozilla.com/D205909
This patch adds:
* `translations_action` probe
* Extras:
* main_flow_toolbar - Interaction with toolbar button
* main_flow_browser - Interaction with browser menu button
* page_settings - Interaction with page settings
* global_settings - Interaction with global settings
* global_lang_settings - Interaction with language settings
* global_site_settings - Interaction with site settings
* downloads - Interaction with downloads
This commit:
* Sends the new `awesomebar.{engagement, abandonment}` events when the
user finishes interacting with the awesomebar. These events match
iOS's events of the same name, and Desktop's
`urlbar.{engagement, abandonment}` events.
* Removes the `engagement_abandoned` extra key for the
`awesomebar.{sponsored, non_sponsored}_suggestion_impressed` events,
since they're specific to AMP and Wikipedia suggestions, and are
subsumed by the new events.
This is the first step toward unifying our awesomebar search telemetry
on all our platforms.
Fenix currently reports AMP and Wikipedia impressions and clicks in the
`fx-suggest` ping, which intentionally omits the `client_id`. This
complicates experiment analysis, because our tooling relies on the
`client_id`.
This commit adds separate events for impressions and clicks on
sponsored and non-sponsored suggestions to the `events` ping.
* The new `awesomebar.{non_}sponsored_suggestion_clicked` events are
collected the same way as the existing `fx-suggest` ping, and in line
with the other `awesomebar.*_suggestion_clicked` events.
* The new `awesomebar.{non_}sponsored_suggestion_impressed` events are
collected for engaged and abandoned search sessions. In constrast,
the `fx-suggest` ping is only sent for engaged search sessions.
We weren't getting submissions for the font telemetry list
and eventually I traced it down to the metric having been expired.
We also need to bump the submission number, otherwise the work
request will be skipped.
Added `surface_powered_by_fakespot_link_clicked` telemetry probe
that is sent when the user taps the "Powered by Fakespot by Mozilla"
footer link in Review Checker Sheet.
This commit:
* Adds new facts, `wikipedia_suggestion_clicked` and
`wikipedia_suggestion_impressed`, to the `feature-fxsuggest`
component.
* Emits `fx-suggest` Glean pings for those facts in Fenix's
`MetricController`.
This commit adds the following measurements:
* A new value for the `fx_suggest.ping_type` metric,
`fxsuggest-impression`.
* An `fx_suggest.position` metric to capture the position of the
Firefox Suggest search suggestion in the awesomebar, for impressions
and clicks.
* An `fx_suggest.is_clicked` metric, to capture whether an
`fxsuggest-impression` ping is for a clicked suggestion.
This commit also:
* Mounts `FxSuggestFactsMiddleware` to collect facts for impressions
and clicks.
* Dispatches `AwesomeBarAction`s from the `SearchDialogController` in
response to user interactions with the awesomebar and toolbar.