GoFundraise Platform Key Syntax
Identifiers use the prefix gofundraise:
The GoFundraise integration processes donations, fundraising page registrations, and event updates via API. All identifiers are numeric GoFundraise IDs. MoveData uses the platform code gofundraise.
| NPSP Object | NPC Object | Identifier | Example | Platform Key Value |
|---|---|---|---|---|
| Contact (Fundraiser) | Person Account (Fundraiser) | GoFundraise User ID | 1540997 |
gofundraise:1540997 |
| Contact (Donor) | Person Account (Donor) | — | — | (no platform key — GoFundraise does not provide a donor ID) |
| Campaign (Event) | Campaign (Event) | Event ID | 17009 |
gofundraise:17009 |
| Campaign (Team records) | Campaign (Team records) | Page ID | 2440617 |
gofundraise:2440617 |
| Campaign (Fundraiser records) | Campaign (Fundraiser records) | Page ID | 2316488 |
gofundraise:2316488 |
| Opportunity | Gift Transaction | TransactionPaymentId:TransactionId | 7910167:15558937 |
gofundraise:7910167:15558937 |
Contacts#
Contacts have two behaviours. MoveData identifies fundraiser contacts by the GoFundraise User ID (e.g., gofundraise:1540997). GoFundraise does not provide an ID for donors, so MoveData matches donor contacts through duplicate rules only.
Campaign hierarchy#
Campaigns are structured by event. Events are the parent campaign (e.g., gofundraise:17009), with teams and individual fundraiser pages nested underneath. All levels are keyed by their GoFundraise numeric ID.
Donations#
Donations are keyed by a composite of TransactionPaymentId:TransactionId (e.g., gofundraise:7910167:15558937).