Now we have Event Telemetry additional to the existing probes. Event Telemetry will report the following information EVENTS: urlbar#engagement#click urlbar#engagement#enter urlbar#engagement#drop_go urlbar#engagement#paste_go urlbar#abandonment#blur EVENT VALUE: The value for the event is the type of initial interaction: "typed", "pasted", "dropped", "topsites" EXTRA DATA: elapsed time, number of characters only for engagement: selection index, selection type We already report keyed scalars counting the number of each event, the above event name is the key, even if recording is disabled. To get events recording must be enabled flipping the browser.urlbar.eventTelemetry.enabled pref, or using the browser.urlbar.engagementTelemetry WebExtension API. Based on this data, data-science and product management should come to a definition of success and a way to visualize it. Please reach engineering if you are missing something. I'm assigning this to Ryan, should likely be discussed with Teon and Connor.
Bug 1570683 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Now we have Event Telemetry in addition to the existing probes. Event Telemetry will report the following information EVENTS: urlbar#engagement#click urlbar#engagement#enter urlbar#engagement#drop_go urlbar#engagement#paste_go urlbar#abandonment#blur EVENT VALUE: The value for the event is the type of initial interaction: "typed", "pasted", "dropped", "topsites" EXTRA DATA: elapsed time, number of characters only for engagement: selection index, selection type We already report keyed scalars counting the number of each event, the above event name is the key, even if recording is disabled. To get events recording must be enabled flipping the browser.urlbar.eventTelemetry.enabled pref, or using the browser.urlbar.engagementTelemetry WebExtension API. Based on this data, data-science and product management should come to a definition of success and a way to visualize it. Please reach engineering if you are missing something. I'm assigning this to Ryan, should likely be discussed with Teon and Connor.
Now we have Event Telemetry in addition to the existing probes. Event Telemetry will report the following information EVENTS: urlbar#engagement#click urlbar#engagement#enter urlbar#engagement#drop_go urlbar#engagement#paste_go urlbar#abandonment#blur EVENT VALUE: The value for the event is the type of initial interaction: "typed", "pasted", "dropped", "topsites" EXTRA DATA: elapsed time, number of characters only for engagement: selection index, selection type We already report keyed scalars counting the number of each event, the above event name is the key, even if recording is disabled. To get events, recording must be enabled by flipping the browser.urlbar.eventTelemetry.enabled pref, or using the browser.urlbar.engagementTelemetry WebExtension API. Based on this data, data-science and product management should come to a definition of success and a way to visualize it. Please reach engineering if you are missing something. I'm assigning this to Ryan, should likely be discussed with Teon and Connor.