Background
We would like to be able to serve AMC to both logged-in and logged-out users with and without JS enabled. The priority of this is as follows:
Low: non-JS logged-out users
Medium: JS logged-out users, non-JS logged-in users
High: JS logged-in users
Questions to answer:
- How difficult is it to serve the treatment and preserve the setting across wikis and sessions for the user groups mentioned above?
- How would this be done?
- How difficult is it to instrument the opt-in button for the user groups mentioned above? (Probably needs to use EventLogging in order to enable the data analysis planned for T210660: [EPIC] AMC Metrics .)
- How would this be done?
Additional questions
- Is there a way to store information on the client side for all wikis? (probably not)
- Do we know how large the non-JS, 100+ edit / month audience is?
- Do we know how large the advanced logged-out audience is?
- How do we pass AMC opt-in to the special pages?
Notes
Notes:
Traffic / caching concerns for:
- anon non-JS
No traffic / caching concerns for:
- logged in JS / non-JS
- anon JS
Idea: Combine mobile beta opt-in with AMC opt-in?