Overview
At checkout, a donor can choose to give anonymously. This article covers
what that setting actually controls, and whether it can be synced to
your CRM.
What “anonymous” controls
Checking the “give anonymously” option at checkout hides that donor’s
name and avatar from public-facing displays — things like a
fundraiser’s leaderboard or recent-activity feed, and a checkout’s
donation feed. In those places, the donor’s name is replaced with
“Anonymous” and their avatar is hidden.
This is a donor-identity-privacy setting, not an internal permissions
control. It never hides who made the gift from your own
organization’s staff — anyone with dashboard access can always see the
real donor on every transaction, regardless of whether it was marked
anonymous. There is currently no way to additionally restrict internal
staff visibility into donor identity.
A related behavior worth knowing: this masking applies to the
supporter, not just the one gift. If a donor has ever given
anonymously even once, their name and avatar are masked on every public
display going forward — not only on the specific anonymous transaction.
See Why a Supporter Shows as Anonymous in Recent
Activity
for more on this.
Syncing the anonymous flag to your CRM
The anonymous flag is not included by default in the standard
Salesforce Opportunity field mapping. However, it can be synced if you
want it: your WeGive admin (or WeGive Support) can add a custom field
mapping rule that maps the anonymous flag to a Salesforce field of your
choice. No code change is required on WeGive’s side — it’s a
configuration step, available on request.
If you’d like this mapped to your Salesforce integration, reach out to
WeGive Support with the target Salesforce field you’d like it synced
to.Last modified on October 7, 2026