Funraisin Platform Key Syntax
Identifiers use the prefix funraisin: along with additional segments (such as event, history, page, or recurring) depending on the record type.
The Funraisin integration processes donations, fundraiser registrations, and recurring donations via API. MoveData uses the platform code funraisin.
| NPSP Object | NPC Object | Identifier | Example | Platform Key Value |
|---|---|---|---|---|
| Contact | Person Account | Member ID | 5478 |
funraisin:5478 |
| Campaign (Event records) | Campaign (Event records) | Event ID | 1 |
funraisin:event:1 |
| Campaign (no Event ID) | Campaign (no Event ID) | — | — | funraisin:funraisin |
| Campaign (Team and Fundraiser records) | Campaign (Team and Fundraiser records) | History ID | 2938 |
funraisin:history:2938 |
| Campaign (Page records) | Campaign (Page records) | Page ID | 49 |
funraisin:page:49 |
| Recurring Donation | Gift Commitment | Scheduled Donation ID | 29 |
funraisin:recurring:29 |
| Opportunity | Gift Transaction | Donation ID | 860 |
funraisin:860 |
| Opportunity (Sale) | Opportunity (Sale) | Sale ID | 4521 |
funraisin:4521 |
| Opportunity (Raffle Sale) | Opportunity (Raffle Sale) | Raffle Sale ID | 1234 |
funraisin:1234 |
Contacts#
Contacts are identified by the Funraisin Member ID (e.g., funraisin:5478).
Campaign hierarchy#
Campaigns are structured by event. When an Event ID exists, MoveData uses it as the parent and nests teams and fundraisers underneath. When no Event ID exists (such as DIY fundraisers or pages), MoveData groups records under a generic Funraisin campaign (funraisin:funraisin).
Fundraiser and team campaigns use the history: segment prefix with the Funraisin History ID (e.g., funraisin:history:2938). Page campaigns use page: with the Page ID.
Recurring donations#
Recurring donations use the recurring: segment prefix with the Funraisin Scheduled Donation ID (e.g., funraisin:recurring:29).
Donations#
Donations are identified by the Funraisin Donation ID (e.g., funraisin:860).
Sales (sales, raffles, registrations, and ticketing)#
Sales are keyed by the Funraisin Sale ID (e.g., funraisin:4521). Individual order line items are keyed by their Order Item ID (e.g., funraisin:8901). Raffle ticket purchases follow the same pattern using the Raffle Sale ID (e.g., funraisin:1234).
Multiple Funraisin sites
If you connect multiple Funraisin sites, configure a prefix in your Funraisin integration settings. Funraisin uses sequential identifiers per site, so without a prefix, identifiers could overwrite each other. For example, setting the prefix to test produces funraisin:test:event:1 and funraisin:test:history:2938.