Wikimedia Apps/Team/Android/Private Donor Recognition Experiment

As part of our contributions to 2024/2025 Annual Plan, the Android team will explore various ways to increase the number of donations via touchpoints outside the annual banner and email appeals per platform. This project page documents the Android team’s experimentation related to the Wikimedia Foundation 2024-2025 Annual Plan, specifically the Wiki Experiences 3.2 Key Result.

Summary

Based on feedback and data, our focus is on increasing the number of donations beyond the methods the Foundation has relied upon in the past, specifically the annual banner appeals. We want to show that by investing in more integrated donor experiences, we can sustain our work and expand our impact by providing an alternative to donors and potential donors that are unresponsive to banner appeals.

Our existing donors would like to be recognized for their contributions and receive a tailored approach to engagement. Our current experiences, beyond email, fail to differentiate from existing recurring donors, one time donors, and potential donors.

Additionally we do not associate donor status with user names. We have an opportunity to learn if recognizing current and potential donors for their contributions, much like what we offer editors, would offer value to our users and if it opens the ability for more intentional campaigns thus it is worth investing in a cross platform system.

Background

Wiki Experiences 3: Consumer experience (Reading & Media)

Under the Wikimedia Foundation's Infrastructure Goal, and within the group of objectives focused on Wiki Experiences, is an objective related to improving the experience of consumers:

Wiki Experiences 3: Consumer experience Objective: A new generation of consumers arrives at Wikipedia to discover a preferred destination for discovering, engaging, and building a lasting connection with encyclopedic content.

Wiki Experiences 3.2 (WE3.2) Key Result: 50% increase in the number of donations via touchpoints outside the annual banner and email appeals per platform.

Several Wikimedia Foundation teams are committed to working on projects under the WE3.2 Key Result: Draft_Hypotheses.

Android team hypothesis	Timeline	Phabricator epic
Wiki Experiences 3.2.3: If we update the contributions page in the app to include an active badge for someone that is an app donor and display an inactive state with a prompt to donate for someone that decided not to donate in app, we will learn if this recognition is of value to current donors and encourages behavior of donating for prospective donors, informing if it is worth expanding on the concept of private donor badges or abandoning it.	Oct 1 2024 - December 31, 2024	T376303

Wikimedia Foundation teams are approaching annual planning more iteratively this year, so rather than committing to larger year-long projects, this hypothesis is fairly narrow in scope. This should allow us to learn from a brief experiment and deliver value in smaller increments throughout the year, while also ensuring we have the flexibility to pivot as we learn.

Community

We’re using in-app surveys to collect feedback from app users.

• Donors in France, and Netherlands.

Designs

• 
  Initial screen (Donor)
• 
  Initial screen (Not a donor/unknown)
• 
  Overflow menu
• 
  Logged-out dashboard
• 
  Donor history unknown
• 
  Donor history (donor=yes)
• 
  Logged-in dashboard
• 
  Survey ask

Measurement and Results

How will we know we were successful?

The team is planning to run an experiment for 20 days to evaluate our hypothesis, along with running a survey to understand user satisfaction and feedback. Our experiment groups are Android app donors in the Netherlands and France. We will validate our hypothesis for the experiment groups with the key indicators and guardrails listed below:

Validation

Current and Prospective Donors

• KR 1: 30% Badge and Donor Additions interaction rate
• 1.1 30% CTR to contributions Dashboard page
• 1.2 2% Save changes
• KR 2: 55% of survey respondents reflect desire for permanence (Qualitative)
• KR 3: 50 donations as a result of feature
• Current Donors
• KR 4: 30% of users that click Contributions Dashboard make an update

Prospective Donors

• KR 5: 40 donations from non donors or unknown donors to donors as a result of feature

Guardrails:

• GR 1: 65% of negative sentiments by in-app users of feature
• GR 2: 10 negative comments on talk page by community members from target audience

Curiosities:

• CR 1: Does showing the edit tab to logged out users result in more account activation?
• CR 2: How many times did we guess someone was a donor correctly vs users had to update their status?
• CR 3: Do users convey frustration with sharing their information as opposed to us already having access? (Qualitative)
• CR 4: Is there alternative placement we should consider than the contributions dashboard? (Qualitative)
• CR5: What proportion of users that made updates were Non Donors vs Donors?
• CR6: How many users updated their icon via settings?

After conducting data analysis we will share the results of the experiment on this page, and in partnership with the community determine if there should be further investment and rerelease of content suggestions or if we should scale another hypothesis instead.

Technical Constraints

• Unable to get cross platform donations
• Unable to know insights if users donate via web
• The app cannot know whether the user has made donations in the past, or what amounts they were.
• If the user signs up for a recurring donation through the app, and then later cancels it (which is done outside of the app), the app won't be able to know about it.
• If the user uninstalls and reinstalls the app, or clears the app's data, their local contribution history will be lost.
• If the user logs in on another device, their contribution history will be empty.

Updates

Weekly updates can be found on our main updates page.