== Background
As part of the work on donor ID and recognition, we want to run an experiment that will present donors with an on-wiki token of appreciation. We have no post-donation retention signal for logged-out donors on mobile web. Once a donor finishes their gift, nothing in subsequent sessions acknowledges that they gave. This experiment runs a three-variant test to find out whether a persistent Donor Thank You badge – and what it does when you tap it – has any effect on 21-day return rates and re-engagement.
Logged-out and mobile only.
PRD: **[[ https://docs.google.com/document/d/1s9YRtV-zHMBSBrTembIodY_P3L86ryFXEkp8Wf60Txo/edit?tab=t.0 | Emotional Recognition: Post-Donation Experience (Lightweight badge interaction) ]]**
Experiment currently lays out a three bucket path (A/B/C) testing:
- A: Control – no badge. User donates but does not get a donor badge.
- B: Plain – badge and plain message. User donates and automatically gets a persistent donor badge on the top right bar. Tapping on it opens the plain thank-you message – similar to the first FR experiment.
- C: Delightful – badge and animation. User donates and automatically gets a persistent donor badge. Tapping on it triggers wiki-hearts plus a short acknowledgement message.
== Goal
Find out whether the badge – and specifically the tap animation – moves 21-day cumulative retention by at least 1% vs. no badge (A) and the plain popover (B). As a secondary question, track whether donors in (C) tap the badge again in later sessions more than those in (B), which would suggest the animation creates a re-engagement habit.
This task encompassed the **technical scoping **of this experiment.
=== Design requirements
UI designs & workflows to be refined during this phase in collaboration with Design.
[[ https://www.figma.com/design/pkG9ssCFmdzKWp8aYQ8VRe/donor-recognition?node-id=105-19655&t=EhlOWdji724SRosY-4 | Figma Designs of A/B/C treatment ]]
=== Engineering requirements
- Clarifying where experiment is going to live
- What are pre-requisites:
-- Provide workflow diagram for all three buckets.
-- Setup TestKitchen experiment
- What are different requirements for groups:
-- A (Control): 0 engineering need.
-- B & C commonalities:
--- Take first FR experiment as orientation point.
--- Where does experiment code live
--- Clarify handling of sticker location (menu item, absolute positioned item)
---
-- B (Plain):
-- C (Delightful):
--- Provide animation (with randomization character, e.g. heart colors)
--- Hide this badge: Codex component or custom?
==== Instrumentation spec
https://docs.google.com/spreadsheets/d/1NYyinpkV3dswcamBJjLx0AW8P3KzefQyhD85VITIp7U/edit?gid=1635536298#gid=1635536298
---
=== Acceptance criteria
- [x] UI designs have been reviewed by an engineer
- [] Phabricator tasks for this experiment have been created (and ideally estimated).
- [] Workflow diagram can be handed to analyst in order to create an instrumentation plan.