1865199 - Add telemetry to track how often the Partitioned cookie attribute is set

Status: RESOLVED FIXED

(Core :: Privacy: Anti-Tracking, enhancement)

Description

[Benjamin VanderSloot [:bvandersloot]]

We want to know how often this is being seen by Firefox users as soon as we can. Let's implement this and get data flowing, without worrying about how to handle the header properly.

Comment 1

[Benjamin VanderSloot [:bvandersloot]]

DATA REVIEW REQUEST

1. What questions will you answer with this data?

How often do we see CHIPS used by websites that Firefox users visit? Are those Partitioned cookies set in same-site contexts?

2. Why does Mozilla need to answer these questions? Are there benefits for users?
   Do we need this information to address product or business requirements?

The answer to these questions will inform the timeline and strategy for the deployment of CHIPS in our project to deprecate third-party cookies by default.

3. What alternative methods did you consider to answer these questions?
   Why were they not sufficient?

We considered relying on Chrome engineers to share data for their deployment, but decided that it is best to understand the character of our users' experience.

4. Can current instrumentation answer these questions?

No.

5. List all proposed measurements and indicate the category of data collection for each
   measurement, using the Firefox data collection categories found on the Mozilla wiki.

Measurement Name	Measurement Description	Data Collection Category	Tracking Bug
networking.set_cookie	This counts the number of times we set a cookie. Introduced as a denomenator for measuring CHIPS adoption.	Technical data	https://bugzilla.mozilla.org/1865199
networking.set_cookie_foreign	This counts the number of times we set a cookie from a foreign (not same-site) context. Introduced as a denomenator for measuring CHIPS adoption.	Technical data	https://bugzilla.mozilla.org/1865199
networking.set_cookie_foreign_partitioned	This counts the number of times we set a cookie that has the Partitioned attribute in a foreign (not same-site) context. This tracks the adoption of CHIPS.	Technical data	https://bugzilla.mozilla.org/1865199
networking.set_cookie_partitioned	This counts the number of times we set a cookie that has the Partitioned attribute. This tracks the adoption of CHIPS.	Technical data	https://bugzilla.mozilla.org/1865199

6. Please provide a link to the documentation for this data collection which
   describes the ultimate data set in a public, complete, and accurate way.

This collection is Glean so is documented in the Glean Dictionary.

7. How long will this data be collected?

This collection has expiry '2024-11-01'. I chose this to cover through Chrome's projected third-party cookie deprecation, which should be the extent of this data's usefulness. However, this may require extension if Chrome postpones their third-party cookie deprecation (again).

8. What populations will you measure?

All channels, countries, and locales. No filters.

9. If this data collection is default on, what is the opt-out mechanism for users?

These collections are Glean. The opt-out can be found in the product's preferences.

10. Please provide a general description of how you will analyze this data.

We will create a dashboard to monitor the ratios of all cookies that have the Partitioned attribute, the ratio of foreign cookies that have the Partitioned attribute, and the ratio of cookies with the Partitioned attribute that are foriegn.

11. Where do you intend to share the results of your analysis?

Monitoring internal to the team only.

12. Is there a third-party tool (i.e. not Glean or Telemetry) that you
    are proposing to use for this data collection?

No.

Comment 2

[Benjamin VanderSloot [:bvandersloot]]

Attachment: data review request

-

Comment 3

[Benjamin VanderSloot [:bvandersloot]]

Attachment: drr

Comment 4

[Benjamin VanderSloot [:bvandersloot]]

Comment on attachment 9364585 [details]
data review request

duplicate.

Comment 5

[Benjamin VanderSloot [:bvandersloot]]

Bugzilla was giving me upload errors, but seems to have accepted them anyway. All copies are identical. Let's treat the last one as the canonical request!

Comment 6

[[e-mail]]

Comment on attachment 9364586 [details]
drr

Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?
​
Yes.
​
Is there a control mechanism that allows the user to turn the data collection on and off?
​
Yes. This collection can be controlled through the product's preferences.
​
If the request is for permanent data collection, is there someone who will monitor the data over time?
​
No. This collection will expire 2024-11-01
​
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.
​
Is the data collection request for default-on or default-off?
​
Default on for all channels.
​
Does the instrumentation include the addition of any new identifiers?
​
No.
​
Is the data collection covered by the existing Firefox privacy notice?
​
Yes.
​
Does the data collection use a third-party collection tool?
​
No.
​

Result: datareview+

Comment 7

[Benjamin VanderSloot [:bvandersloot]]

Attachment: Bug 1865199 - Parse partitioned attribute - r=#cookies!

Only parse the attribute so that we can do telemetry with it.

Comment 8

[Benjamin VanderSloot [:bvandersloot]]

Attachment: Bug 1865199 - Add telemetry to determine what percent of Set-Cookies are Partitioned - r=#cookies!

Depends on D194235

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/42029f50de7d
Parse partitioned attribute - r=cookie-reviewers,timhuang
https://hg.mozilla.org/integration/autoland/rev/1772dfe55a1e
Add telemetry to determine what percent of Set-Cookies are Partitioned - r=cookie-reviewers,timhuang

Comment 10

[Serban Stanca [:SerbanS]]

Backed out for causing mochitests failures in browser_partitioned_telemetry.js.

• Backout link
• Push with failures
• Failure Log
• Failure line: TEST-UNEXPECTED-FAIL | netwerk/cookie/test/browser/browser_partitioned_telemetry.js | initially empty - all set cookies - Got 30, expected undefined

Comment 11

[Benjamin VanderSloot [:bvandersloot]]

I needed to clear telemetry at the start of the test. Relanding with that change.

Comment 12

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/92f07e8c3190
Parse partitioned attribute - r=cookie-reviewers,timhuang
https://hg.mozilla.org/integration/autoland/rev/2ec416e3c7f7
Add telemetry to determine what percent of Set-Cookies are Partitioned - r=cookie-reviewers,timhuang

Comment 13

[Norisz Fay [:noriszfay]]

Backed out for causing bc failures on browser_partitioned_telemetry.js

Backout link

Push with failures

Failure log

Comment 14

[Benjamin VanderSloot [:bvandersloot]]

Relanding with a fix for an opt-only failure, once it passes try auto

Comment 15

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/450cd0d000b5
Parse partitioned attribute - r=cookie-reviewers,timhuang
https://hg.mozilla.org/integration/autoland/rev/4fb9d539b9fd
Add telemetry to determine what percent of Set-Cookies are Partitioned - r=cookie-reviewers,timhuang

Comment 16

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/450cd0d000b5
https://hg.mozilla.org/mozilla-central/rev/4fb9d539b9fd