Experiments and remote config
Every experiment the server serves from
GET /api/v1/config.
Changes here are data, not a release: clients pick them up on their
next config fetch, including iOS and Android builds already
installed on people's phones. Assignment itself happens on the
client, so the config payload is identical for every caller and the
server never sees a device id on that path.
All experiments
Loading.
The exposure counts in this table are distinct devices in
experiment_exposures, the keyed table
the current beacons write. The home
experiment's historical readout comes from
marketing_pageviews.variant instead,
which carries weeks of history that predates that table, so its row
here can read as no exposures while its results panel shows
thousands. The results panel names its own source.