Closed Bug 1645906 Opened 4 months ago Closed 3 months ago

Telemetry for navigation/topics component


(Firefox :: New Tab Page, enhancement, P1)




Firefox 80
80.1 - June 29 - July 12
Tracking Status
firefox79 + verified
firefox80 --- verified


(Reporter: thecount, Assigned: gsuntop)




(2 files)

Right now we don't have much in the way of click and impression data on the topics component.

We wanted an experiment coming up soon so we should probably get this fixed so we can track it.

We need to send an event ping for when users click on a popular topic. We do not currently do this.

An event ping with event = “CLICK” and source = “POPULAR_TOPICS” would work.

I don't think we need to send an impression. For now we can proxy with the existing tile impression events.

Assignee: nobody → gsuntop
Iteration: --- → 79.2 - June 15 - June 28
Priority: -- → P2
Priority: P2 → P1

Test steps:

Attached file request.txt

Attaching Data Collection request for Kenny to review.

Attachment #9160148 - Flags: data-review?(kenny)

Will want to request this for uplift into Fx 79 Beta as soon as we can (but definitely by 14 July).

Iteration: 79.2 - June 15 - June 28 → 80.1 - June 29 - July 12
Comment on attachment 9160148 [details]


    Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

The event is documented in: browser/components/newtab/docs/v2-system-addon/

The specific change is in this PR:

And will be available here when merged:

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

Yes. Users can opt-out the data collection by either disabling the telemetry of Activity Stream or disabling the Firefox telemetry as a whole.

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

Yes, Kirill Demtchouk is responsible.

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

Kirill has classified this as Category 3 because it tracks clicks on "topic" names (currently: must-reads, productivity, health, finance, technology, more-recommendations). It is unclear to me whether this qualifies as Category 3 or Category 2, but to be safe I am escalating this for review/approval.

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

Default on for all channels and countries/locales that have Pocket new tab recs enabled.

    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)?


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


    Does there need to be a check-in in the future to determine whether to renew the data?

No. This collection is permanent.

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


Result: Pending
Flags: needinfo?(agray)

Trust review notes: This collection includes information about the user’s direct engagement with the service in which there is no or little risk of personal identification. My evaluation is that tracking clicks on "topic" names (currently: must-reads, productivity, health, finance, technology, more-recommendations) is information about the user’s in-product journeys and product choices helpful to understand engagement (attitudes) for example, selections of add-ons or tiles to determine potential interest categories etc.

Therefore, this is reasonably Cat 2 collection.

Flags: needinfo?(agray)
Comment on attachment 9160148 [details]

Updated to data-review+ based on agray's input in comment 7
Attachment #9160148 - Flags: data-review?(kenny) → data-review+
Pushed by
Adding telemetry to Popular Topics r=nanj

[Tracking Requested - why for this release]:

Comment on attachment 9159525 [details]
Bug 1645906 - Adding telemetry to Popular Topics

Beta/Release Uplift Approval Request

  • User impact if declined: None.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This is only an added telemetry event. Reporting mechanism is already in place and there is no user facing functionality added here.
  • String changes made/needed:
Attachment #9159525 - Flags: approval-mozilla-beta?
Flags: qe-verify+
Blocks: 1649635
Pushed by
Adding telemetry to Popular Topics r=thecount
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 80
QA Whiteboard: [qa-triaged]
Flags: needinfo?(gsuntop)

Comment on attachment 9159525 [details]
Bug 1645906 - Adding telemetry to Popular Topics

Approved for 79.0b5. We should try to verify the incoming Telemetry data as soon as we can, though.

Attachment #9159525 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

This enhancement was part of the work done in PI-694 that was signed-off as GREEN. Considering this I am marking this as VERIFIED.

Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.