1788960 - Send engagement telemetry event when re-launching Firefox to complete a background task message notification

Status: RESOLVED FIXED

(Toolkit Graveyard :: Notifications and Alerts, enhancement)

Description

[Nick Alexander :nalexander [he/him]]

After Bug 1781929, a (Windows) toast notification popped by a background task message will, upon user interaction, relaunch Firefox (optionally navigating to a launch_url). To measure how frequently such a call to action is invoked, we need to send a telemetry event when we process this relaunch. There's a natural point to do this; we just need to funnel an identifier through the relevant APIs and decide the form of the telemetry event.

Comment 1

[Romain Testard [:RT]]

Could we potentially extend https://probes.telemetry.mozilla.org/?search=launch_method&view=detail&probeId=scalar%2Fos.environment.launch_method or https://probes.telemetry.mozilla.org/?search=pdf&view=detail&probeId=scalar%2Fos.environment.launched_to_handle?

Comment 2

[Nick Alexander :nalexander [he/him]]

(In reply to Romain Testard [:RT] from comment #1)

Could we potentially extend https://probes.telemetry.mozilla.org/?search=launch_method&view=detail&probeId=scalar%2Fos.environment.launch_method or https://probes.telemetry.mozilla.org/?search=pdf&view=detail&probeId=scalar%2Fos.environment.launched_to_handle?

We could, but I think a (Glean) event makes the most sense. launched_to_handle would be sensible except that we'd want to indicate something like notification, and then we don't have a sensible place to stuff the tag/campaign id of the notification.

We really only care about the counts of re-engaged users (and pivoting on environment data), so I'll add a new event unless I hear strong direction otherwise.

Comment 3

[Romain Testard [:RT]]

Though all other desktop data is not on Glean yet so we won't be able to correlate this data with any other telemetry data if we use Glean, right?

Comment 4

[Nick Alexander :nalexander [he/him]]

(In reply to Romain Testard [:RT] from comment #3)

Though all other desktop data is not on Glean yet so we won't be able to correlate this data with any other telemetry data if we use Glean, right?

I thought the Glean Desktop data was not so separated, but I see that you're right. So I'll either send a regular Firefox Legacy Telemetry event or extend the existing launched_to_handle telemetry to include this, perhaps with a launched_to_handle_extra string that can capture the additional tag/campaign id.

Comment 5

[Nick Alexander :nalexander [he/him]]

Attachment: Bug 1788960 - Part 1: Round trip `name` for privileged alerts through Firefox restart. r?nrishel

On Windows, when an alert is privileged and name is non-empty, round
trip its name (as privilegedName) through the Windows notification
mechanism, and provide it to the "relaunch" callback.

Comment 6

[Nick Alexander :nalexander [he/him]]

Attachment: Bug 1788960 - Part 2: Telemetry event when completing chrome-privileged Windows native notification with `name`. r?chutten

This allows to connect a backgroundTaskMessage popping a toast
notification with a given name through to a re-engagement with
Firefox.

Depends on D156636

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

The following patch is waiting for review from an inactive reviewer:

ID	Title	Author	Reviewer Status
D156636	Bug 1788960 - Part 1: Round trip name for privileged alerts through Firefox restart. r?nrishel	nalexander	nrishel: Inactive

:nalexander, could you please find another reviewer?

For more information, please visit auto_nag documentation.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

The following patch is waiting for review from a reviewer who resigned from the review:

ID	Title	Author	Reviewer Status
D156637	Bug 1788960 - Part 2: Telemetry event when completing chrome-privileged Windows native notification with name. r?chutten	nalexander	chutten: Resigned from review

:nalexander, could you please find another reviewer?

For more information, please visit auto_nag documentation.

Comment 9

[Nick Alexander :nalexander [he/him]]

Attachment: 1788960-review-1.md

Comment 10

[Chris H-C :chutten]

Comment on attachment 9294289 [details]
1788960-review-1.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?

Yes, [e-mail], and [e-mail] are responsible.

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+

Comment 11

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/b91f04ec9d73
Part 1: Round trip `name` for privileged alerts through Firefox restart. r=nrishel
https://hg.mozilla.org/integration/autoland/rev/0cf586a90214
Part 2: Telemetry event when completing chrome-privileged Windows native notification with `name`. r=chutten

Comment 12

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/b91f04ec9d73
https://hg.mozilla.org/mozilla-central/rev/0cf586a90214