I did a review of temporary accounts on the beta cluster. In this assessment I am working on the assumption that temporary accounts will only be deployed to wikis where Vector 2022 is the default skin and Minerva is the default skin for anonymous and temporary users.

I don't see any blockers for the pilot from my perspective, but I flagged a few might be blockers from @Niharika @rho or @kostajh 's perspective. @ovasileva suggested we meet to discuss them (will let Olga ping them when we are ready to chat).

Things I noticed during the exercise:

Access to Help:Introduction for temporary users

• Currently anonymous users get a dropdown with links to contributions and USER IP talk page which also provides a link to https://en.wikipedia.org/wiki/Help:Introduction:

With temporary accounts this menu disappears for anons (which we believe is intentional since neither of these pages exist anymore.)

It's worth calling out that upon making an edit, the link to Help:Introduction is lost.

• No confirmation step when clicking "Exit session" ***

As discussed in T375712#10240244 it is easy to exit a session by accidentally clicking "exit session". A confirmation step is proposed. We should clarify if web team's involvement is needed in this.

Analytics needs
In T375712 we discovered that there are some assumed analytics needs for temporary accounts. For example we want to track clicks to "Exit session" which is currently not possible. I created T377590 for the work to do this, but it's not clear to me if this blocks pilot wiki roll out.

The web team was not planning to update all our schemas for temporary account support until there is a product need to measure something. For example our A/B tests schema is not setup for temporary accounts as we are not running an A/B test (and are not sure if we would ever use the existing schema again if we do). As a result, it would be useful to understand exactly what analysis we plan to do post-temporary accounts roll out to make sure web team's schemas are up for the task.
Note: many schemas have not been updated for temporary accounts but I have excluded schemas by team does not maintain - it may be useful to ask similar questions for other schemas with other teams such as language team / language selector schema

Open questions:

• Is click tracking support (T377590) a blocker for roll out to pilot wikis or all wikis?
• The WebClientError schema provides the ability to know how many JavaScript errors are occurring in temporary accounts (as opposed to logged in users). Is this instrumentation a blocker for temporary accounts?
• The ReadingDepth schema tracks reading behaviour e.g. how long they stay on a page. Is this instrumentation a blocker for temporary accounts?
• User scroll behaviour- we track when user scrolls to table of contents, or page title e.g. does the user scroll back to the top of the page. Is this instrumentation needed for temporary accounts?

QuickSurveys
QuickSurveys does not currently support running survey's just for temporary users. It's assumed if this is ever needed that can be added by the team planning to run the survey for this audience.