Page MenuHomePhabricator

Account Creation CTA experiment: handle experience after login for treatment group
Closed, DeclinedPublic

Description

Background

Tapping on Log in will take the user to the existing login flow. After successfully logging in, they'll be opted into the ReadingLists beta feature, they are brought back to the article page.

For "reader" users:

  • Skip the RL onboarding popover for the save button
  • Skip the pulsating dot for dashboard

For non-reader users:

  • Skip all RL popovers
  • Show a popover indicating where the watchstar has moved

User story

If I choose to log into an existing Wikipedia account, I am taken to the standard login page. After logging in, I am taken back to the article and I understand where the watchstar went.

Design requirements

Figma file

{F74837076}


Requirements

Technical requirements

  • The returnto URL parameter can be added to the login link in the dialog to bring the user back to the article page.
  • If the experiment runs during the beta feature phase, the user will need to be opted into the beta feature

Acceptance criteria

  • On mobile web, for the treatment group, after logging in, the user will be brought back to the article page they saved
  • If the experiment runs during the beta feature phase, the user will be opted into the beta feature
  • For non-reader users, popover indicating where the watchstar has moved will be displayed
  • No other popovers will be shown
  • Users in the control group or outside the experiment will not see the bookmark button nor the notice about the watchstar.

BDD

FEATURE: a non-logged mobile user in a treatment group clicks the Login in in the

Scenario 1: a user logs in as a user with previously enabled "Saved pages" beta feature

Given a user with enabled "Saved pages" option logs in after clicking Login in the Save pages CTA dialog
When a user is returned to a page where the Save pages CTA dialog was shown
Then a user doesn't see the RL onboarding popover for the save button
And a user doesn't see the pulsating dot for dashboard

Scenario 2: a user logs in as a user with NOT previously enabled "Saved pages" beta feature

Given a user with NOT enabled "Saved pages" option logs in after clicking the Login in button on the Save pages CTA dialog
When a user is returned to a page where the Save pages CTA dialog was shown
Then a user doesn't see RL popovers
And a user sees a popover indicating where the watchstar has moved

Scenario 3: (a comparison scenario for the Login button in the CTA Watch star dialog) a user in control group logs in via CTA in the Watch start dialog
Note: the was added for the case when a user upon login might be enrolled into Saved pages beta feature.

Given a user logs in via the Login button in the Watch star CTA
When a user is returned to a page where the Watch star CTA was displayed
Then a user sees the Watch star
And a user is able to click on the Watch star to add an article to a Watchlist

Test Steps

  • run the scenarios above
  • check for a temp user
  • document the steps in the scenarios in the comments to this task

Communication criteria

n/a

Rollback plan

If there's an issue with this work we'd likely need to revert the patch showing the bookmark button to the treatment group (T422157) to disable the entire experimental UI, or turn the experiment off in TestKitchen.

This task was created by Version 1.0.0 of the Reader Experience team task template using phabulous.

Event Timeline

AnneT added a subscriber: Sneha.

hey @HFan-WMF and @Sneha, there's some disagreement between the description in the parent task T421999 and the figma file about what should happen when a user in the treatment group logs in. Specifically, should they see:

  • The popover indicating where they can view their reading list
  • The popover indicating that the watchstar has moved

If y'all talk abut this next week while I'm on vacation, I'd greatly appreciate if one of you could update this task accordingly. Thanks!

Note that I'm not posting this in the estimation channel yet since we haven't finalized the scope

@AnneT I have added a few more paths and edge cases into Figma file which clarifies how pop up should be sequenced. I will sync up with @HFan-WMF and we will align the tickets and figma file this week.

HFan-WMF triaged this task as High priority.Apr 7 2026, 4:57 PM
HFan-WMF moved this task from Incoming to Needs refinement on the Reader Experience Team board.
AnneT renamed this task from Account Creation CTA experiment: handle experience after login to Account Creation CTA experiment: handle experience after login for treatment group.Apr 15 2026, 7:00 PM
AnneT updated the task description. (Show Details)
Testing Summary

@AnneT for review.

Login in after clicking CTA Login button in the Save pages dialog - the table below shows the current behavior on enwiki beta for four groups of users:

  • treatment --> log in --> users who had enabled Saved pages
  • treatment --> log in --> users who don't have Saved pages enabled
  • control --> log in --> users who had enabled Saved pages
  • control --> log in --> users who don't have Saved pages enabled

Findings

  • Scenario 2 (and (2) in the table below) fails - users (not new accounts) won't be automatically enrolled into Saved pages beta feature if they click on the bookmark and then login. The screenshot below shows in red the result of Scenario 2.

Screenshot 2026-05-01 at 10.55.00 AM.png (673×1 px, 144 KB)

  • I reviewed figma design - for the treatment group it shows the case when users without enabled Saved pages would be automatically enrolled upon login
  • the popover about moved Watch star is not shown
User groupWhat icon is clicked??returnto=is presentWhat icon is shown upon loginRL onboarding popovera popover indicating where the watchstar has moved
(1) a user in account-creation-reading-list-cta:treatmentAND when logged in, has Saved pages beta feature enabled previouslybookmark buttonYesbookmark buttonNoN/A
(2) a user in account-creation-reading-list-cta:treatmentAND when logged in, has NO enabled Saved pages beta feature previouslybookmark buttonYesWatch starNoNo
(3) a user account-creation-reading-list-cta:control AND when logged in, has Saved pages beta feature enabled previouslyWatch starYesbookmark buttonN/AN/A
(4) a user in account-creation-reading-list-cta:controlAND when logged in, has NO Saved pages beta feature enabled previouslyWatch starYesWatch starN/AN/A

Per Elena's testing results, we are ok with leaving this in its current state. For existing users who log into their account when they see the bookmark button while logged out (in treatment group), we will NOT opt them into the beta, and they will just maintain their access to the watchstar button.

While this may be confusing for Readers who previously hold accounts, we hope to avoid any confusion that might be caused for moderators and patrollers who may depend on the watchstar button frequently on mobile web, if we automatically opt them into the reading list beta (when it's unclear that by logging in via the bookmark, it would result in the position of their watch button being moved).