Closed Bug 1485437 Opened 3 years ago Closed 2 years ago

Reverse Bucketing for CFR telemetry in Release channel

Categories

(Firefox :: Messaging System, enhancement, P3)

60 Branch
enhancement

Tracking

()

RESOLVED INVALID

People

(Reporter: tspurway, Unassigned)

References

(Blocks 1 open bug)

Details

Let's make sure we are anonymizing the telemetry from CFR by using a 'reverse bucketing' approach.  Here we will throw out the message_id on impression pings (which identifies which addon is referenced), and replace it with a bucket_id, which for this experiment will be "CFR_BUCKET_M1".  

This will ensure that all impression telemetry from the experiment will not exfiltrate browser history.
Severity: normal → enhancement
Priority: -- → P3
If channel === release and the user is NOT in an experiment cohort:
- we will replace message_id with bucket_id
- will use impression_id instead of client_id

For other channels and users in the experiment cohort, we can still send message_id and client_id
Component: Activity Streams: Newtab → Messaging System
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.