Online Donations Syncing to Salesforce but Missing From Your Totals? Check the Stage
GiveWP and similar tools can land gifts in Salesforce as Pledged — where NPSP rollups and most reports never see them. How to find and fix the invisible donations.
A nonprofit I work with connected their WordPress giving platform to Salesforce, and the sync worked — every test gift appeared in the org within seconds. Weeks later, the questions started. Why didn’t the year-to-date dashboard move? Why did a donor who gave last week show Total Gifts: $0 on their contact record? Why was the first-time donors report empty in a month with obvious first-time donors?
The gifts were all there. They were just invisible to every number the staff actually looked at.
The mechanism
In an NPSP org, a donation is an Opportunity, and an Opportunity has a Stage. NPSP’s rollup fields — Total Gifts, Last Gift Date, Largest Gift, all the numbers on the contact and household — only count Opportunities in a Closed Won stage. So do most of the reports anyone has ever built in the org, because that’s the correct filter for “money we actually received.”
Donation platform integrations, meanwhile, often create gifts in Pledged or another open stage. Sometimes it’s a configurable default nobody set. Sometimes it’s by design: recurring donations commonly sync as NPSP Recurring Donation records whose installments are created as Pledged placeholders, expecting something to close them when each payment actually clears.
Either way the result is the same: real, settled money sitting in an open stage forever. The org’s totals drift further from reality with every online gift, and nobody notices because the gifts are visible when you go looking for them individually. It’s the aggregates that lie.
How to check your org in five minutes
- Make a small test gift through your online form (or find this morning’s real one).
- Open it in Salesforce and look at Stage. If it says Pledged and the card already settled, you have this problem.
- Run an Opportunity report grouped by Stage for the last 90 days. A pile of aging Pledged records that all came from the integration is the signature.
- Check one of those donors’ contact records — if Total Gifts ignores their online giving, the rollups confirm it.
Fixing it
Decide what each stage means, then make the integration honest about it. A one-time card gift that settled is not a pledge — it should land Closed Won at sync time. Check your integration’s stage mapping or default stage setting first; this is often a one-dropdown fix.
Recurring gifts need a closing process. If installments sync as Pledged placeholders, something must close each one when the payment clears — the integration itself, NPSP’s recurring donation automation, or (worst case) a documented manual step. Don’t assume it’s happening: watch one real recurring payment go from charge to Closed Won before you trust it. This is the piece I most often find missing.
Check the integration user’s default record type. If the sync user’s profile defaults to the wrong Opportunity record type, gifts can pick up a record type whose default stage isn’t even in your normal sales path — compounding the invisibility. (Changing a user’s profile or license can quietly reset this.)
Backfill the stuck records. Once new gifts land correctly, close the historical Pledged-but-actually-paid records in bulk — Data Loader or an operator with a list view and patience. Rollups recalculate, dashboards jump to the true number, and someone on staff gets a pleasant shock.
The deeper lesson
Integrations get judged by “did the record show up,” and that’s the wrong test. The right test is: did the number the executive director looks at change? A sync can be technically flawless and operationally wrong. When you wire any giving platform to Salesforce, follow one real dollar all the way from the donor’s card to the dashboard — stage, record type, rollups, and the report the board sees — before calling it done.
I’m Chris Moore — an independent consultant in Henderson, NV. I work with small nonprofits on donation pipelines and Salesforce cleanup, including pro-bono engagements through Catchafire and Taproot. If your totals don’t match what you know came in, get in touch.