Closed Bug 1591880 Opened 5 years ago Closed 5 years ago

Investigate a case where with_ads probe isn't incremented for Google

Categories

(Firefox :: Search, defect, P2)

defect
Points:
3

Tracking

()

RESOLVED FIXED
Firefox 72
Tracking Status
firefox-esr68 72+ fixed
firefox70 + wontfix
firefox71 + wontfix
firefox72 + fixed

People

(Reporter: standard8, Assigned: mikedeboer)

References

Details

Attachments

(5 files, 2 obsolete files)

When investigating bug 1589972, I noticed that on my main development profile, I was not getting the with_ads probe incremented.

It seemed to be that the page only had relative links which were aclk/, which were resolving to urls of https://www.google.com/aclk this did not match the regexp that we have in search telemetry:

/^https:\/\/www\.googleadservices\.com\/(?:pagead\/)?aclk/

Although the with_ads probe wasn't being counted, the https://www.google.com/aclk links were redirecting to https://www.googleadservices.com/aclk and hence were being counted as ad_clicks.

My other profile was loading the page with the links as googleadservices, which is slightly strange. However, we probably do want to investigate updating the regexp (probably at some stage after bug 1589972) is rolled out, to ensure that we get clear data.

[Environment]

71.0a1 20191020214712
72.0a1 20191027212548
Ubuntu 16.04/Windows 10 (doubt it's a OS specific issue)

[Steps;]

Use case scenario for browser.search.with_ads not being initialized, I can reproduce reliably on a new profile and more intermittent on a regular use - didn't catch a clear scenario for which I could reproduce:

  1. Open Firefox with a new profile.
  2. In address bar type Iphone 11.
  3. Check that the search results contain add results.
  4. Open about:telemetry#keyed-scalars-tab_search=browser.search.with_ads
[Actual Result:]

The probe is not initialzed.

[Expected Result:]

about:telemetry#keyed-scalars-tab_search=browser.search.with_ads value should be 1

[Logs:]

72.0a1 https://pastebin.com/grWdvgyg
71.0a1 https://pastebin.com/rpQSNgUX

[Note:]

The behavior for this particular case is the same in both cases: before bug 1589972 fix and after bug 1589972 fix

Thank you for the attachment, I've just looked at it, and similar to what I was seeing with the ad_click probe, this page looks to be https://www.google.com/aclk vs https://www.googleadservices.com/aclk.

I'll check what we want to do for getting this rolled out.

Assignee: nobody → standard8
Status: NEW → ASSIGNED
Points: --- → 2

Mike's currently looking at finishing this off.

Assignee: standard8 → mdeboer
Attachment #9104910 - Attachment is obsolete: true
Attachment #9104911 - Attachment is obsolete: true

Adrian, can you check one of the builds from comment 11 when they're done ready for download? I'm curious to learn if you can still reproduce the bug with the patches applied!

Flags: needinfo?(aflorinescu)

(In reply to Mike de Boer [:mikedeboer] from comment #12)

Adrian, can you check one of the builds from comment 11 when they're done ready for download? I'm curious to learn if you can still reproduce the bug with the patches applied!

Let me redirect this to Cristian, since I'll be off until 11.05.

Flags: needinfo?(aflorinescu) → needinfo?(cristian.comorasu)

Tested the try-build from comment 12 (72.0a1 20191031132313) on Ubuntu 16.04, and from the browser.search.with_ads (about:telemetry#keyed-scalars-tab_search=browser.search.with_ads) point of view, the fix looks fine to me: all searches that returned at least one search results would increment the probe. Also, the pages that didn't contain any ads would not increment the probe.

Flags: needinfo?(cristian.comorasu)

Do you want to land this on m-c now? And, is it something you might want in 70.0.2 (since we are prepping one)

Flags: needinfo?(mdeboer)

(In reply to Liz Henry (:lizzard) from comment #15)

Do you want to land this on m-c now? And, is it something you might want in 70.0.2 (since we are prepping one)

Thanks for asking Liz! We don't need this on 70.0.2, unless it's really no trouble! I mean, obviously it'd be nice to have improved and more reliable metrics earlier, but everything has a cost...

Flags: needinfo?(mdeboer)

(In reply to Liz Henry (:lizzard) from comment #15)

Do you want to land this on m-c now? And, is it something you might want in 70.0.2 (since we are prepping one)

Thanks for asking Liz! We don't need this on 70.0.2, unless it's really no trouble! I mean, obviously it'd be nice to have improved and more reliable metrics earlier, but everything has a cost...

Points: 2 → 3

Liz, please disregard my comment on wanting an uplift potentially, we'd like this to be fully verified on Nightly and ride the trains regularly. Thanks!

Regressions: 1595123
Group: mozilla-employee-confidential

Moving the ESR tracking flag to the next cycle in the event that we want ESR68 to pick up this fix alongside Fx72.

Is this something we want to uplift to ESR68 for the 68.4 release shipping alongside Fx72?

Flags: needinfo?(mdeboer)

(In reply to Ryan VanderMeulen [:RyanVM] from comment #21)

Is this something we want to uplift to ESR68 for the 68.4 release shipping alongside Fx72?

Yeah, that sounds like a good plan. Should I check if the patches graft cleanly?

Flags: needinfo?(mdeboer) → needinfo?(ryanvm)

That would be great (please include bug 1595123 in that testing also).

Flags: needinfo?(ryanvm)

Alright, I was able to successfully transplant the patches from central to esr-68, without any changes. Bug 1595123 also applies cleanly.

Comment on attachment 9105779 [details]
Bug 1591880 - Expand the RegExp to match better and prevent double-counting clicks by ignoring beacon requests. r?Standard8!

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: Improved search telemetry coverage. Much appreciated if this could make it into the next upcoming ESR build!
  • User impact if declined: We would be getting better insight into ad impressions and adclicks for more of our main search partners.
  • Fix Landed on Version: 72
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): The patches transplant cleanly, thus looks like low risk; this bug has caused one regression - bug 1595123 - which I'll also nominate for uplift.
  • String or UUID changes made by this patch: n/a
Attachment #9105779 - Flags: approval-mozilla-esr68?
Attachment #9105780 - Flags: approval-mozilla-esr68?
Attachment #9105781 - Flags: approval-mozilla-esr68?
Attachment #9105782 - Flags: approval-mozilla-esr68?

Comment on attachment 9105779 [details]
Bug 1591880 - Expand the RegExp to match better and prevent double-counting clicks by ignoring beacon requests. r?Standard8!

Search Telemetry improvements. Approved for 68.4esr.

Attachment #9105779 - Flags: approval-mozilla-esr68? → approval-mozilla-esr68+
Attachment #9105780 - Flags: approval-mozilla-esr68? → approval-mozilla-esr68+
Attachment #9105781 - Flags: approval-mozilla-esr68? → approval-mozilla-esr68+
Attachment #9105782 - Flags: approval-mozilla-esr68? → approval-mozilla-esr68+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: