Telemetry Address Bar + Search

[bbinto]

Understand how (often) users perform searches

• As a product owner, I want to know what the most successful search access point is so we can optimize our search story
• As a product owner, I want to know if people type in more domains or search keyword

What questions will you answer with this data?

• What’s the most successful search access point (# of search queries), goal is to improve search access points

Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

• Improve search and search counts
• Help users find the information they are searching for quicker

What probes

• address bar: type in URL vs search keyword
• bottom address bar activity vs. homescreen search bar activity
• do users click on autocomplete
• do users click on search suggestions
• do users copy the URL bar (out of scope, feature not implemented yet)
• do users copy of key word (out of scope, feature not implemented yet)

Dependencies (Added by PM and Eng)

• Glean SDK Event pings working in Android components

Acceptance Criteria (Added by PM)

• Event pings can be queried via re:dash
• We are sending telemetry events for the actions listed in the requirements
• We have documented the telemetry
• We have asked a data steward to review the telemetry

┆Issue is synchronized with this Jira Task

[boek]

Hey @bbinto,

We currently don't have a method to copy the URL from the URL bar, but I created a story #1068
Secondly, what does do users copy of key word mean?

[bbinto]

Thanks @boek.

Secondly, what does do users copy of key word mean?

That'd be similar to copy the URL from the address bar, i.e. if somebody types in a search term / key word, how often do they copy it from the address bar?

Both, since the feature is not implemented yet, should be removed. I'll update the initial field.

[georgf]

What probes

* address bar: type in URL vs search keyword

* bottom address bar activity vs. homescreen search bar activity

* do users click on autocomplete

* do users click on search suggestions

* do users copy the URL bar (out of scope, [feature](https://github.com/mozilla-mobile/fenix/issues/1068) not implemented yet)

* do users copy of key word (out of scope, [feature](https://github.com/mozilla-mobile/fenix/issues/1068) not implemented yet)

I think there are two (or more?) themes in here:

1. search counts, broken down by different dimensions
2. other UI actions like copying

For the search counts, i think it would be good to break this out for a spec on how we'll instrument search counts.
I think mconnor or others have requirements here too.

[georgf]

I assume for search instrumentation we'd need:

• Something comparable to Firefox Desktops search counts (in Glean these could be labeled counters, sent through the metrics ping).
• Search events, for usage in Amplitude & Redash.

[boek]

@georgf What do you mean by search events on your second point?

Also I did look into using use_counter to compare search counts over the different search engines, but it wasn't implemented yet in the SDK, Would we also want to add just a generic counter for all search events?

[georgf]

I think you already implemented the search events - i'm not sure which exactly are required :)

For other search instrumentation like counts...
On Desktop we have SEARCH_COUNTS as the most critical metric.

That is a keyed count histogram, the equivalent in Glean would be a labeled count. We're still backfilling documentation, but basically (edit: added docs):

• You add labeled: true in the metrics.yaml
• Then use yourMetric["some string"].add().

But this is just assuming we'd use the same approach.
The search team or assigned data scientist might have more current or additional requirements for this though.
Following up with them (mconnor, javaun, emily thompson?) might be good.