“Anonymous donor” covers two very different situations, and Altru handles them in different ways. In one, a known person gives and asks you not to publicize it. In the other, money arrives and nobody on staff knows, or is allowed to know, who sent it. Before you change any records, decide which of the two you’re dealing with. Mixing them up is how a private donor’s name ends up on a donor wall, or how one cash envelope turns into a phantom major donor in your reports.
Case 1: You know who gave, but they want privacy
This is the more common one. A member writes a large check and says, “Please don’t list my name.” You still need a real constituent record. Their giving history, household, and tax acknowledgment all depend on it, and if you hide the gift you’ll lose track of a relationship you want to keep.
The work here is in marking the record so that every public-facing output leaves the name out:
- Flag the constituent. Depending on your configuration, Altru may already have an anonymous-giving indicator on the constituent record. If you can’t find one, or you’re not sure it reaches your reports, create a constituent attribute such as “Anonymous – do not publish.” Attributes are easy to query on and hard to miss.
- Decide whether it applies to the person or one gift. Some donors want everything kept private. Others only want one gift kept quiet, like a memorial gift or a campaign pledge. If it’s gift-level, note it on the revenue record as well as the constituent, so a later report doesn’t treat all of their giving as private or all of it as public.
- Set a recognition name. For donor walls and annual report lists, many organizations publish “Anonymous” in place of the name. Store that wording where your recognition list actually pulls from, so nobody has to remember to swap it by hand.
Case 2: Nobody knows who gave
Cash in a donation box, a check with no return address, or a gift passed through an attorney or community foundation that won’t reveal the source. In these cases there’s no person to put on the record.
You have a few reasonable options. Pick one and write it down.
One shared placeholder constituent
Create a single constituent named something unmistakable, such as “Anonymous Donor (Unidentified),” and post every untraceable gift to it. Revenue stays accurate and reconciles cleanly in batches. The downside is that this record will look like your most loyal donor in any top-donor or retention query, so you need to exclude it on purpose (see below).
Record the intermediary as the giver
When a gift comes through a donor-advised fund, foundation, or law firm that knows the donor but won’t say, the cleanest record is often the intermediary itself. That’s the organization that sent the money, and it’s who should get the acknowledgment. If the donor later reveals themselves, you can add a soft credit or a relationship at that point without moving the gift.
One placeholder per recurring anonymous source
Sometimes the same unknown person gives every year: same envelope, same amount, same week. A dedicated placeholder (“Anonymous – annual December envelope”) lets you see that pattern without guessing who it is. Use this sparingly, or you’ll end up with a pile of nameless records nobody can explain.
Whichever option you choose, keep these records free of addresses, emails, and guesses in the notes. “We think this is probably the Hendersons” in a note field defeats the purpose and will eventually turn up in an export.
Guardrails that keep anonymity intact
Usually the original entry is fine. Anonymity breaks later, in queries, mailings, and lists that someone built without the flag in mind. Check these places:
- Recognition and donor lists. Any query that feeds a donor wall, annual report, or event program should filter on your anonymous flag or attribute. Test it with one real anonymous record before you send anything to print.
- Top-donor and retention reports. Exclude placeholder constituents so one shared record doesn’t skew donor counts, average gift, or retention rates. A saved selection of placeholder records makes this a single filter instead of a fresh decision every time.
- Acknowledgments. A privacy-requesting donor still gets a thank-you and tax receipt. An unidentified gift has no one to receive one, so make sure placeholder records have no deliverable address and drop out of acknowledgment runs.
- Exports to other tools. If Altru data flows to an email platform, spreadsheet, or board report, the anonymous flag has to go along with it, or the downstream list has to exclude those records. A field that only exists in Altru doesn’t protect anyone in Mailchimp.
- Duplicate cleanup. When merging records, check for the anonymous flag first. A merge that keeps the wrong record’s settings can quietly remove a donor’s privacy flag.
Confirming what your database supports
Altru databases differ in which fields, attributes, and recognition settings are turned on. Before you settle on a method, try it in a sandbox or on a test constituent. Post a gift, run your recognition query, run an acknowledgment, and see where the name shows up. If you can’t tell whether a built-in anonymous indicator affects a particular report, ask Blackbaud support rather than assuming it does. Then add a short note to your gift-entry procedures so whoever is batching next season handles it the same way.
Quick answers
Should an anonymous gift still count toward campaign totals?
Yes. Anonymity limits who sees the name, not whether the money counts. Keep the revenue on a real or placeholder record so totals reconcile.
What if an “anonymous” donor later wants credit?
With a privacy flag, just remove the flag. With a placeholder, you’ll need to decide whether to move the gift to their real record or add a soft credit. Make that call with your finance team, since moving revenue can affect closed periods.
