Page MenuHomePhabricator

Personalized 48 hour notifications for newcomers: Get Started, Re-engage, and Keep Going
Closed, ResolvedPublic5 Estimated Story Points

Description

User story & summary:

As a newcomer, I want to receive a well-timed and engaging notification, so I can quickly understand what to do next and feel encouraged to contribute. Receiving clear, relevant guidance at the right moment will increase my confidence and likelihood of contributing or continuing to contribute to Wikipedia.

Related epic: T392256: [EPIC] "Get Started" notifications

Details:

Current UX:
Growth currently sends one of two notifications at 48 hours after account creation. These two notifications were developed as part of Growth's Positive Reinforcement project.

  • Keep Going Notification: sent to newcomers who have already completed a Suggested Edit.

image.png (1×750 px, 131 KB)

  • Get Started Notification: sent to newcomers who have NOT completed a Suggested Edit.

image.png (1×750 px, 128 KB)

We hypothesize that if we can make these 48 hour notifications more personalized, they will be more effective in re-engaging newcomers.

Proposed UX:
Segment users more precisely at 48 hours and send one tailored notification per account based on editing behavior:

User SegmentNotificationDestinationDesign
No edits madeGet Started NotificationSpecial:Homepage
image.png (1×750 px, 133 KB)
Edits made, but no Suggested Edits completedRe-engage NotificationSpecial:Homepage
image.png (1×750 px, 135 KB)
Suggested Edit completedKeep Going NotificationSpecial:Homepage/.../openTaskTypeDialog see gerrit
image.png (1×750 px, 133 KB)
Highly active (10+ edits)No notification (avoid distraction)N/AN/A

The "No notification" segmentation is based on past experiment findings (e.g. T342819) indicating that highly active newcomers do not benefit from additional notifications.

Release Plan:
Edge cases to consider:
  • Temp accounts: Temp accounts do note have a Homepage or Suggested Edits and should not receive these notifications
  • Auto-created accounts should not receive these notifications.
  • Display of previously delivered "Get Started" and "Keep Going" notifications.
Acceptance Criteria:

Given I created a new account on a Wikipedia with GrowthExperiments enabled,
When 48 hours have passed,
And I have completed less than 10 edits,
Then I receive a notification that is personalized based on my prior editing (or lack of editing)

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
KStoller-WMF set the point value for this task to 5.Jul 22 2025, 4:01 AM
KStoller-WMF moved this task from Inbox to Up Next (estimated tasks) on the Growth-Team board.
KStoller-WMF attached a referenced file: F65534856: image.png. (Show Details)
KStoller-WMF attached a referenced file: F65534850: image.png. (Show Details)
KStoller-WMF attached a referenced file: F65534838: image.png. (Show Details)
KStoller-WMF attached a referenced file: F65534833: image.png. (Show Details)
KStoller-WMF attached a referenced file: F65534829: image.png. (Show Details)

note for engineers: i'm unsure if this is a regression but the current get started notification includes the copy "Try other edits" from our work on T398262 instead of the original copy which is "Try suggested edits"

image.png (1×3 px, 318 KB)

second note for engineers: for the keep going notification we're intentionally using the same copy "try other edits" from the limit add-a-link notification. we could explicit this in the qqq message for translators.

CleanShot 2025-07-23 at 12.14.54@2x.png (1×1 px, 347 KB)

note for engineers: i'm unsure if this is a regression but the current get started notification includes the copy "Try other edits" from our work on T398262 instead of the original copy which is "Try suggested edits"

image.png (1×3 px, 318 KB)

Yes, that looks like the regression Elena found in T398262#11002681. But my change to fix that had been merged last Tuesday, so I would have expected this to be fixed on testwiki by now. Maybe that needs a bit more investigation.

note for engineers: i'm unsure if this is a regression but the current get started notification includes the copy "Try other edits" from our work on T398262 instead of the original copy which is "Try suggested edits"

image.png (1×3 px, 318 KB)

Yes, that looks like the regression Elena found in T398262#11002681. But my change to fix that had been merged last Tuesday, so I would have expected this to be fixed on testwiki by now. Maybe that needs a bit more investigation.

This should be fixed. I reviewed a more recent notification (see below), and although I'm in the treatment group;which is why the copy says "Curious about editing {{SITENAME}}...."-> the underlying message is essentially the same. Based on that, the regression appears resolved:

Screenshot 2025-07-24 at 12.38.47.png (356×1 px, 49 KB)

@AAlhazwani-WMF , Let me know if you're still seeing the old behavior, and I’ll double-check whether the latest patch has fully propagated.
CC : @Michael

note for engineers: i'm unsure if this is a regression but the current get started notification includes the copy "Try other edits" from our work on T398262 instead of the original copy which is "Try suggested edits"

image.png (1×3 px, 318 KB)

Yes, that looks like the regression Elena found in T398262#11002681. But my change to fix that had been merged last Tuesday, so I would have expected this to be fixed on testwiki by now. Maybe that needs a bit more investigation.

This should be fixed. I reviewed a more recent notification (see below), and although I'm in the treatment group;which is why the copy says "Curious about editing {{SITENAME}}...."-> the underlying message is essentially the same. Based on that, the regression appears resolved:

Screenshot 2025-07-24 at 12.38.47.png (356×1 px, 49 KB)

@AAlhazwani-WMF , Let me know if you're still seeing the old behavior, and I’ll double-check whether the latest patch has fully propagated.
CC : @Michael

thanks @Cyndymediawiksim!

Change #1173899 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: remove GetStarted notification variant

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

Change #1173904 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: rename and retarget GetStarted notification

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

Change #1173899 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: remove GetStarted notification variant

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

Change #1174744 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: new get started notification

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

Minor detail, the copy for the revised keep going notifications says Great progress on your edits in plural but it could be that the user only has made a single suggested edit by the time we send the notification. Great progress on your edit does not sound great but I'm not proficient with language, any suggestions @AAlhazwani-WMF?

Change #1175481 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: update keep going notification copy

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

Minor detail, the copy for the revised keep going notifications says Great progress on your edits in plural but it could be that the user only has made a single suggested edit by the time we send the notification. Great progress on your edit does not sound great but I'm not proficient with language, any suggestions @AAlhazwani-WMF?

@Sgs it's okay if we're not 100% precise here, we can keep it as is. it's unlikely that newcomers may feel confused by the plural, it's more aspirational than anything.

Change #1173904 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: change get started notification audience and copy

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

Change #1175919 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[operations/mediawiki-config@master] [Growth] beta: enable new leveling up notifications

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

Change #1174744 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: send a re-engage notification after 48h

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

Change #1175481 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] LevelingUp: update keep going notification copy

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

Change #1175919 merged by jenkins-bot:

[operations/mediawiki-config@master] [Growth] beta: enable new leveling up notifications

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

Checked on testwiki and beta; timing was also checked.

Updated on Sep 04/2025

User SegmentNotificationDesignenwiki beta
No edits made - get-started-no-editsGet Started Notification - Destination: Special:Homepage
image.png (1×750 px, 133 KB)
Screenshot 2025-08-25 at 5.34.11 PM.png (1×868 px, 84 KB)
Edits made, but no Suggested Edits completedRe-engage Notification Destination::Special:Homepage
image.png (1×750 px, 135 KB)
enwiki beta user 148167
Screenshot 2025-09-04 at 1.13.30 PM.png (852×1 px, 123 KB)
Suggested Edit completed - keep-going-exploringKeep Going Notification Special:Homepage/.../openTaskTypeDialog see gerrit
image.png (1×750 px, 133 KB)
enwiki beta user 148210
Screenshot 2025-09-04 at 1.22.10 PM.png (822×1 px, 120 KB)

Thanks for testing @Etonkovidova! The feature (new copies and target audiences) is only enabled in Beta for now, no testwiki. I was able to get the Get started and Keep going new notification messages, mind that for the Keep going only the second sentence has been modified. I haven't been able to get the Re-engage one, I believe it is because I missed a necessary "job configuration" that exists for Get started/Keep going but not for Re-engage. I'm investigating it now and will get update here once it is solved.

Change #1182583 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[operations/deployment-charts@master] changeprop: add rule for notificationReEngageJob

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

Change #1182583 merged by jenkins-bot:

[operations/deployment-charts@master] changeprop: add rule for notificationReEngageJob

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

Change #1183077 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] fix(LevelingUp notifications): register re-engage notification in echo events

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

Change #1183077 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] fix(LevelingUp notifications): register re-engage notification in echo events

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

Thanks, @Sgs for your help with clarifying the notifications workflow! I've updated my test results in https://phabricator.wikimedia.org/T400118#11117181.

It seems that keep-going-exploring notification has a link label "Make a suggested edit", but in this comment below - "try other edits" should be used (unless it was decided otherwise somewhere else).

second note for engineers: for the keep going notification we're intentionally using the same copy "try other edits" from the limit add-a-link notification. we could explicit this in the qqq message for translators.

CleanShot 2025-07-23 at 12.14.54@2x.png (1×1 px, 347 KB)

Currently, keep-going-exploring notification (it comes to a user who made a suggested edit already) looks like this:

Screenshot 2025-09-04 at 1.22.10 PM.png (822×1 px, 127 KB)

Change #1186485 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] fix(LevelingUp): fix wrong link and secondary button cta text

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

Change #1186485 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] fix(LevelingUp): fix wrong link and secondary button cta text

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

QA notes cc @Edtadros

In order to test this task at least three accounts need to be created, one to test each notification:

  • Get started: create the account and make no edits, wait 48h
  • Re-engage: create the account and make a regular edit, wait 48h
  • Keep going: create the account and make a suggested edit through the module in Special:Homepage, wait 48h

Note: this feature is currently under an A/B test in production including testwiki, that means that when an account is created GE will decide a variant for it, and assign a corresponding notification text for that variant. Which variant the account falls-in is not relevant, but it is important to check that the user got the appropriate notification message for its assigned variant. The text of each variant can be checked in T400047. To check the variant your new account got assigned one can run the following JS snippet in the dev console from any MW page:

> mw.xLab.getAssignments()
// Object { "growthexperiments-get-started-notification": "treatment" }`

the output is a map of experiment => assigned group. Hope this helps!

Thanks @Sgs, I created 3 new users in beta to validate this. Production will be trickier since I will need to coordinate to create three new users and can only test this in testwiki.

@Edtadros is it okay for us to close this task? The epic that this task is under has already been closed out.

@DMburugu - I reviewed the task and closing it as Resolved.