1841892 - Desktop shopping data collection

Status: RESOLVED FIXED

(Firefox :: Shopping, task)

Description

[Perry McManis [:perry.mcmanis]]

Placeholder for implementation of instrumentation around metrics for the new shopping component (fakespot)

Comment 1

[Perry McManis [:perry.mcmanis]]

Attachment: WIP: Bug 1841892 - shopping instrumentation

Comment 2

[Perry McManis [:perry.mcmanis]]

Initially, we will only want to land content-agnostic events.

As a concrete example, the Shopping UI will display a rating of how reliable the review is considered to be. We would not send in an event what that reliability rating was, what product it was, or what commerce site was being viewed.

Comment 3

[Perry McManis [:perry.mcmanis]]

An challenge that has arisen is the limit on glean metric names.

We have switched over to using the Event metric type (to live on the event ping), but it is my desire to see us follow a taxonomy in naming. Specifically, the organization of events should follow a Component.Element.Event structure.

I will be temporarily using the category system to fill in for this, but either we need to expand the limit or potentially commit to DE resourcing against it to do the transformation after the fact.

Comment 4

[Alessio Placitelli [:Dexter]]

Ack!

Comment 5

[Perry McManis [:perry.mcmanis]]

Attachment: shopping_metrics_dr.txt

This is a data review request for several of the UI interaction events we will want to get implemented.

Comment 6

[Travis Long [:travis_]]

Comment on attachment 9349890 [details]
shopping_metrics_dr.txt

Data Review

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.

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

Yes, through the data preferences in the application settings.

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

N/A, collection to end by version 122 or be renewed

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

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?

No

Result

data-review+

Comment 7

[Perry McManis [:perry.mcmanis]]

We will be changing the name of shopping_surface_trusted_deal_displayed to more accurately reflect what it will actually measure, so it will become shopping_surface_trusted_deal_impression. There are no changes to any of the details of this measure, ONLY the name is changing.

Comment 8

[Perry McManis [:perry.mcmanis]]

To avoid duplication with category, names will be dropping the shopping prefix.

For example, shopping.shopping_surface_closed will become shopping.surface_closed. In general, names will follow the pattern of shopping.surface*, shopping.address_bar*, etc.

Comment 9

[Jared Hirsch [:jhirsch] (PTO, back 5/28) (he/him) (Needinfo please)]

Closing this separate telemetry metabug and shifting remaining tasks into the general shopping backlog, as the front-end team will handle telemetry duties in the future.