@ovasileva this came up in https://phabricator.wikimedia.org/T375712#10240244 - basically @RHo was asking if we could detect clicks to "Exit session" from users. We can but we can't distinguish between a logged in user logging out and a temporary user. Not sure how important this is and whether it should be a considered a blocker for filing a ticket (please also see my concern on T374942#10242904) - we potentially might need tickets for our other schemas if there are other product needs.

In T377590#10242914, @Jdlrobson wrote:

@ovasileva this came up in https://phabricator.wikimedia.org/T375712#10240244 - basically @RHo was asking if we could detect clicks to "Exit session" from users. We can but we can't distinguish between a logged in user logging out and a temporary user. Not sure how important this is and whether it should be a considered a blocker for filing a ticket (please also see my concern on T374942#10242904) - we potentially might need tickets for our other schemas if there are other product needs.

We don't need to, right? The "Exit session" button is only visible for temp accounts. So all that would theoretically be needed is tracking a click to the button?

We would need events for:

• Log-in
• Exit session

This might relate to https://docs.google.com/document/d/1egtrDC7lo8KtOw1spcnupByljdOCfRo5fWESRCu4XqA/edit?tab=t.0

In T377590#10258766, @ovasileva wrote:

We would need events for:

• Log-in
• Exit session

This is not quite right. The issue isnt about adding events for clicks it is about distinguishing temporary accounts from logged in accounts.

The elements are tracked but events will appear with isAnon=false. While this allows us to identify the log in link (as no login link is shown to logged in users) it doesnt alllow us to distinguish "exit session" - as an event for that click will look identical to an event for "logout" for a logged in user.

If we only care about that link, yes we should change its event but that would likely need some other changes - they share code for good reasons. I wouldnt recommend this path.

However this goes deeper than those links - all events for temporary users will look like events for a logged in user so if you want information such as click through rate for temporary account or to compare clicks to say the random button (from s logged in vs temporary account user) you cant get that without an additional schema field.

In T377590#10259253, @Jdlrobson wrote:

In T377590#10258766, @ovasileva wrote:

We would need events for:

• Log-in
• Exit session

This is not quite right. The issue isnt about adding events for clicks it is about distinguishing temporary accounts from logged in accounts.

The elements are tracked but events will appear with isAnon=false. While this allows us to identify the log in link (as no login link is shown to logged in users) it doesnt alllow us to distinguish "exit session" - as an event for that click will look identical to an event for "logout" for a logged in user.

If we only care about that link, yes we should change its event but that would likely need some other changes - they share code for good reasons. I wouldnt recommend this path.

However this goes deeper than those links - all events for temporary users will look like events for a logged in user so if you want information such as click through rate for temporary account or to compare clicks to say the random button (from s logged in vs temporary account user) you cant get that without an additional schema field.

@ovasileva and I spoke earlier today about this and we both wonder if it is possible to filter to temporary users only without additional scheme by using the unique username pattern for temp accounts -- ie. is it possible to show the number of "logout" clicks from logged in user that have a username starting with ~20?

ie. is it possible to show the number of "logout" clicks from logged in user that have a username starting with ~20?

No. Not with the existing schema. We do not log username for privacy reasons.

Change #1084228 had a related patch set uploaded (by Kimberly Sarabia; author: Kimberly Sarabia):

[mediawiki/extensions/WikimediaEvents@master] Adds new field

https://gerrit.wikimedia.org/r/1084228

ksarabia opened https://gitlab.wikimedia.org/repos/data-engineering/schemas-event-secondary/-/merge_requests/20

Adds temp user field in schema

bwang merged https://gitlab.wikimedia.org/repos/data-engineering/schemas-event-secondary/-/merge_requests/20

Adds temp user field in schema

Change #1084228 merged by jenkins-bot:

[mediawiki/extensions/WikimediaEvents@master] Adds new field

https://gerrit.wikimedia.org/r/1084228

The fix is not working. Taking another look.

Change #1087211 had a related patch set uploaded (by Kimberly Sarabia; author: Kimberly Sarabia):

[mediawiki/extensions/WikimediaEvents@master] Adds missing object key

https://gerrit.wikimedia.org/r/1087211

Change #1087211 merged by jenkins-bot:

[mediawiki/extensions/WikimediaEvents@master] Adds missing object key

https://gerrit.wikimedia.org/r/1087211

Test Result - Prod

Status: ✅ PASS
Environment: testwiki
OS: macOS
Browser: Chrome
Device: MS
Emulated Device: NA

Test Artifact(s):

Test Steps

Test Case 1: Verify isTemp Field in Web UI Click Tracking for Temporary Accounts

1. Log in as a Temporary Account user.
2. Perform any UI interaction (e.g., click the logout button).
3. Open Chrome DevTools and go to the Network tab.
4. Filter by events and locate the schema web_ui_actions.
5. ✅ AC1: Confirm that the isTemp field appears in the event data, correctly identifying the user as a temporary account.