1) We have [[ https://meta.m.wikimedia.org/wiki/Schema:MobileOptionsTracking | Schema:MobileOptionsTracking ]]. This tracks activity to the beta field (e.g. opt-in and opt-out) and lives inside [[ https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/master/includes/specials/SpecialMobileOptions.php | Special:MobileOptions ]]. It uses server side event logging.
2) We also log opt ins to beta/stable via wfIncrStats (statsd) for `mobile.opt_in_cookie_set` and `mobile.opt_in_cookie_unset`. It lives inside [[ https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/master/includes/MobileContext.php | MobileContext ]]
3) When a user is logged in and opts into beta we record this. This event is logged in preferences (https://phabricator.wikimedia.org/T67079#3815127)
The current implementation of the new form in the `specialpages` branch introduces asynchronous saving via JavaScript. This means it cannot use server side event logging i.e. it breaks #1. If we want to continue using #1 we'll need to create some new client side code to log this. It does not break #2 or #3.
Which of these do we actually need? What can be removed.
= Strawman acceptance criteria
[] I propose we emove all code relating to #1 and decommission the MobileOptionsTracking schema. We will rely on statsd from now on.