The target": "non_ads_link" is registered in the serp glean telemetry after clicking the Shopping tab from Google
Categories
(Firefox :: Search, defect, P2)
Tracking
()
People
(Reporter: cmuntean, Assigned: jteow)
References
Details
(Whiteboard: [sng])
Attachments
(2 files)
[Notes]:
- We haven't managed to reproduce this issue with Bing. The "target": "shopping_tab", is correctly registered in the "engagement" ping after clicking the Shopping tab from Google.
[Affected versions]:
- Firefox Release 121.0.1 (Build ID: 20240108143603)
- Firefox Beta 122.0b8 (Build ID: 20240110091443)
- Firefox Nightly 123.0a1 (Build ID:20240117145030)
[Affected Platforms]:
- macOS 13.1
- Windows 10 x64
- Ubuntu 20.04
[Prerequisites]:
- Have Google set as default search engine.
- Have a Firefox profile with the following prefs in the "about:config" page:
- browser.search.serpEventTelemetry.enabled set to true
[Steps to reproduce]:
- Open the browser from the prerequisites.
- Navigate to "about:glean" and create a debug tag.
- Open a new tab and search in urlbar for "shopping shoes".
- Click on the "Shopping" tab from the Google page.
- Go to “https://debug-ping-preview.firebaseapp.com/” and select the previous debug tag.
- Click on the last event sent.
- Observe the "engagement" ping.
[Expected result]:
- The target": "shopping_tab" is correctly registered.
[Actual result]:
- The target": "non_ads_link" is registered instead of the target": "shopping_tab".
[Additional Notes]:
- Attached is a screen recording of the issue.
| Assignee | ||
Comment 1•2 years ago
•
|
||
We temporarily store URLs as they appear on page like:
https://www.foo.com/search?q=bar&page=shopping
When the user clicks the URL, it's possible for the URL to change and for the pertinent data to be inserted into the redirect URL as a percent escaped string, e.g:
https://www.foo.com/baz?redirect_url=%2Fsearch%3Fq%3Dbar%26page%3Dshopping
So we may need to provide a query parameter to examine in cases when we know redirects or URL manipulation will happen.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 2•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
| bugherder | ||
Comment 5•2 years ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 6•2 years ago
|
||
The patch landed in nightly and beta is affected.
:jteow, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox124towontfix.
For more information, please visit BugBot documentation.
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 7•2 years ago
|
||
The patch adds functionality to Desktop that should fix this issue, but I still need to update search-telemetry-v2 which I'll do in Bug 1884923 and request QA to verify the fix.
Comment 8•2 years ago
|
||
Hey James,
Issue has been tested(on Win 10, Ubuntu and macOS using the latest Nightly build), using RS - Staging as advised. Clicking on a shopping tab now is correctly recorded as such. We can move on with the push to production.
One note that I'd like to make here is that the source of the ping is listed as 'unknow', but that happens without the Staging environment as well, so it might not be related, but worth looking into.
Updated•2 years ago
|
Description
•