1963707 - Add content metadata only for newtab-content ping

Status: ASSIGNED

(Firefox :: New Tab Page, task)

Description

[Nathan Barrett [:nbarrett]]

In the newtab-content ping, add extra metadata (url, publisher, title, time_sensitive) to the following metrics:

• click
• impression
• thumb_voting_interaction
• dismiss

Comment 1

[Nathan Barrett [:nbarrett]]

Attachment: Bug 1963707 - Add content metadata to newtab-content r=#home-newtab-reviewers

Comment 2

[Nathan Barrett [:nbarrett]]

Attachment: Data review request

Comment 3

[Travis Long [:travis_]]

Comment on attachment 9485089 [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

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?

nbarret will be responsible for the permanent collection of this data.

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

Category 3, Stored Content and Communications && Category 2, User Interaction

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

Default-on, for clients enrolled in the experiment.

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

No

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

Yes, pending escalated review confirmation

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

No

Result

data-review pending escalated review process to approve the Category 3 collections

Comment 4

[Travis Long [:travis_]]

Please email https://groups.google.com/a/mozilla.com/g/data-review per the escalated review process to proceed with the data-collection-request. I have filled out the review form in order to help make it easier for the escalated reviewers to process and will give you data-review+ as soon as we hear their response.

Please let me know if you have any questions or issues with the process! Thanks, Travis

Comment 5

[Nathan Barrett [:nbarrett]]

Thanks Travis - just sent an email to the data-review group.

Comment 6

[Nathan Barrett [:nbarrett]]

I sent an email to [e-mail], but haven't heard anything back. What is the usual turn around?

Comment 7

[Travis Long [:travis_]]

It's usually within a week and we are fast approaching that date. Typically you should get a response with at least acknowledging it was received. Let me check in on this and see what the status/situation is. Thanks for letting me know.

Comment 8

[Travis Long [:travis_]]

Still awaiting a response from this, sorry for the delay I'll try pinging again.

Comment 9

[Martin Thomson [:mt:]]

Hi Nathan,

I'm finding this request a little challenging. It's not in the template (and we're looking to improve that) but what I really would like to get from you is an analysis of why this information would either have no additional privacy impact relative to existing fields in the pings or (and this might be preferable) what the privacy implications of the ping is as a whole. Having a list of what you are adding is rarely sufficient to understand the privacy implications because it is often how one set of fields is connected to another set of fields that leads to privacy challenges.

If my understanding of the system is correct, there is some amount of personalization going on here. But that personalization is extremely limited in scope. How that personalization manifests on the page is important. If there are per-user things that drive the choice of content that is shown (and where it is shown), then we need to keep that personalization isolated. That's why we use OHTTP. To properly understand the privacy of this arrangement, we need a clear articulation of what personal information enters the system and what other information that touches.

If our goal is to understand, in general, whether people are interacting with tiles (with clicks, impressions, or dismissals). That information probably does need to be connected with the URL. I don't know why it would also need a title if that has a fixed relationship with the URL.

(It is probably not for this, but if we only need to know about this in the aggregate, OHTTP is the wrong tool. We have DAP.)