Page MenuHomePhabricator

Emailability: basic measurement
Closed, DeclinedPublic

Description

We have decided that we will not be implementing controlled A/B tests to measure the changes we will be making for this emailability initiative. That's because of the effort required around running experiments, because we intend to make the sort of changes that we don't expect to have negative impacts, and because increasing emailability is not a core goal of our team.

Instead, we want to do some basic longitudinal tracking. We want to know:

  • Number of accounts created, by day, during the weeks surrounding the change.
  • Percent of users adding emails on Special:CreateAccount during the few weeks leading up to the change.
  • Percent of users adding emails on Special:CreateAccount during the few weeks after the change.
  • Percent of users verifying their emails during the few weeks leading up to the change.
  • Percent of users verifying their emails during the few weeks after to the change.

All of this should be split by platform (desktop/mobile) and wiki (Czech/Korean/Vietnamese).

We may also want to remove (or otherwise account for) users who add email addresses via the welcome survey or help panel features.

Event Timeline

JTannerWMF moved this task from Q1 2019-20 to Q2 2019-20 on the Growth-Team board.

Our team has decided that we will not be working on this project during Q4. Moving it to the next fiscal year.

nettrom_WMF triaged this task as Medium priority.Apr 3 2019, 5:10 PM
nettrom_WMF moved this task from Triage to Backlog on the Product-Analytics board.

@nettrom_WMF @MMiller_WMF is this task still needed? It's currently in our backlog, wondering if it needs to be moved or declined.

@kzimmerman -- this is an analysis task that is part of a project, "Emailability", that we have not prioritized but may want to prioritize in the future. I don't think the task should be closed, but perhaps there is a better place to keep it?

nettrom_WMF claimed this task.
nettrom_WMF moved this task from Backlog to Icebox on the Product-Analytics board.

@nettrom_WMF: Per emails from Sep18 and Oct20 and https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup , I am resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!). Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task. Please claim this task again when you plan to work on it (via Add Action...Assign / Claim in the dropdown menu) - it would be welcome. Thanks for your understanding!