Enthuse Platform Key Syntax
Identifiers use the prefix enthuse:
The Enthuse integration processes donations, recurring schedules, and fundraiser pages via API. MoveData uses the platform code enthuse.
| NPSP Object | NPC Object | Identifier | Example | Platform Key Value |
|---|---|---|---|---|
| Contact | Person Account | Supporter ID | 883591 |
enthuse:883591 |
| Campaign (Event records) | Campaign (Event records) | Company ID | 363 |
enthuse:363 |
| Campaign (Campaign records) | Campaign (Campaign records) | Event Page ID | 20178 |
enthuse:20178 |
| Campaign (no Event/Campaign ID) | Campaign (no Event/Campaign ID) | — | — | enthuse:enthuse |
| Campaign (Team and Fundraiser records) | Campaign (Team and Fundraiser records) | PF ID | 731863 |
enthuse:731863 |
| Recurring Donation | Gift Commitment | Schedule ID | 109375 |
enthuse:109375 |
| Opportunity | Gift Transaction | Payment Transaction GUID | db71c8d5-c5a8-448c-9aee-d7d72c3fcf61 |
enthuse:db71c8d5-c5a8-448c-9aee-d7d72c3fcf61 |
Contacts#
Contacts are identified by the Enthuse Supporter ID (e.g., enthuse:883591).
Campaign hierarchy#
Campaigns are structured by event. When an Event or Campaign ID exists, MoveData uses it as the parent and nests fundraiser pages underneath. When no Event or Campaign ID exists (such as recurring or direct donations), MoveData groups records under a generic Enthuse campaign (enthuse:enthuse).
Recurring donations#
Recurring donations are identified by the Enthuse Schedule ID (e.g., enthuse:109375).
Donations#
Donations are keyed by the Enthuse Payment Transaction GUID (e.g., enthuse:db71c8d5-c5a8-448c-9aee-d7d72c3fcf61).