1653073 - [meta] Add telemetry needed for A/B testing of Credit Card Form Autofill

Status: RESOLVED FIXED

(Toolkit :: Form Autofill, enhancement, P1)

Description

[Zibi Braniecki [:zbraniecki][:gandalf]]

This is cumulative bug for telemetry needed for A/B testing of Credit Card Autofill feature.

Comment 1

[Zibi Braniecki [:zbraniecki][:gandalf]]

Attachment: CC Autofill Data Review.txt

requesting data review from Nicole as per Matrix #data-stewards discussion

Comment 2

[Zibi Braniecki [:zbraniecki][:gandalf]]

Attachment: CC Autofill Data Review.txt

Updating the doc to state 12 months as per :chsiang and :jimm request.

Comment 3

[Nicole Shadowen]

Hi, I'm on PTO until Monday, July 27, and will respond first thing then. Thanks

Comment 4

[Zibi Braniecki [:zbraniecki][:gandalf]]

Thanks Nicole! Tim offered to take it over and we'd like to try to land it soon!

Comment 5

[Tim Smith (inactive) 👨‍🔬 [:tdsmith]]

Comment on attachment 9165225 [details]
CC Autofill Data Review.txt

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, the metadata in Events.yaml and the probe dictionary.

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

Yes, the Firefox telemetry opt-out.

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

n/a; temporary collection

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, interaction 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**?

Flow IDs are identifier-like but aren't persisted beyond a session, so I assert that these aren't identifiers.

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

Yes.

8) Does there need to be a check-in in the future to determine whether to renew the data?

Up to the team to renew probes before they expire.

9) Does the data collection use a third-party collection tool?

Nope.

Comment 6

[Zibi Braniecki [:zbraniecki][:gandalf]]

Attachment: CC Autofill Data Review, part 2.txt

This is complementary to the previous data review. We're adding several scalars, one histogram and several fields to the already present events.

Comment 7

[Tim Smith (inactive) 👨‍🔬 [:tdsmith]]

Comment on attachment 9167762 [details]
CC Autofill Data Review, part 2.txt

looks good; thanks!

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, in the probe definition files and the [Probe Dictionary](https://probes.telemetry.mozilla.org/).

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

Yes, the [Firefox telemetry opt-out](https://support.mozilla.org/en-US/kb/share-data-mozilla-help-improve-firefox).

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

Yes, jimm and chsiang

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1 (technical data)/Category 2 (interaction 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 there need to be a check-in in the future to determine whether to renew the data?

:gandalf et al are responsible for renewing the event telemetry as required; other events are permanent.

9) Does the data collection use a third-party collection tool?

Nope.