1799190 - Request improvement to `browser_search_with_ads` and `browser_search_ad_clicks`

Status: NEW

(Firefox for iOS :: Telemetry, enhancement)

Description

[Xuan Luo]

This is for Firefox iOS. Please see this query for details.

Currently metrics.labeled_counter.browser_search_with_ads and metrics.labeled_counter.browser_search_ad_clicks both report in format as <provider>; while for labeled_counter.search_counts and labeled_counter.search_in_content both report in format <provider>.<source>. Splitting out would help us understand better the metrics from tagged traffic or organic traffic - to enable further understanding of revenue performance.

Fenix is using <provider>.<source> for search_counts, search_in_content, and ad_clicks, and I am requesting improvement of having it for search_with_ads (as here).

Comment 1

[Mark Banner (:standard8)]

(In reply to Xuan Luo from comment #0)

Fenix is using <provider>.<source> for search_counts, search_in_content, and ad_clicks, and I am requesting improvement of having it for search_with_ads (as here).

For SAP telemetry, i.e. search_counts, Fenix is currently using <provider>.<source> format, the same as desktop.

For SERP based Telemetry, i.e. browser.search.in_content, browser.search.with_ads and browser.search.ad_clicks, Fenix is currently using the format <provider>.in-content.<sap|sap-follow-on|organic>.<code|none><.channel>.

This is slightly different from Desktop, which uses <provider>:<tagged|tagged-follow-on|organic>:<code|other|none> for the in-content SERPs, and <provider>:<tagged|organic> for "with ads" and "ad clicks".

Neither Android nor iOS currently record any sources for SERP telemetry. Desktop does via the use of different probe names.

We're currently putting together some documents to discuss what exactly we want here, so we should finalise those before we move forward with this.