1702178 - Update search datasets to reflect SERP reporting changes in Firefox 89 (desktop)

Status: RESOLVED FIXED

(Data Platform and Tools :: General, task)

Description

[Mark Banner (:standard8)]

In bug 1634564, we have added new keyed scalars for browser.search.content.*

This telemetry is similar to the existing SERP results logged to SEARCH_COUNTS, but with the SAP origin included as well.

We need to update the search datasets to handle the new keyed scalars, so that at some stage we can remove the old SEARCH_COUNTS logging from Firefox.

Documentation will appear here soon: https://firefox-source-docs.mozilla.org/browser/search/telemetry.html#searchserptelemetry-jsm

More details:

The new keyed scalars replace the SERP part of SEARCH_COUNTS, i.e. those with the key of the format <provider>.in-content:[sap|sap-follow-on|organic]:[code|none].

The new keyed scalars are of the format browser.search.content.*, where * is the SAP associated with the SERP. The key format is similar but not quite the same: <provider>:[tagged|tagged-follow-on|organic]:[<code>|none]

For any given key, the sum of the new browser.search.content.* scalars should match the count logged for the same key in SEARCH_COUNTS.

Comment 1

[Mark Banner (:standard8)]

(In reply to Mark Banner (:standard8) from comment #0)

We need to update the search datasets to handle the new keyed scalars, so that at some stage we can remove the old SEARCH_COUNTS logging from Firefox.

I've just filed bug 1702180 for the clean-up.

Comment 2

[Ben Wu [:benwu]]

This was done with https://github.com/mozilla/bigquery-etl/pull/2253
See https://mozilla-hub.atlassian.net/browse/DS-1603 for some more context