Nonprofit fundraising data often knows more about a supporter than any one system can see.
A donor gives through a campaign link, opens three stewardship emails, attends an event with a spouse, later recommends a donor-advised fund grant, and then appears in the CRM under a slightly different name. Each signal may be real. The reporting risk is pretending every connection is equally certain.
That is where a donor identity confidence report helps. It gives fundraising, marketing, and operations teams a practical way to connect donor activity across systems while showing how confident the organization should be in each match.
Why donor identity confidence matters now
Recent sector data makes identity confidence more than a technical cleanup issue. The 2026 M+R Benchmarks Study reported that online revenue rose 15% in 2025, with one-time giving up 17%, monthly revenue up 12%, and DAF revenue up 44%. More revenue flowing through more digital and blended paths means more records to connect.
At the same time, the Fundraising Effectiveness Project reported that donor counts continued to fall even as dollars improved, with overall retention only edging from 43.1% to 43.3%. Giving USA 2026 put total 2025 giving at $617.2 billion, a record total, but many nonprofits still feel the pressure of fewer relationships carrying more revenue.
When donor relationships are more valuable and donor journeys are more fragmented, matching errors become expensive. A false match can credit the wrong campaign, assign the wrong steward, or merge two different supporters into one story. A missed match can make a loyal donor look new, hide DAF influence, or understate the role of stewardship.
What is a donor identity confidence report?
A donor identity confidence report is a dashboard or recurring review that shows how donor records, campaign signals, giving records, and engagement activity have been connected, along with the level of confidence behind each connection.
It does not simply ask, “Did we match this record?” It asks, “How strong is the evidence that these records belong together, and what decisions are safe to make from that match?”
That distinction matters. Some matches are strong enough for reporting automation. Some are strong enough for a fundraiser to review. Some should stay separate until more evidence appears.
The signals worth comparing
Identity confidence usually improves when teams compare several clues instead of relying on one field. Useful signals include:
- Email address: exact email matches are often strong, but shared household emails and forwarded appeals can still create ambiguity.
- Name and household: useful when paired with address, spouse, organization, event registration, or giving history.
- Gift behavior: donation amount, timing, designation, payment method, campaign source, and recurring status can support or challenge a match.
- Engagement activity: email clicks, event attendance, advocacy actions, content downloads, volunteer activity, and stewardship responses.
- Offline context: checks, pledge records, DAF sponsor information, fundraiser notes, and imported event lists.
- Campaign tracking: UTM values, source codes, referral paths, QR links, or appeal IDs that connect the action to a known outreach effort.
No single signal should carry more certainty than it deserves. A matching email address is strong. A matching last name and ZIP code is weaker. A DAF grant with no donor name may be revenue, but it is not automatically attributable to a specific supporter.
The confidence bands to use
The report becomes easier to use when every match falls into a small set of confidence bands. For most teams, four bands are enough.
- Confirmed: the match has strong unique evidence, such as donor ID, exact email, verified CRM link, or staff-confirmed identity.
- Likely: several signals point to the same person or household, but one key identifier is missing or not unique.
- Review needed: the match may be right, but the evidence is partial, conflicting, or high-impact enough to need human judgment.
- Unmatched: the activity cannot yet be connected to a known donor record with useful confidence.
The point is not to make the data sound less useful. The point is to make it safer. A likely match can still inform stewardship planning. A confirmed match can support attribution, ROI reporting, and donor journey analysis with more confidence.
What to include in the dashboard
A donor identity confidence report should be compact enough for a weekly or monthly review. Include the fields that help people act:
- Record type: gift, DAF grant, event attendee, email engagement, form submission, volunteer action, or stewardship note.
- Matched donor or household: the record the activity is currently connected to.
- Confidence band: confirmed, likely, review needed, or unmatched.
- Evidence used: email, name, address, campaign code, gift timing, event registration, CRM ID, or staff confirmation.
- Conflict flag: whether another possible donor record also fits the signal.
- Decision use: safe for stewardship, safe for attribution, safe for merge, or review before use.
- Owner: the person or role responsible for review or correction.
- Resolution outcome: confirmed, separated, merged, assigned to household, or left unmatched.
This turns identity resolution from a hidden data chore into a visible reporting workflow.
Where identity confidence changes fundraising decisions
The first use case is attribution. If a donor clicks an email and later gives through a different path, the team may want to include that email as an assisted touch. But if the email click is tied to a shared household address, the report should show the confidence level before claiming influence.
The second use case is donor stewardship. A first-time online donor may actually be an existing offline supporter. If the match is confirmed, the welcome plan should reflect the existing relationship. If the match is only likely, the team may still send a warm welcome, but hold off on merging records until someone reviews the evidence.
The third use case is DAF and major-gift reporting. A grant may arrive through a sponsor, while the donor relationship lives somewhere else in the CRM. Identity confidence helps the team separate received revenue from donor journey certainty.
The fourth use case is campaign ROI. If campaign response, later giving, and stewardship activity are connected poorly, ROI reporting can reward the wrong source or miss the touches that kept a donor engaged.
How to start without boiling the ocean
Start with one high-value matching problem. Do not try to repair every identity issue in the database at once.
A good first version might focus on DAF grants, event attendees who later give, first-time online donors who may already exist offline, or high-intent email clickers who appear under multiple records.
- Choose the record type. Pick the activity where identity mistakes create real reporting or stewardship risk.
- Define the evidence rules. Decide which fields create confirmed, likely, review-needed, and unmatched status.
- Separate reporting use from merge decisions. A signal may be useful for stewardship before it is safe for a permanent record merge.
- Create a review queue. Show the records that need human judgment, not every record in the system.
- Measure improvement. Track the share of records confirmed, likely, reviewed, corrected, and still unmatched over time.
This is also a useful companion to a UTM data contract, because clean campaign tracking is easier to trust when the donor record behind the action is also confidence-scored. It also strengthens engagement-to-gift lag reporting, where delayed outcomes can be misunderstood if the underlying identity match is weak.
The ReportWerks perspective
Fundraising teams need connected data, but connected data should not flatten uncertainty.
A donor identity confidence report helps teams connect more of the donor journey while preserving the judgment needed for good stewardship, cleaner attribution, and more honest ROI reporting. It gives leaders a better answer than “matched” or “not matched.” It shows which matches are ready for decisions, which ones need review, and where better tracking will improve future reports.
ReportWerks helps nonprofit teams connect fundraising data, campaign tracking, donor engagement, and ROI reporting into decision-ready dashboards. If your reports depend on knowing which supporter did what, identity confidence is one of the most useful layers you can add.
