Page MenuHomePhabricator

Get Started Notification Experiment - finalize copy
Closed, ResolvedPublic1 Estimated Story Points

Description

User story & summary:

As a newcomer, I want to receive a well-timed and engaging notification that guides me toward my first edit, so I can quickly understand what to do next and feel encouraged to contribute. By receiving clear guidance at the right moment, I will be more likely to take my first editing step and continue participating in Wikipedia.

Background & research:

Hypothesis: If new accounts that have not yet edited receive a supportive notification* with a Suggested Edit recommendation within 24 hours of creating an account, then they will be more likely to activate constructively.
*An Echo notification and an email if the account has an associated email address.


Related tasks:


Update Copy:
  • Copy:
    • main text: "Curious about editing Wikipedia? Your knowledge joins a community reaching millions."
    • button label: "Try suggested edits" (unvaried / as in production) - changed per T398262.
  • Icon: cdxIconLightbulb (unvaried/ as in production)
  • Design mockup:
    • image.png (1×750 px, 133 KB)
Acceptance Criteria:
  • Change notification copy as specified for treatment group

Event Timeline

Based on the conclusion in T393955#10845085, this is possible, but it is going to be a technically risky change, because we are not certain about the job queue behaviour. We will need @Etonkovidova's support on checking how large the delay actually is, and be more-precise-than-usually on the expected behaviour part.

Based on todays backlog refinement, I added two subtasks for meeting the delay requirements. T394957 is needed to make the delay A/B testable, T394958 is to make the actual configuration change.

Based on the conclusion in T393955#10845085, this is possible, but it is going to be a technically risky change, because we are not certain about the job queue behaviour. We will need @Etonkovidova's support on checking how large the delay actually is, and be more-precise-than-usually on the expected behaviour part.

The existing Echo notifications have been tested for delivery timing, for email bundling, and for received/read notification timestamps. The testing for considerations listed in T393955#10845085 will be quite doable.

KStoller-WMF moved this task from Blocked to Up Next (estimated tasks) on the Growth-Team board.
KStoller-WMF renamed this task from Get Started Notification Experiment [Phase 1] to Get Started Notification Experiment - finalize copy.Jun 9 2025, 4:27 PM
KStoller-WMF updated the task description. (Show Details)
KStoller-WMF set the point value for this task to 1.Jun 10 2025, 4:54 PM
KStoller-WMF edited projects, added Growth-Team (Current Sprint); removed Growth-Team.

Change #1159463 had a related patch set uploaded (by Urbanecm; author: Urbanecm):

[mediawiki/extensions/GrowthExperiments@master] feat: Update Get Started notification message for users in the treatment group

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

Change #1159463 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat: Update Get Started notification message for users in the treatment group

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

Checked on testwiki wmf.7 -a question about user_variant: "control"- this variant has the same timing for "Get started notification"? pinging @Urbanecm_WMF

(1) user 69264 (user_registration: 20250625001743') gets variant user_variant: 'get-started-notification'`

  • Get started notification (with updated text: "Curious about...") comes in 48 h

Screenshot 2025-06-27 at 10.34.10 AM.png (654×1 px, 107 KB)

(2) user 69263 (user_registration:20250624235207) gets variant user_variant: "control"

  • Get started notification (old text: "Try a suggested edit...") comes in 48 h

Screenshot 2025-06-27 at 12.18.23 PM.png (580×1 px, 83 KB)

That's...not what should happen. I'll look into this, thanks for reporting @Etonkovidova.

With T398262: Adjustments to Limiting Add Link notification CTA label and icon done and T398233 filed - the scope of the task is done & verified on testwiki wmf.8.
The current copy (from eswiki beta) looks according to the specs:

Screenshot 2025-07-01 at 4.39.35 PM.png (918×1 px, 165 KB)