1849373 - Update search-telemetry-v2 with cookie banner related selectors for detection and accept/reject engagement

Status: RESOLVED FIXED

(Firefox :: Search, task, P2)

Description

[James Teow [:jteow]]

We'll need to add the queries that correspond to detecting cookie banners search-telemetry-v2.

Comment 1

[Karandeep Lubana [:klubana]]

Attachment: Bug 1849373 - Update search-telemetry-v2 with cookie banner related selectors for detection and accept/reject engagement. r=jteow

Depends on D200862

Comment 2

[Karandeep Lubana [:klubana]]

When utilizing the search-telemetry-v2 data, we need to pay close attention to ad impression components in the logs. For instance, in scenarios where a cookie banner is present, you should observe a log entry similar to:

• Cookie Banner Presence: Counting ad: { type: “cookie_banner”, ads_visible: 1, ads_hidden: 0, ads_loaded: 1 }

This entry signifies the detection and counting of a cookie banner as part of ad impressions.
It is also important to observe that cookie banner is only listed in ad impressions on pages where it is actually loaded.

User engagements with the cookie banner, such as clicking accept, reject, or more options, will be distinctly recorded.

• Accepting Cookie Banner: Reported page action: { target: “cookie_banner”, action: “clicked_accept” }
• Rejecting Cookie Banner: Reported page action: { target: “cookie_banner”, action: “clicked_reject” }
• Exploring More Options: Reported page action: { target: “cookie_banner”, action: “clicked_more_options” }

It is essential that these interactions are accurately reflected in the logs, demonstrating the users' decisions regarding cookie settings.
On pages that do not load a cookie banner, there should be no ad impressions related to the cookie banner logged. Moreover, Upon the user selecting one of the three options (accept, reject, more options) in the cookie banner, it should not register as an abandonment action in the telemetry.
On older builds, you should expect that cookie_banner is present on ad_impression but no engagement event will be recorded for clicking on any of the options.
Note that these updates are not exclusive to Google but also extend to Bing and Ecosia, ensuring a consistent approach across different search engines.

Comment 3

[Cristian Baica [:cbaica], Release Desktop QA]

Tested the cookie banner ad_impressions for Google, Bing and Ecosia using RS-Staging. Apart from bug 1887662, no other issues were found.
The testing coverage can be viewed here.
If the Ecosia bug is not that impactful, we might consider pushing the cookie banner ad impression to PROD.

Comment 4

[James Teow [:jteow]]

Thank you Cristian.

I think we can gain insight from the changes commited to production.

I'm going to recommend not including the Ecosia changes because if it only sometimes works (locally it works for me but clearly in QA it doesn't work at all), it could give very inaccurate data.