1744748 - Missing browser.search.withads.urlbar_handoff in telemetry for duckduckgo searches

Status: RESOLVED WORKSFORME

(Firefox :: Search, defect)

Description

[Pablo]

Description
missing browser.search.withads.urlbar_handoff in telemetry for duckduckgo searches

Tested on
Windows10 64bit affected.
MacOS 11 affected.
ubuntu 21 affected

With versions
94.0.2 ( affected)
95 beta ( affected)
96.0a1 nightly (affected)

Steps to reproduce
-Launch firefox
-Search duckduckgo as default search engine
-open NEW TAB page and using the web search input "samsung galaxy"
-notice that the search shows ads.
-check telemetry

Actual result
This is missing in telemetry:" browser.search.withads.urlbar_handoff"

Expected result

this record should appear on telemetry:

"""browser.search.withads.urlbar_handoff"": {
""duckduckgo:tagged"": 1"

Comment 1

[Mark Banner (:standard8) (afk until 21st July)]

I've just tried this on latest nightly with DDG and it all seems to work fine. I would suggest testing other access points at the same time (e.g. direct from the address bar), and searching for just "withads" in telemetry so you can see if they show elsewhere.

Comment 2

[Adrian Florinescu [:aflorinescu]]

I just love this area and how random it sometimes is. Pablo and I retested this issue again with the following results.

At least for right now, we could reproduce reliable not having withads for duckduckgo on a new profile: ddg search results in page would be displayed, but no telemetry recorded -> this would be bug 1673868. When we record no ads search page, browser.search.withads.urlbar_handoff would not be recorded either. At least for todays results, seems that if we record withads, we also record withads.urlbar_handoff.

Additionally, we have also noticed that in case of follow-on web search will return browser.search.withads.unknown instead of browser.search.withads.urlbar_handoff. (this also reproduces with google, so it's not due to the fact that ddg doesn't have follow-on telemetry)

The above was tested on Mac11 and Windows 10 with the same results.

Comment 3

[Mark Banner (:standard8) (afk until 21st July)]

(In reply to Adrian Florinescu [:aflorinescu] from comment #2)

At least for right now, we could reproduce reliable not having withads for duckduckgo on a new profile: ddg search results in page would be displayed, but no telemetry recorded -> this would be bug 1673868.

Ok, I think lets close this as wfm for now, and we'll leave that open for more investigation.

Additionally, we have also noticed that in case of follow-on web search will return browser.search.withads.unknown instead of browser.search.withads.urlbar_handoff. (this also reproduces with google, so it's not due to the fact that ddg doesn't have follow-on telemetry)

The follow-on case is interesting. Might be worth comparing what happens if you start in the address bar. We should probably get a bug filed on that though.