1862096 - [toolbar redesign] add missing telemetry events

Status: RESOLVED FIXED

(Fenix :: Toolbar, task, P2)

Description

[Mike a [:mavduevskiy]]

We need telemetry to measure the success of the new toolbar. Hence, all functionality that is being moved around should be measured before and after the UI change. Navigation buttons, toolbar action buttons, swiping mechanism, share and reloading page actions.

Comment 1

[Mike a [:mavduevskiy]]

note to myself: should talk with someone from data team/data stewards what's the optimal way to measure performance of the new design. Should we add flags to existing ones, or there is other ways to tell the events from old and new design apart?

Comment 2

[Mike a [:mavduevskiy]]

I went through the actionable elements of the new design to see what events we are already tracking. Here is the results, with event names if present.

• Voice input (voice_search.tapped)
• QR code
• Navigation buttons (back and forward)
• Triggering addressbar into edit mode (entering text into the address bar) (search_bar_tapped)
• Opening tabs tray (open_tabs_tray)
• Menu (toolbar_menu_visible), the event is only sent when open from a page, and is not sent when opened from the home screen
• Share
• Refresh
• Open in Firefox
• Tab swiped

The majority of actions are not being tracked and we need that information to evaluate if the new design is an improvement for the user. Once the product team considers required telemetry changes, I will proceed to add it.

Comment 3

[Mike a [:mavduevskiy]]

Updated list of existing events.

• Voice input (voice_search.tapped)
• QR code
• Navigation buttons (browser_menu_action, with extras back and forward)
• Triggering addressbar into edit mode (entering text into the address bar) (search_bar_tapped)
• Opening tabs tray (open_tabs_tray)
• Menu (toolbar_menu_visible), the event is only sent when open from a page, and is not sent when opened from the home screen
• Share (browser_menu_action, with share extra)
• Refresh (browser_menu_action, with reload extra)
• Open in Firefox (browser_menu_action, with open_in_fenix extra)
• Tab swiped

Comment 4

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1862096 – add toolbar related telemetry (#4522)

Comment 5

[BMO Github Automation]

Authored by mike a
https://github.com/mozilla-mobile/firefox-android/commit/75ffacbf1b2a5ff13e082a8405da5117a005fbde
[main] Bug 1862096 – add toolbar related telemetry

Comment 6

[Oana Horvath [:ohorvath]]

Hi Mike! Is this something QA can verify now, or since it's part of the larger redesign, should we wait until the feature is complete?

Comment 7

[Mike a [:mavduevskiy]]

Hi, :ohorvath

Yes, it should. We need to verify that we gather telemetry from the old implementation as well, before the feature is complete. So that when we actually run the experiment, we can compare the telemetry from old and new feature implementations.

Comment 8

[miralobontiu]

Verified on the latest Fenix Nightly 123.0a1 from 1/5 with a Google Pixel 8 (Android 14) device.
The following events were generated:

• Voice input: "category": "voice_search"

• QR code: "name": "browser_toolbar_qr_scan_tapped"

• Navigation buttons (back and forward): "name": "browser_menu_action", "extra": { "item": "forward" "name": "browser_menu_action", "extra": { "item": "back"

• Triggering addressbar into edit mode (entering text into the address bar) (search_bar_tapped): "name": "search_bar_tapped"

• Opening tabs tray (open_tabs_tray): "category": "tabs_tray", "name": "opened" "category": "tabs_tray", "name": "closed"

• Menu (toolbar_menu_visible), the event is only sent when open from a page, and is not sent when opened from the home screen: "name": "toolbar_menu_visible"

• Share: "name": "browser_menu_action", "extra": { "item": "share"

• Reload: "name": "browser_menu_action", "extra": { "item": "reload"

• Tab swiped" "name": "toolbar_tab_swipe"

Mike, I am not really sure what action needs to be performed to trigger this: Open in Firefox (browser_menu_action, with open_in_fenix extra)?