Closed Bug 1853420 Opened 1 year ago Closed 8 months ago

Investigate sending a product page detection event

Categories

(Firefox :: Shopping, task)

task

Tracking

()

RESOLVED WONTFIX

People

(Reporter: perry.mcmanis, Assigned: perry.mcmanis)

References

Details

As a followup to 1848160, let's discuss (and maybe implement)

Having a counter that we collect on the Metrics ping is useful, but is not the full extent of the data we want.

We want an additional event to go on the Events ping triggered under the same conditions, but is compliant on the exposure telemetry decision brief. As such, this event SHALL NOT be fired unless someone is fully opted in to the Shopping experience.

It also would not contain any information about the product page itself, so no domain or url, product info, category, etc.

Recording exposure events was ruled out as part of the decision brief discussion process, see https://docs.google.com/document/d/1WkEthAFW-avbOxm63AHhdQQF4gwowq3fWoDPt-yYOx0/edit

Essentially: product doesn't need that extra info, so we're not going to gather it. Probably a decision brief, not a bug, would be the right venue to revisit this decision.

Closing as a WONTFIX

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX

(In reply to Perry McManis [:perry.mcmanis] from comment #0)

We want an additional event to go on the Events ping triggered under the same conditions, but is compliant on the exposure telemetry decision brief. As such, this event SHALL NOT be fired unless someone is fully opted in to the Shopping experience.

(In reply to Jared Hirsch [:jhirsch] (he/him) (Needinfo please) from comment #1)

Recording exposure events was ruled out as part of the decision brief discussion process, see https://docs.google.com/document/d/1WkEthAFW-avbOxm63AHhdQQF4gwowq3fWoDPt-yYOx0/edit

The above decision is about collecting this information for both control and treatment in the context of the Shopping experiment. My understanding is that collecting an event for this would be acceptable in the case where customers have opted in to the Shopping experience (and not opted back out). If customers are not in an opted-in state, we must only measure using the counter.

Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

This is targeted for inclusion in 120, where 119 will have the counter productPageVisists

Bruce can you please confirm/deny that the counter will allow you to answer the success metrics we've laid out?

Flags: needinfo?(betling)

Confirming that the counter productPageVisits will be sufficient for 119.

Flags: needinfo?(betling)
Status: REOPENED → RESOLVED
Closed: 1 year ago8 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.