What Is Saved
Each saved identity links one piece of donor evidence to one Planning Center person. The page groups them into four sections:- Bank Account References: check deposit routing and account numbers. Every check import shares these.
- Provider References: a donor reference from one import source, such as a Stripe customer ID. References from different sources never match each other, even when the raw values are identical.
- Confirmed Contacts: a donor’s first and last name plus an email address, or plus a phone number. Port never saves a name, email, or phone on its own, and never saves household names such as “John and Jane Smith”.
- Remote IDs: a provider’s donor ID linked to a Planning Center person.
- Planning Center person ID (links to the person in Planning Center)
- Donor name from the import
- Source (the import provider, “Bank account”, or “Contact”) and identity type
- Value (the reference, contact, or remote ID as imported)
- Provenance
- Last update time
Provenance
- Manual: you chose this person in the match screen. A manual match always wins over automatic ones.
- Auto: saved when an import was approved and the identity pointed to exactly one person in that batch. An automatic match never replaces a manual one.
- Backfill: created from historical imports when saved matches were introduced.
- Ambiguous: more than one donor has claimed this evidence, so Port no longer trusts it for anyone. The row shows “Needs review” instead of a person and assigns nobody.
Ambiguous Identities
Sometimes the same evidence turns out to belong to more than one donor: a provider reuses a reference, a household shares an email address, or one import approves two different people against the same value. Port cannot tell those donors apart any more, so it keeps the row and marks it Ambiguous. An ambiguous row assigns nobody. Donors carrying that evidence go through normal matching, or come to you for review, exactly as if nothing had been saved. Port keeps the row rather than deleting it on purpose: a deleted row records nothing, so the next import would simply learn the identity again and hand the donor back to whoever happened to come first. Two things clear it:- Pick the right person for that donor in the match screen. Your choice replaces the ambiguous row with a confirmed match, and Port reuses it again from then on.
- Select Remove on the row. The evidence goes back to being unknown, so a later import may learn it afresh.
Correcting a Match
If you pick a different person for a donor in the match screen, that choice replaces the saved identity. The old person is not used again. You do not need to remove the old row first.Removing One Identity
Select Remove on a row to delete that single identity. Future imports will match that donor again instead of reusing it. The person’s other saved identities are kept. Removing a confirmed contact also clears the cached Planning Center searches for that name, email, or phone. This stops an old search result from bringing back the old person. If a removal fails partway, the identity stays in place and Port reports the error. Nothing is half-removed, so you can simply try again.Forgetting a Person
Select Forget person on any row to remove everything saved for that Planning Center person: bank account references, provider references, confirmed contacts, and remote IDs. Port also clears that person’s cached Planning Center searches. Use this when a person was merged or deleted in Planning Center, or when many identities point to the wrong person.Resets
- Reset on Bank Account References removes every bank account reference.
- Reset on Provider References removes every provider reference.
- Reset cache on Planning Center Search Cache clears cached search responses only. Saved identities are kept.
- Reset all removes every saved identity, remote ID, and cached search for your organization.