Adjust the urlbar.abandonment and urlbar.engagement events

[data-sync-user]

Looking at the event sequences, it looks like the urlbar.abandonment event may be firing too often. I’m seeing a large number of cases where urlbar.abandonment and awesomebar.engagement are being sent at the same time, and then some where we see urlbar.abandonment , awesomebar.engagement , urlbar.engagement  together.The rate of search_result_tap is lower than I expected (<10% of (engagement + abandonment) across all suggestion types). However, this is maybe not that surprising given that these are clicks/taps of suggestions. On desktop the rate of clicks per search session for search suggestions is around 10%.

I think adding back the awesomebar events would be a good idea while the urlbar events are still new so we have a baseline, as Lina suggested. Does the logic for when the urlbar events fire differ from what was used for the awesomebar events? It would be good if the urlbar events can build on the awesomebar ones since we already had a discussion to align on the behaviour for those ones.

┆Issue is synchronized with this Jira Bug

[data-sync-user]

➤ Stefan Vladut commented:

to test this please verify that the urlbar.abandonment and urlbar.engagement events include only the visible search results instead of the whole list and that the awesomebar.engagement and awesomebar.abandonment events are sent alongside the previous 2 events.

[data-sync-user]

➤ Alina Moldovan commented:

Validated as fixed using FF v124 (39587) and iPhone 15+ (17.4)

A different bug was logged for the remaining issue: [[FXIOS-8622] #19140 ⁃ Telemetry - Incorrect "n_results" and "results" values are displayed for urlbar.abandonment & urlbar.engagement & urlbar.impression - Jira (atlassian.net)|https://mozilla-hub.atlassian.net/browse/FXIOS-8622]