Careers
Part of Donor acquisition: judging a channel by retained donors, consent and capacity
Where donor acquisition plans quietly go wrong, and the fix
Donor acquisition plans quietly go wrong when campaign assets drift from strategy, so trace each failure, fix every asset it touched, and retest before scaling.
What to take away
- Diagnose donor acquisition by the control that failed, not the symptom a donor saw.
- Most failures are one of fourdefinition drift, claim gap, handoff break, false success.
- Preserve the old value and trace the correction through every asset, report and public statement.
- Retest the same defect under normal work before you close it or raise budget.
- Give prevention, detection, response and closure different owners where the team allows it.
A failed acquisition campaign rarely announces itself. It shows up as a cost per acquired donor that drifted, a list that stopped growing, or a thank-you letter sent to someone who asked for nothing.
Find the source before you fix the symptom
Start at the number that looks wrong and walk backward. Which list, which gift array, which ad, which appeal produced it? Then walk forward through every asset that number touched.
The four defects below cover most of what a mid-size shop will find. Work the row that matches, and record what you changed.
| Defect | What it looks like | Acceptance test |
|---|
Four donor acquisition defects
Defect
- Definition drift
- Unit changed mid-campaign
- Claim gap
- Promise exceeds program evidence
- Handoff break
- Role or finish unassigned
- False success
- Gross gifts up, net donors down
Looks like
- Definition drift
- Restore versioned definition
- Claim gap
- Correct every affected asset
- Handoff break
- Name owner and retest
- False success
- Pair proxy with retention and cost
Acceptance test
- Definition drift
- Claim gap
- Handoff break
- False success
| Defect | What it looks like | Acceptance test |
|---|---|---|
| Definition drift | A label or threshold quietly changes meaning, so every number built on it now means something else | The definition on file matches the query behind the number, and the number reproduces on a recount |
| Claim gap | A corrected dashboard next to an overclaim still live on a donation page, an ad or a board slide | Every asset that carried the claim is corrected or retired |
| Handoff break | Mail house to CRM, agency to in-house, campaign code to receipt, with no one owning the join | One gift can be followed end to end, from the list it came from to the acknowledgment |
| False success | A target beaten by a changed definition, a weak list or a duplicate rather than better acquisition | The number survives a settled recount and the donors it counted are still giving later |
Definition drift is the quietest. Someone changes "new donor" from first gift to first gift over $25, and every dashboard built on the old definition is now wrong. Nothing errors. The number just means something else.
The fix for definition drift is to restore the written definition, recount, and republish every number built on the old one. Acceptance test: the definition on file matches the query behind the number, and the number reproduces on a recount.
Claim gap. A claim outlives the error it came from: the dashboard is corrected, but the same number is still live on a donation page, in an ad or on a board slide. The fix is to find every asset that repeated the claim and correct or retire it. Acceptance test: no live asset repeats the old claim.
Handoff break. The failure sits between two people or two systems, mail house to CRM, agency to in-house, campaign code to receipt, gift processing to stewardship. Each side believes it did its part, and no one owns the join. The fix is to name one owner for the join, write down what passes between the two sides, and watch a live gift cross it. Acceptance test: one gift can be followed end to end, from the list it came from to the acknowledgment the donor received.
False success. The campaign beats its target for a reason that is not better acquisition: a changed definition, a weak list, a duplicate, a one-time gift. The fix is to hold the result open until duplicates, refunds and definition changes are settled, then look at what happened after the first gift. Acceptance test: the number survives a settled recount, and the donors it counted are still giving later.
Correct the asset, not only the report
When a claim gap is found, the correction must reach everything the claim touched. This includes the following:
- The donation page and every landing page that carries the claim.
- Receipt, confirmation and thank-you emails.
- Paid ads, organic posts and the creative files behind them.
- Appeal letters, call scripts and volunteer talking points.
- Dashboards, board decks, grant reports and press statements.
- Any agency, platform or partner that repeats the number in its own material.
Assets a claim gap touches
- Landing page
- Email
- Receipt insert
- Board slide
- Agency brief
Work in the order a donor meets the asset: the page where the gift is made first, then the receipt, then the follow-up email, then the ad or appeal that brought the gift, then the internal reports and outward statements that repeat the claim. Verify each one against the corrected source and note who checked it and when. Finish by rerunning the original query; if the corrected number does not reproduce, the gap is still open.
The FTC guidance for marketers using reviews covers fake feedback, selective requests, conditioned incentives, hidden relationships and paid ranking. Those tests apply when you name a provider, quote a beneficiary, or compare your results to another organization's.
Keep the operating boundary visible
Mission, beneficiary dignity, donor intent, and program evidence all sit inside the review.
Fundraising cost, consent and stewardship also sit inside the review. The working file should show the approved scope, exclusions, version, owner and decision date.
Buying software is part of this. The CISA software acquisition fact sheet points buyers toward development practice, supply-chain exposure, deployment and vulnerability management. Add those checks to the purchase record. They inform the decision; they do not approve it.
Test the result before you scale
- Use a defined population and a stated comparison basis.
- Track net acquired donors and later retention alongside cost and quality.
- Observe one normal path and one failure path.
- Preserve claims, inputs, versions and decisions.
- Record uncertainty and the explanations you rejected.
- Set a stop rule and a next review date.
Worked example: tracing one defect
A shop finds cost per acquired donor up 40% quarter over quarter. The ad account looks fine.
| Field | Test applied | Result recorded |
|---|---|---|
| Case | Population, date and responsible reviewer | Fall appeal, 1 Aug to 30 Sep, reviewed by the development lead |
| Method | Follow the defect back to source, then forward to every affected asset | Gift array changed on 12 Aug; old array still live in two emails |
| Outcome | Effect on net acquired donors and later retention, with cost and quality | Net acquired donors flat; average gift down; retention not yet measurable |
| Escalation | Stop if channels are judged on gross gifts without cost or refunds | Stop rule set; correction owner named; review date 15 Nov |
The fix was not the ad. It was the gift array, and then the two emails nobody had re-checked.
The same order applies here: confirm the gift array is where the change started, correct the two emails that repeated it, then rerun the same segment before anyone raises budget.
Common questions
What is the first decision in a donor acquisition review?
Name the owner, the audience, the outcome and the evidence that would stop the work. Without a stop condition, a review becomes a status update.
How long should a correction stay open?
Until the corrected path and a recurrence test both pass. A corrected report with an untested path will fail again the next time someone runs the same campaign.
What should a team avoid?
Judging channels on gross gifts without cost or refunds. When an error reaches a public statement, preserve the record and correct the statement where it appeared.
Does this replace legal or tax review?
No. Receipting, consent and cross-border giving rules vary by jurisdiction. In the United States the IRS sets what a charitable receipt must show and what a Form 990 reports, while state charity officials handle registration and solicitation rules. Name the authority that applies, then take the question to a qualified charity lawyer.
