Guides
How to run a lapsed donor reactivation campaign that isn't spam
A lapsed donor reactivation campaign runs on order, not volume: clean the list, clear consent, then send mail and email stages on their own clocks.
What to take away
- Reactivation starts with a lapse window and a cleaned list, not with a creative concept.
- Stage clocks matter1-2 weeks to segment, 4-6 days to clear consent, 3-4 weeks for a mail wave, 5-7 days for an email series.
- Suppression and consent reconciliation is a blocker. Nothing sends until it clears.
- The failure to watch is the silent burn, where complaint rates climb while delivered volume falls.
- If response drops below your floor, pause and re-segment instead of adding volume.
The short version
A lapsed donor reactivation campaign goes after donors who stopped giving, usually 12 to 36 months after their last gift. The aim is a decision, not a gift. Either they re-engage or you stop spending on them. That rule keeps the campaign from becoming a volume contest.
Order beats creative: a sharp letter to a bad-address list fails, while a plain letter to a clean, well-chosen segment can work.
Teams adding volume to win back lapsed donors usually burn the list faster. To decide which quiet donors deserve retention work, the parts worth your attention separate segments that repay effort from those that do not.
Stage by stage
Each stage has a clock and a gate. Do not start the next stage until the gate is signed off.
| Stage | Typical duration | Output | Gate to pass |
|---|
Reactivation Stages and Gates
- File pull and segmentation1-2 weeks
- Suppression and consent4-6 days
- Message testing1-2 weeks
- Mail wave3-4 weeks
- Email series5-7 days
- Triage and second ask1-2 weeks
- Close and re-segment3-5 days
- Segment and fix the lapse window1 to 2 weeks. Output: a pulled segment and a written lapse window (for example, 12 to 36 months) applied to every record the same way. Gate: a second person confirms the pull matches the written definition.
- Clear consent and build the suppression file4 to 6 days. Output: one merged file covering do-not-contact flags, deceased records, and donors who gave in the last 90 days. Gate: someone other than the person who built it reviews and signs off. Nothing sends until this clears.
- Mail wave3 to 4 weeks. Output: one letter to the mail-eligible segment, on its own calendar, with its own response floor. Gate: the wave is judged only after the full 3 to 4 weeks, and only against that floor.
- Email series5 to 7 days to build, schedule and test; 3 to 5 sends spaced 5 to 10 days apart. Output: the sequence, a logged opt-out path, and a permanent unsubscribe list. Gate: response, complaints and bounces stay inside the floor you set. If response falls below the floor, pause the stage and re-segment instead of adding volume.
The donor reactivation email sequence is its own discipline, and nonprofit email marketing covers cadence and list hygiene in more depth. What matters here is the gate: after three to five asks with no response, the next send costs more in complaints than it can return. Stop the sequence for that record and leave it for a later lapse window.
What has to exist before what
- A lapse definition you can defend. Choose a window, such as 12 to 36 months, and apply it to every record the same way.
- One source of truth for gift dates. If your CRM and your payment processor disagree, fix that before you pull names.
- A suppression file that merges do-not-contact flags, deceased records, and anyone who gave in the last 90 days.
The third item is a blocker. Until that file exists and someone has reviewed it, no mail or email leaves the building. Sending without it invites complaints, and complaints reduce your ability to reach everyone else.
The CAN-SPAM Act sets the duties that apply to the email stages: give every message a clear and conspicuous way to opt out, honor an opt-out within 10 business days, include the sender's valid physical postal address, and keep the from-line and subject line accurate. Apply the same identification and opt-out discipline to reactivation mail that carries an ask, and record every unsubscribe on the suppression file so it holds across all stages.
Prerequisites Before Any Send
- Defensible lapse definition applied uniformly
- One source of truth for gift dates
- Merged suppression and do-not-contact file
- Suppression file reviewed and signed off
Where it stalls
The common stall has a name: the silent burn. It happens when the list carries addresses that are years stale. Bounces and complaints climb, inbox providers throttle the sender, and delivered volume falls week by week.
The cause sits upstream. Someone skipped validation and suppression to save a few days. Dashboards report opens and clicks, so the shrinking denominator stays hidden until a whole wave underperforms. Treat each wave as a small campaign with its own calendar, the way nonprofit fundraising campaigns get planned.
What to do while waiting
Use the dead time to prepare pieces that do not depend on sending.
- Reconcile gift dates between the CRM and the payment processor.
- Build the merged suppression and do-not-contact file.
- Draft acknowledgment language for returning donors and check it against IRS rules.
- Set the response floor that pauses the campaign.
A paused campaign costs a week. A burned sending domain costs a year.
Returning donors expect a receipt, and the substantiation and disclosure rules govern what that receipt has to say. IRS Publication 1771, Charitable Contributions: Substantiation and Disclosure Requirements, is the plain-language version of those rules. Match your acknowledgment language to it before the first wave drops.
Then set the response floor from your own history, not a peer's number: take the response rate of your most recent comparable appeal to the same segment and treat any wave that lands below it as a signal to pause and re-segment rather than send more. nonprofit marketing analytics explains how to choose a threshold that fits the list you have.
