Closed Bug 1886851 Opened 2 years ago Closed 2 years ago

Change Nimbus Exposure Event and Add Telemetry when an Expected or Offer Translation Event Occurs

Categories

(Firefox for Android :: Translations, defect, P2)

All
Android
defect

Tracking

()

RESOLVED FIXED
126 Branch
Tracking Status
firefox126 --- fixed
firefox127 --- verified

People

(Reporter: olivia, Assigned: olivia)

References

Details

(Whiteboard: [fxdroid][foundation])

Attachments

(3 files, 2 obsolete files)

The exposure event for translations should occur in these cases:

  • When translatable page is encountered
  • When menu is opened

Right now, it happens when the user sees the dialog. The Nimbus event needs to be moved back to when the expected offer event occurs.

Severity: -- → S3
Priority: -- → P2
Whiteboard: [fxdroid][foundation]

Should also probably add telemetry here too that corresponds to this Nimbus signal.

Assignee: nobody → ohall
Attachment #9393356 - Flags: data-review?(royang)
Summary: Change Nimbus Exposure Event → Change Nimbus Exposure Event and Add Telemetry when an Expected or Offer Translation Event Occurs

Comment on attachment 9393356 [details]
OfferToTranslateDataRequest.md

DATA COLLECTION REVIEW RESPONSE:

  1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, through the metrics.yaml file and the Glean Dictionary.

  1. Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

  1. If the request is for permanent data collection, is there someone who will monitor the data over time?

android-probes@mozilla.com will be responsible for monitoring the data over time

  1. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, Interaction data

  1. Is the data collection request for default-on or default-off?

Default on for all channels.

  1. Does the instrumentation include the addition of any new identifiers?

No

  1. Is the data collection covered by the existing Firefox privacy notice?

Yes

  1. Does the data collection use a third-party collection tool?

No

Result: data-review+

Attachment #9393356 - Flags: data-review?(royang) → data-review+

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

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
Attachment #9393606 - Attachment is obsolete: true
Attached file OfferToTranslateDataRequestRefactor.md (obsolete) —

In Bug 1886851, the organization of this event is slightly changed to be under the translations heading, instead of the event heading.
See Comment 7 for the right file.

Attachment #9394244 - Flags: data-review?(royang)
Attachment #9394244 - Attachment mime type: application/octet-stream → text/plain
Attachment #9394244 - Flags: data-review?(royang)
Attachment #9394244 - Attachment filename: OfferToTranslateDataRequestRefactor.md- → OfferToTranslateDataRequestRefactor.md
Attachment #9394244 - Attachment is obsolete: true

Includes information on refactor of earlier probe.

Attachment #9394247 - Flags: data-review?(royang)

Comment on attachment 9394247 [details]
OfferToTranslateDataRequestRefactor.md

DATA COLLECTION REVIEW RESPONSE:

  1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, through the metrics.yaml file and the Glean Dictionary.

  1. Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

  1. If the request is for permanent data collection, is there someone who will monitor the data over time?

android-probes@mozilla.com will be responsible for monitoring the data over time

  1. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, Interaction data

  1. Is the data collection request for default-on or default-off?

Default on for all channels.

  1. Does the instrumentation include the addition of any new identifiers?

No

  1. Is the data collection covered by the existing Firefox privacy notice?

Yes

  1. Does the data collection use a third-party collection tool?

No

Result: data-review+

Attachment #9394247 - Flags: data-review?(royang) → data-review+
Pushed by ohall@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d9858c319e84 Translations Nimbus Exposure Event and Offer Telemetry r=android-reviewers,Roger
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 126 Branch
Flags: qe-verify+

Verified on the latest Fenix Nightly 127.0a1 builds from 5/8, and 5/9, using a Realme GT Master Edition (Android 13), and a Google Pixel 6 (Android 14).

The events are being generated each time the translations bottom sheet is displayed.

"category": "translations"
"name": "offer_event"
"extra":
"item": "expected"
"category": "translations"
"name": "offer_event"
"extra":
"item": "offer"
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: