Closed Bug 1797078 Opened 3 years ago Closed 3 years ago

Add Telemetry for cookie banner handling auto clicking

Categories

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

task

Tracking

()

RESOLVED FIXED
109 Branch
Tracking Status
firefox109 --- fixed

People

(Reporter: timhuang, Assigned: emz)

References

(Blocks 1 open bug)

Details

Attachments

(5 files, 1 obsolete file)

We would like to collect data related to cookie banner auto clicking, including

  • Did we detect the banner
    • This will include the cases where the banner has been already handled.
  • Did we correctly handle the banner (By clicking the banner)
    • Count how often we successfully handle a banner by clicking?
  • Why did it fail?
    • Found the banner but it's hidden.
    • Found the banner but couldn't find the button
    • Cannot handle the banner after the timeout
  • When we successfully handle the cookie banner.
    • Handle banner on DOMContentLoaded event
    • Handle banner before load event
    • Handle banner within timeout
  • How long on average does it take for the banner to show up / until we click the banner after DOMContentLoaded?
Assignee: nobody → pbz
Status: NEW → ASSIGNED

This prevents running the cookie banner click code for sites which have a rule
with an empty click object. This is important for performance reasons and
prevents us from recording invalid "banner not found" telemetry.

Depends on D161824

Attachment #9302942 - Attachment description: WIP: Bug 1797078 - Add cookiebanner.click_result metric. r=timhuang! → Bug 1797078 - Add cookiebanner.click_result metric. r=timhuang!
Attachment #9302942 - Attachment description: Bug 1797078 - Add cookiebanner.click_result metric. r=timhuang! → Bug 1797078 - Add cookieBannersClick.result metric. r=timhuang!
Attached file DATA REVIEW REQUEST.md
Attachment #9303750 - Flags: review?(chutten)
Attachment #9303750 - Flags: review?(chutten) → data-review?(chutten)

Comment on attachment 9303750 [details]
DATA REVIEW REQUEST.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 Fx 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.

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+

Attachment #9303750 - Flags: data-review?(chutten) → data-review+
Pushed by pzuhlcke@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ec9139e9e08a Add cookie.banners.click_handle_duration metric. r=timhuang https://hg.mozilla.org/integration/autoland/rev/1d302d459cf0 Avoid importing empty click rules. r=timhuang https://hg.mozilla.org/integration/autoland/rev/e3c3f534f19f Add cookieBannersClick.result metric. r=timhuang https://hg.mozilla.org/integration/autoland/rev/dfacd59c45d8 Tests for cookie banner clickResult telemetry. r=timhuang
Regressions: 1801717
Regressions: 1797094
Blocks: 1804328
Blocks: 1805653
Blocks: 1821738

This bug adds basic telemetry if window.print() is used or not in
Android through GeckoView.

Attachment #9325531 - Attachment is obsolete: true

Sorry, didn't mean to add a patch here! I had an incorrect bug number on the git commit when submitting an unrelated patch.

Depends on: 1900769
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: