Growth/Personalized first day/Structured tasks/Add a link

Wikimedia Foundation projects Add a link Suggest potential wikilinks as easy edits for newcomers Group: Growth Start: 2020-04-06 Team members: Gergő Tisza (software engineer), Benoît Evellin (community relations specialist), Elena Tonkovidova (QA engineer), Kosta Harlan (software engineer), Morten Warncke-Wang (data analyst), Rita Ho (senior user experience designer), Max Binder (coach) Backlog: #T252822 Lead: Roan Kattouw Management: Marcella Florence (engineering), Marshall Miller (product) Updates: Most updates posted here .

This page describes the Growth team's work on the "add a link" structured task, which is a type of structured task that the Growth team offers through the newcomer homepage. This page contains major assets, designs, open questions, and decisions. Most incremental updates on progress will be posted on the general Growth team updates page, with some large or detailed updates posted here.

As of August 2021, the first iteration of this task is deployed to half of all new accounts being created in Arabic, Czech, Vietnamese, Bengali, Polish, French, Russian, Romanian, Hungarian, and Persian Wikipedias. We have analyzed data from the first two weeks of the feature's deployment, and we find that newcomers are making many of these edits, and that they have low revert rates. Learnings from this analysis have led us to make improvements to the feature, and the results are encouraging us to broaden the deployment of the feature to more wikis.

You can see what we are building in these interactive prototypes. Note that because they are prototypes, not all buttons work:

• Mobile
• Desktop

Members of the team presented on the background, algorithm, implementation, and results of this work at Wikimania 2021. See the video here. and the slides here.

Try the feature !

• 2020-01-07: first evaluation of feasibility of link recommendation algorithm
• 2020-02-24: evaluation of improved link recommendation algorithm
• 2020-05-11: community discussion on structured tasks and link recommendations
• 2020-05-29: initial wireframes
• 2020-08-27: backend engineering begins
• 2020-09-07: first round of user testing of mobile designs
• 2020-09-08: call for community discussion on latest designs
• 2020-10-19: second round of user testing of mobile designs
• 2020-10-21: first round of user testing of desktop designs
• 2020-10-29: frontend engineering begins
• 2020-11-02: second round of user testing desktop designs
• 2020-11-10: call for feedback on designs from Arabic, Vietnamese, and Czech communities
• 2021-04-19: added sections on Terminology and Measurement
• 2021-05-10: feature is being tested in production on our four pilot wikis
• 2021-05-27: deployed to half of newcomers on Arabic, Vietnamese, Czech, and Bengali Wikipedias
• 2021-07-21: deployed to half of newcomers on Polish, Russian, French, Romanian, Hungarian, and Persian Wikipedias.
• 2021-07-23: posted analysis from first two weeks of feature's deployment.
• 2021-08-15: presentation at Wikimania about the background, implementation, algorithm, and results.
• 2022-05-20: Completion of Iteration 2 of the feature, which includes improvements based on community feedback and data analysis (see list of improvements on the Add a link "Iteration 2" page.
• 2022-06-19: Publish "add a link" Experiment Analysis
• 2022-08-20: start work to address patroller feedback about structured tasks (T315732)
• 2022-09-02: publish Newcomer task edit type analysis
• 2023-12-31: Almost all Wikipedias now have this task available for newcomers. The exception are a dozen of small wikis where there are not enough articles to activate the algorithm, and English and German Wikipedias.
• Next: deployments to all wikis and work with patrollers to improve their experience dealing with link edits.

Structured tasks are meant to break down editing tasks into step-by-step workflows that make sense for newcomers and make sense on mobile devices. The Growth team believes that introducing these new kinds of editing workflows will allow more new people to begin participating on Wikipedia, some of whom will learn to do more substantial edits and get involved with their communities. After discussing the idea of structured tasks with communities, we decided to build the first structured task: "add a link". This task will use an algorithm to point out words or phrases that may be good wikilinks, and newcomers can accept or reject the suggestions. With this project, we want to gain learnings on these questions:

• Are structured tasks engaging to newcomers?
• Do newcomers succeed with structured tasks on mobile?
• Do they generate valuable edits?
• Do they lead some newcomers to increase their involvement?

After completion of "Add a link" Experiment Analysis, we can conclude that the "add a link" structured task improves outcomes for newcomers over both a control group that did not have access to the Growth features as well as the group that had the unstructured "add links" tasks, particularly when it comes to constructive (non-reverted) edits. The most important points are:

• Newcomers who get the Add a Link structured task are more likely to be activated (i.e. make a constructive first article edit).
• They are also more likely to be retained (i.e. come back and make another constructive article edit on a different day).
• The feature also increases edit volume (i.e. the number of constructive edits made across the first couple weeks), while at the same time improving edit quality (i.e. the likelihood that the newcomer's edits are reverted).

The below is excerpted from the structured tasks page, explaining why we chose to build "add a link" as the first structured task.

The Growth team currently (May 2020) wants to prioritize the "add a link" workflow over the other ones listed in the table above. Although other workflows, such as "copyedit", seem to be more valuable, there are a set of reasons we would want to start first with "add a link":

• In the near term, the most important thing we would want to do first is to prove the concept that "structured tasks" can work. Therefore, we would want to build the simplest one, so that we can deploy to users and gain learnings, without having to invest too much in the first version. If the first version goes well, then we would have the confidence to invest in types of tasks that are more difficult to build.
• "Add a link" seems to be the simplest for us to build because there already exists an algorithm built by the WMF Research team that seems to do a good job of suggesting wikilinks (see the Algorithm section).
• Adding a wikilink doesn't usually require the newcomer to type anything of their own, which we think will make it particularly simple for us to design and build -- and for the newcomer to accomplish.
• Adding a wikilink seems to be a low-risk edit. In other words, the content of an article can't be as compromised through adding links incorrectly as it could through adding references or images incorrectly.

This section contains our current design thinking. To look into the full set of thinking around designs for the "add a link" structured task, see this slideshow, which contains background, user stories, and initial design concepts.

Our designs evolved through several rounds of user tests and iterations. As of December 2020, we have settled on the designs that we'll engineer for the first version of this feature. You can see them in these interactive prototypes. Note that because they are prototypes, not all buttons work:

• Mobile
• Desktop

When we design a feature, we look into similar features in other software platforms outside of the Wikimedia world. These are some highlights from comparative reviews done in preparation for Android’s suggested edits feature, which remain relevant for our project.

• Task types – are divided into five main types: Creating, Rating, Translating,  Verifying content created by others (human or machine), and Fixing content created by others.
• Visual design & layout – incentivizing features (stats, leaderboards, etc) and onboarding is often very visually rich, compared to pared back, simple forms to complete short edits. Gratifying animations often compensate for lack of actual reward.
• Incentives – Most products offered intangible incentives grouped into: Awards and ranking (badges) for achieving set milestones, Personal pride and gratification (stats), or Unlocking features (access rights)
• Users motivations – those with more altruistic motivations (e.g., help others learn) are more likely to be incentivized by intangible incentives than those with self-interested motivations (e.g., career/financial benefits)
• Personalization/Customization – was used in some way on most apps reviewed. The most common customization was via surveys during account creation or before a task; and geolocalization used for system-based personalization.
• Guidance – Almost all products reviewed had at least basic guidance prior to task completion, most commonly introductory ‘tours’. In-context help was also provided in the form of instructional copy, tooltips, step-by-step flows,  as well as offering feedback mechanisms (ask questions, submit feedback)

After organizing our thoughts and doing background research, the first visuals in the design process are "wireframes". These are simply meant to experiment and display some of the ideas we think could work well in a structured task workflow. For full context around these wireframes, see the design brief slideshow.

• 
  Giving more explanation the first time the newcomer uses the workflow than on subsequent times
• 
  Explaining why the task is worth doing
• 
  Teaching concepts through checklists
• 
  Letting users disagree with algorithms and generate useful data in the process
• 
  Encouraging the newcomer to move on to more impactful tasks and learn more
• 
  Providing opportunities to learn the more powerful editing tools
• 
  Guardrails against low-quality contributions
• 
  Rewarding good work

Translate this section

Our team discussed the wireframes from the previous section. We considered what would be best for the newcomers, taking into account the preferences expressed by community members, and thinking about engineering constraints. In August 2020, we took the next step of creating mockups, meant to show in more detail what the feature might look like. These mockups (or similar versions) will be used in team discussions, community discussions, and user tests. One of the most important things we thought about with these mockups is the concern we heard consistently from community members during the discussion: structured tasks may be a good way to introduce newcomers to editing, but we also want to make sure they can find and use the traditional editing interfaces if they are interested.

We have mockups for two different design concepts. We're not necessarily aiming to choose one design concept or the other. Rather, the two concepts are meant to demonstrate different approaches. Our final designs may contain the best elements from both concepts:

• Concept A: the structured task edit takes place in the Visual Editor. The user can see the whole article, and switch out of "recommendation mode" into source or visual editor mode. Less focused on adding the links, but easier access to the visual and source editors.
• Concept B: the structured task edit takes place in its own new area. The user is shown only the paragraph of the article that needs their attention, and can go edit the article if they choose. Fewer distractions from adding links, but more distant access to the visual and source editors.

Please note that the focus in this set of mockups is on the user flow and experience, not on the words and language. Our team will go through a process to determine the best way to write the words in the feature and to explain to the user whether a link should be added.

Static mockups

To view these design concepts, we recommend viewing the full set of slides below.

Interactive prototypes

You can also try out the "interactive prototypes" that we're using for live user tests. These prototypes, for Concept A and for Concept B, show what it might feel like to use "add a link" on mobile. They work on desktop browsers and Android devices, but not iPhones. Note that not everything is clickable -- only the parts of the design that are important for the workflow.

Essential questions

In discussing these designs, our team is hoping for input on a set of essential questions:

1. Should the edit happen at the article (more context)?  Or in a dedicated experience for this type of edit (more focus, but bigger jump to go use the editor)?
2. What if someone wants to edit the link target or text?  Should we prevent it or let them go to a standard editor? Is this the opportunity to teach them about the visual editor?
3. We know it’s essential for us to support newcomers discovering traditional editing tools. But when do we do that? Do we do it during the structured task experience with reminders that the user can go to the editor? Or periodically at completion milestones, like after they finish a certain number of structured tasks?
4. Is "bot" the right term here? What are some other options? "Algorithm", "Computer", "Auto-", "Machine", etc.?"
  What might better help convey that machine recommendations are fallible and the importance of human input?

Background

During the week of September 7, 2020, we used usertesting.com to conduct 10 tests of the mobile interactive prototypes, 5 tests each of Concepts A and B, all in English. By comparing how users interact with the two different approaches at this early stage, we wanted to better understand whether one or the other is better at providing users with good understanding and ability to successfully complete structured tasks, and to set them up for other kinds of editing afterward. Specific questions we wanted to answer were:

• Do users understand how they are improving an article by adding wikilinks?
• Do users seem like they will want to cruise through a feed of link edits?
• Do users understand that they're being given algorithmic suggestions?
• Do users make better considerations on machine-suggested links when they have the full context of the article (like in Concept A)?
• Do users complete tasks more confidently and quickly in a focused UI (like in Concept B)?
• Do users feel like they can progress to other, non-structured tasks?

Key findings

• The users generally were able to exhibit good judgment for adding links. They understood that AI is fallible and that they have to think critically about the suggestions.
• While general understanding of what the task would be ("adding links") was low at first, they understood it well once they actually started doing the task. Understanding in Concept B was marginally lower.
• Concept B was not better at providing focus. The isolation of excerpts in many cases was mistaken for the whole article. There were also many misunderstandings in Concept B about whether the user would be seeing more suggestions for the same term, for the same article, or for different articles.
• Concept A better conveyed expectations on task length than Concept B. But the additional context of a whole article did not appear to be the primary factor of why.
• As participants proceed through several tasks, they become more focused on the specific link text and destination, and less on the article context. This seemed like it could lead to users making weak decisions, and this is a design challenge. This was true for both Concepts A and B.
• Almost every user intuitively knew they could exit from the suggestions and edit the article themselves by tapping the edit pencil.
• All users liked the option to view their edits once they finished, either to verify or admire them.
• “AI” was well understood as a concept and term. People knew the link suggestions came from AI, and generally preferred that term over other suggestions. This does not mean that the term will translate well to other languages.
• Copy and onboarding needs to be succinct and accessible in multiple points. Reading our instructions is important, but users tended not to read closely. This is a design challenge.

Outcome

• We want to build Concept A for mobile, but absorbing some of the best parts of Concept B's design. These are the reasons why:
  • User tests did not show advantages to Concept B.
  • Concept A gives more exposure to rest of editing experience.
  • Concept A will be more easily adapted to an “entry point in reading experience”: in addition to users being able to find tasks in a feed on their homepage, perhaps we could let them check to see if suggestions are available on articles as they read them.
  • Concept A was generally preferred by community members who commented on the designs, with the reason being that it seemed like it would help users understand how editing works in a broader sense.
• We still need to design and test for desktop.

Ideas

The team had these ideas from watching the user tests:

• Should we consider a “sandbox” version of the feature that lets users do a dry run through an article for which we know the “right” and “wrong” answers, and can then teach them along the way?
• Where and when should we put the clear door toward other kinds of editing?  Should we have an explicit moment at the end of the flow that actively invites them copyedit or do another level task?
• It’s hard to explain the rules of adding a link before they try the task, because they don't have context. How might we show them the task a little bit, before they read the rules?
• Perhaps we could onboard the users in stages?  First they learn a few of the rules, then they do some links, then we teach them a few more pointers, then they do more links?
• Should users have a cooling-off period after doing lots of suggestions really fast, where we wait for patrollers to catch up, so we can see if the user has been reverted?

After designing, testing, and deciding on Concept A for mobile users, we moved on to thinking about desktop users. We again have the same question around Concepts A and B. The links below open interactive prototypes of each, which we are using for user testing.

• Concept A: the structured task takes place at the article, in the editor, using some of the existing visual editor components. This gives users greater exposure to the editing context and may make it more likely that they explore other kinds of editing tasks.
• Concept B: the structured task takes place on the newcomer homepage, essentially embedding the compact mobile experience into the page. Because the user doesn't have to leave the page, this may encourage them to complete more edits. They could also see their impact statistics increase as they edit.

We are user testing these designs during the week of October 23. See below for mockups showing the main interaction in each concept.

• 
  Mockup of Concept A
• 
  Mockup of Concept B

Outcome

The results of the desktop user tests led us to decide on Concept A for desktop for many of the same reasons we chose Concept A for mobile. The convenience and speed of Concept B did not outweigh the opportunity for Concept A to expose newcomers to more of the editing experience.

"Add a link" is a feature in which human users interact with an algorithm. As such, it is important that user have a strong understanding that suggestions come from an algorithm and that they should be regarded with skepticism. In other words, we want the users to understand that their role is to evaluate the algorithm's suggestion and not to trust it to much. Terminology (i.e. the words we use to describe the algorithm) play an important role in building that understanding.

At first, we planned to use the terms "artificial intelligence" and "AI" to refer to the algorithm, but we eventually decided to use the term "machine". This may be a practice that gets adopted more broadly as multiple teams build more structured tasks that are backed by algorithms. Below is how we thought about this decision.

Background

As we build experiences that incorporate augmentation, we are thinking about the terminology to use when referring to suggestions that come from automated systems. If possible, we want to make a smart choice at the outset, to minimize changes and confusion later. For instance, we are looking at sentences in the feature like these:

• "Suggested links are machine-generated, and can be incorrect."
• "Links are recommended by machine, and you will decide whether to add them to the article."

Objectives

We want the terms we use to satisfy these objectives.

• Transparency: users should understand where recommendations come from, and we should be being honest with them.
• Human-in-the-loop: users should understand that their contributions improve recommendations in the future.
• Usability: copy should help users complete the tasks, not confuse or burden them with too much information.
• Consistency: we should use the same copy as much as possible to lower cognitive load.

Terms we considered

Term	Strengths	Weaknesses
AI	Well understood in some cultures. Users naturally understand that it can fail.	May not accurately describe all the various augmentation we use. Users may think methods are more sophisticated or opaque than they are. Can be challenging to translate.
Machine	Moderately understood. Wide applicability.	Some users may not understand what we mean / term seems archaic. Unclear how much to trust it.
Computer	Moderately understood. Wide applicability.	Sounds archaic
Algorithm	Well understood. Wide applicability.	Unclear how much to trust it. Different meaning in ML context.
Automated	Total applicability.	So broad that it may not convey much meaning to users.

Methods and findings

• User testing: the Growth team tested "add a link" in English using the terms "artificial intelligence" and "AI". We found that users understood the term well and that English-speaking users understood that they should regard the output of AI with skepticism.
• Experts: we spoke to WMF experts in the fields of artificial intelligence and machine learning. They explained that the link recommendation is not truly "AI", in the way that the term is used in the industry today. They explained that by using that term, we may be over-inflating our work and giving users a false sense of the intelligence of the algorithm. Experts preferred the term "machine", as it would accurately describe the link recommendation algorithm as well as be broad enough to describe almost any other kind of algorithm we might use for structured tasks.
• Multi-lingual community members: we spoke to about seven multilingual colleagues and ambassadors about the terms that would make the most sense in their languages. Not all languages have a short acronym for "AI"; many have long translations. The consensus was that "machine" made good sense in most languages and would be easy to translate.

Result

We are going to use the term "machine" to refer to the link recommendation algorithm, e.g. "Suggested links are machine-generated". See screenshots below to see one of the places where the terminology changed based on this decision.

• 
  Onboarding screen using the term "AI"
• 
  Onboarding screen using the term "machine"

The “add a link” workflow structures the process of adding wikilinks to a Wikipedia article, and assists the user with artificial intelligence to point out the clearest opportunities for adding links.  Our hypothesis with the “add a link” workflow is that such a structured editing experience will lower the barrier to entry and thereby engage more newcomers, and more kinds of newcomers than an unstructured experience.  We further hypothesize that newcomers with the workflow will complete more edits in their first session, and be more likely to return to complete more.

Below are the specific hypotheses we seek to validate. These govern the specifics around which data we'll collect and how we'll analyze it.

1. The "add a link" structured task increases our core metrics of activation, retention, and productivity.
2. “Add a link” edits are more likely to be successful than unstructured suggested edits, meaning that a user completes the task and saves the edit. They are also more likely to be constructive, meaning that the edit was not reverted, than unstructured suggested edits.
3. Users seem to understand this task more than unstructured tasks.
4. Users who start with "add a link" will move on to other kinds of tasks, instead of staying siloed (the latter being a primary community concern).
5. The perceived quality of the link recommendation algorithm will be high, both from the users who make "add a link" edits and the communities who review those edits.
6. Users who get “add a link” and who primarily use/edit wikis on mobile see a larger increase in the effects on retention and productivity relative to desktop users.

A randomly selected half of users who get the Growth features will get "add a link" tasks, and the other randomly selected half will get unstructured link tasks. We prefer to give users maximum exposure to these tasks and will therefore not give these users any copyedit tasks by default. In other words, for the purposes of this experiment, we’ll change the default difficulty filters from “links” and “copyedit” to just “links”. For wikis that don’t have unstructured link tasks, all those users get “add a link” and in that case we’ll exclude that wiki from the experiment.

We plan to continue to have a Control group that does not get access to the Growth features, which is a randomly selected 20% of new registrations.

• Group A: users get “add a link” as their only default task type.
• Group B: users get unstructured link task as their only default task type.
• Group C: control (no Growth features)

The experiment will run for a limited time, most likely between four to eight weeks. In practice the experiment will start with our four pilot wikis.  After two weeks, we will analyze the leading indicators below to decide whether to extend the experiment to the rest of the Growth wikis.

After completion of "Add a link" Experiment Analysis, we can conclude that the "add a link" structured task improves outcomes for newcomers over both a control group that did not have access to the Growth features as well as the group that had the unstructured "add links" tasks, particularly when it comes to constructive (non-reverted) edits. The most important points are:

• Newcomers who get the Add a Link structured task are more likely to be activated (i.e. make a constructive first article edit).
• They are also more likely to be retained (i.e. come back and make another constructive article edit on a different day).
• The feature also increases edit volume (i.e. the number of constructive edits made across the first couple weeks), while at the same time improving edit quality (i.e. the likelihood that the newcomer's edits are reverted).

We are at this point fairly certain that Growth features are not detrimental to the wiki communities. That being said, we also want to be careful when experimenting with new features. Therefore, we define a set of leading indicators that we will keep track of during the early stages of the experiment. Each leading indicator comes with a plan of action in case the defined threshold is reached, so that the team knows what to do.

Indicator	Plan of Action
Revert rate	This suggests that the community finds the Add a Link edits to be unconstructive. If the revert rate for Add a Link is significantly higher than that of unstructured link tasks, we will analyze the reverts in order to understand what causes this increase, then adjust the task in order to reduce the likelihood of edits being reverted.
User rejection rate	This can indicate that we are suggesting a lot of links that are not good matches. If the rejection rate is above 30%, we will QA the link recommendation algorithm and adjust thresholds or make changes to improve the quality of the recommendations.
Task completion rate	This might indicate that there’s an issue with the editing workflow. If the proportion of users who start the Add a Link task and complete it is lower than 75%, we investigate where in the workflow users leave and deploy design changes to enable them to continue.

We collected data on usage of Add a Link from deployment on May 27, 2021 until June 14, 2021. This dataset excluded known test accounts, and does not contain data from users who block event logging (e.g. through their ad blocker).

This analysis categorizes users into one of two categories based on when they registered. Those who registered prior to feature deployment on May 27, 2021 are labelled "pre-deployment", and those who registered after deployment are labelled "post-deployment". We do this because users in the "post-deployment" group are randomly assigned (with 50% probability) into either getting Add a Link or the unstructured link task. Users in the "pre-deployment" group have the unstructured link task replaced by Add a Link. By splitting into these two categories, we're able to make meaningful comparisons between Add a Link and the unstructured link task, for example when it comes to revert rate.

Revert rate: We use edit tags to identify edits and reverts, and reverts have to be done within 48 hours of the edit. The latter is in line with common practices for reverts.

User registration	Task type	N edits	N reverts	Revert rate
Post-deployment	Add a Link	290	28	9.7%
	Unstructured	63	22	34.9%
Pre-deployment	Add a Link	958	49	5.1%

For the post-deployment group, a Chi-squared test of proportions finds the difference in revert rate to be statistically significant (${\displaystyle {\chi }^2=16.5,df=1,p\ll 0.001}$). This means that the threshold described in the leading indicator table is not met.

Rejection rate: We define an "edit session" as reaching the edit summary or skip all dialogue, at which point we count the number of links that were accepted, rejected, or skipped. Users can reach this dialogue multiple times, because we think that choosing to go back and review links again is a reasonable choice.

User registration	N accepted	%	N rejected	%	N skipped	%	N total
Post-deployment	597	72.4	125	15.2	103	12.5	825
Pre-deployment	1,464	65.1	595	26.5	189	8.4	2,248
	2,061	67.1	720	23.4	292	9.5	3,073

The threshold in the leading indicator table was a rejection rate of 30%, and this threshold has not been met.

Over-acceptance rate: This was not part of the original leading indicators, but we ended up checking for it as well in order to understand whether users were clicking "accept" on all the links and saving those edits. We reuse the concept of an "edit session" from the rejection rate analysis, and count the number of users who only have sessions where they accepted all links. In order to understand whether these users make many edits, we measure this for all users as well as for those with five or more edit sessions. In the table below, the "N total" column shows the total number of users with that number of edit sessions, and "N accepted all" the number of users who only have edit sessions where they accepted all suggested links.

User registration		N total	N accepted all	%
Post-deployment	≥1 edit	96	31	32.3
	≥5 edits	6	0	0.0
Pre-deployment	≥1 edit	64	10	15.6
	≥5 edits	19	1	5.3

We find that some users only have sessions where they accepted all links, but these users do not typically continue to make Add a Link edits. Instead, users who make additional edits start rejecting or skipping links as needed.

Task completion rate: We define "starting a task" as having an impression of "machine suggestions mode". In other words, the user is loading the editor with an Add a Link task. "Completing a task" is defined as clicking to save an edit, or confirming that all suggested links were skipped.

User registration	N Started a Task	N Completed 1+ Tasks	%
Post-deployment	178	96	53.9
Pre-deployment	101	64	63.4
	279	160	57.3

The threshold defined in the leading indicator table is "lower than 75%", and this threshold has been met. In this case, we're planning to do follow-up analysis to understand more about the tasks, e.g. if they had a low number of suggested links, or if this happens on specific wikis or platforms.

We've analyzed data on why users reject suggested links, focusing on newcomers to help us understand how they learn what constitutes good links in Wikipedia. In this analysis, we used rejections from January and February 2022, and restricted it to actions made within 7 or 28 days since registration. There was no significant difference in patterns between the two, and the data reported here uses the 28 day window. The data was split by wiki, platform (desktop or mobile) and bucketed by the number of Add a Link edits the user had made. We used a logarithmic bucketing scheme with 2 as the base, because that gives us a fair number of buckets early in a user's life while at the same time being easy to understand since the limits double each time.

Rejection reason counts and percentages by platform.

Platform	Rejection reason	N	%
Desktop	Almost everyone knows what it is	2,732	53.0%
	Linking to wrong article	1,377	26.7%
	Other	688	13.0%
	Text should include more or fewer words	378	7.3%
Mobile	Almost everyone knows what it is	1,835	53.3%
	Linking to wrong article	791	23.0%
	Other	484	14.1%
	Text should include more or fewer words	271	7.9%
	Undefined	62	1.8%

The distribution of these reasons is generally the same across all wikis, platforms, and number of Add a Link edits made. For some combinations of these features, we run into the issue of having few data points available (e.g. because some wikis lean strongly to usage of one platform) and that might result in a somewhat different distribution (e.g. just ones marked "Text should include more or fewer words"). In general, we have a lot of data for users with few edits as that's what most users are.

One thing we do appear to see is that for some wikis the usage of "Other" decreases as the number of Add a Link edits made increases. We interpret this to mean that "Other" might be a catchall/safe category for less experienced users, and that as they become more experienced and confident in labelling a link they'll use a different category.

See this page for an explanation of the link recommendation algorithm and for statistics around its accuracy. In short, we believe that users will experience an accuracy around 75%, meaning that 75% of the suggestions they get should be added. It is possible to tune this number, but the higher the accuracy is, the fewer candidate link we will be able to recommend. After the feature is deployed, we can look at revert rates to get a sense of how to tune that parameter.

For a detailed understanding of how the algorithm functions and is evaluated, see this research paper.

To follow along with engineering progress on the backend "add link" service, please see this page on Wikitech.

Articles are selected based on the topic(s) the use chooses. Then articles with a low ratio of links compared to the number of words are selected. A small amount of randomness was added to it so that not every article suggested look the same. The formula is documented on Phabricator.

On May 27, 2021, we deployed the first iteration of this task to our four pilot wikis: Arabic, Czech, Vietnamese, and Bengali Wikipedias. It is available to half of new accounts, as described above. All accounts created before the deployment will also have the feature available. After two weeks, we will analyze our leading indicators to determine if any quick changes need to be made. After about four weeks, we will use data and community feedback to determine whether and how to deploy the feature to more wikis.

Since the initial deployment to our pilot wikis, the Growth team has gathered extensive community feedback and data about the usage and value of Add a Link. We then used those learnings to make improvements to the feature so that newcomers would have a better experience and experienced editors would see higher quality edits. We have completed the improvements, and communities are now using iteration 2 of Add a Link.

The deployment to all Wikipedias was completed at the end of 2023, with only few wikis missing: German and English as they require specific community engagement, and very small Wikipedias where there is no critical mass to have enough links.