Add Telemetry for cookie banner handling coverage
Categories
(Core :: Privacy: Anti-Tracking, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox109 | --- | fixed |
People
(Reporter: timhuang, Assigned: timhuang)
References
Details
Attachments
(5 files)
To answer the following question
How many sites covered do cookie banner handling in an all or private session (Top URL loads)
We collect the data when the page loads to see if there is a hit or miss on the cookie banner rule list. And we would like to know the following things
- Cookie Rule coverage
- Click Rule coverage
- Overall coverage
And the data should be divided by - coverage by loads
- coverage by domains (duplicate loads)
There are two places where we can collect the data,
- nsCookieBannerService::GetRuleForDomain()
- Web Progress changes for top-level navigations.
|
Assignee | |
Updated•3 years ago
|
|
|
Assignee | |
Comment 1•3 years ago
|
||
|
|
Assignee | |
Comment 2•3 years ago
|
||
The patch implements nsCookieBannerService::ReportRuleLookupTelemetry().
In the function, we report two telemetry probes related to hit/miss rule
lookups: one for rule lookup hit/miss counts by loads, another for
counts by domains. We will only report once for each domain.
Depends on D162628
|
|
Assignee | |
Comment 3•3 years ago
|
||
We collect the rule lookup telemetry when getting cookie banner click
rule because the cookie banner clicking will be called for both
top-level pages and iframes.
This patch adds a parameter to
nsICookieBannerService.getClickRulesForDomain to indicate if the caller
is in top-level context so that we can know and report the data to
corresponding telemetry labels. It also instructs GetRuleForDomain() to
report telemetry if it is called from GetClickRulesForDomain().
Depends on D162629
|
|
Assignee | |
Comment 4•3 years ago
|
||
Depends on D162630
|
|
Assignee | |
Comment 5•3 years ago
|
||
|
||
Comment 6•3 years ago
|
||
Comment on attachment 9304727 [details]
data-request-Bug1797073.md
DATA COLLECTION REVIEW RESPONSE:
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 is Telemetry so can be controlled through Firefox'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 in Firefox 115.
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. (Though the description says "by domain", this is the unit of resolution. The domain isn't collected.)
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 8•3 years ago
|
||
Backed out for causing failures on test_cookiebannerlistservice.js
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | toolkit/components/cookiebanners/test/unit/test_cookiebannerlistservice.js | xpcshell return code: 0
|
|
Assignee | |
Updated•3 years ago
|
|
||
Comment 9•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/ca1fba1367f8
https://hg.mozilla.org/mozilla-central/rev/6a04f08bb5d8
https://hg.mozilla.org/mozilla-central/rev/3b40c920ab8d
https://hg.mozilla.org/mozilla-central/rev/3477658b7a3c
Description
•