Need a way to record experiment information in the serp category ping
Categories
(Firefox :: Search, task, P3)
Tracking
()
People
(Reporter: wstuckey, Assigned: scunnane)
References
Details
(Whiteboard: [sng])
Attachments
(1 file, 1 obsolete file)
We will want a method for including specific experiment information in the SERP category ping. Because the ohttp pings will not include ping_info metadata, which currently contains all experiments a client is enrolled in, we need some way to record that the client is enrolled in a specific experiment & branch.
A possible (maybe) path would be a boolean nimbus variable that turned on experiment logging for the experiment that sets the value.
Comment 1•3 months ago
|
||
We'll need a bit more investigation around ensuring we can get the experiment stub and branch names.
Also might be worth a Privacy review to ensure that this isn't a fingerprinting vector.
Updated•3 months ago
|
Assignee | ||
Updated•1 month ago
|
Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 3•28 days ago
|
||
For the record, there are Glean APIs for setting (but not getting) the experiments
block, and their are Nimbus APIs for getting. See https://bugzilla.mozilla.org/show_bug.cgi?id=1868676 for example usage, namely https://searchfox.org/mozilla-central/rev/1f5e1875cbfd5d4b1bfa27ca54832f62dd19589e/toolkit/components/nimbus/lib/ExperimentStore.sys.mjs#293.
Assignee | ||
Comment 4•28 days ago
|
||
Very helpful - thanks for the clarification, Nick.
Assignee | ||
Comment 5•20 days ago
|
||
Assignee | ||
Comment 6•18 days ago
|
||
Wil, for this patch I'm now planning to allow the single experiment to be specified via the Nimbus config, within the recipe JSON in the Experimenter UI. So for a given feature object, you'd ensure that the following key-value pairs appear:
"featureId": "search",
"value": {
"targetExperiment": "dummy-experiment"
}
Then the following info would come back as a new Glean object metric added to the custom SERP categorization ping:
{
slug: "dummy-experiment",
isActive: true,
branch: "control"
}
Is this what you have in mind?
Assignee | ||
Comment 8•11 days ago
|
||
Updated•11 days ago
|
Description
•