1805256 - Add legacy telemetry id to Glean internal pings for Focus Android

Status: VERIFIED FIXED

(Data Platform and Tools :: Glean: SDK, task, P1)

Description

[Travis Long [:travis_]]

As part of investigating why legacy counts more core-active users than Glean does on Focus Android, we will add to the Glean internal pings the Legacy telemetry id for the purpose of connecting old and new telemetry for the same user.

Comment 1

[Travis Long [:travis_]]

Need to file a data-review since the current legacy-id going into the deletion-request ping is exempted.

Comment 2

[Travis Long [:travis_]]

Attachment: data-review request

Comment 3

[BMO Automation]

Attachment: [mozilla-mobile/focus-android] Bug 1805256 - Adds the legacy-id to Glean internal and other pings (#8138)

Comment 4

[Travis Long [:travis_]]

Attachment: GitHub Pull Request

Comment 5

[BMO Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1805256 - Adding legacy telemetry id to Glean pings (#303)

Comment 6

[Travis Long [:travis_]]

Comment on attachment 9307855 [details]
data-review request

editing the attachment as a comment didn't work out like I expected, I'll obsolete the old one and attach a new one instead.

Comment 7

[Travis Long [:travis_]]

Attachment: data-review request

This obsoletes the previous data-review. This has been updated to reflect the guidance on the data-collection category from the escalation of the data-review.

Comment 8

[Elise Richards]

Comment on attachment 9308319 [details]
data-review request

Data Review Form

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 Glean Dictionary and in the metrics.yaml file.

2. Is there a control mechanism that allows the user to turn the data collection on and off? (Note, for data collection not needed for security purposes, Mozilla provides such a control mechanism) Provide details as to the control mechanism available.

   • Yes, through the normal telemetry opt-out in the application settings.

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

   • Yes, this a permanent collection and it will be monitored by Travis Long ([e-mail]).

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

   • Category 1 - technical data.

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

   • Default-on.

6. Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?

   • No

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

   • Yes

8. Does the data collection use a third-party collection tool? If yes, escalate to legal.

   • No

Result

data-review+

Comment 9

[BMO Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1805256 - Adding legacy telemetry id to Glean pings (backport #303) (#371)

Comment 10

[Travis Long [:travis_]]

This has landed and will be uplifted into a v108 dot release.

Comment 11

[Mira Lobontiu (Android QA)]

Verified that in the Focus RC 108.1.1 build, and Focus Nightly 110.0a1 from 12/21 the client_id is displayed in baseline, events, activation, and metrics.

Comment 12

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6a17c605163f
Adding legacy telemetry id to Glean pings