Benevity Platform Key Syntax
Identifiers use the prefix benevity:
The Benevity integration processes workplace giving donations. Donors are identified by a slugified version of their email address. MoveData uses the platform code benevity.
| NPSP Object | NPC Object | Identifier | Example | Platform Key Value |
|---|---|---|---|---|
| Contact | Person Account | Email (slugified) | jaboraboraexamplecom |
benevity:jaboraboraexamplecom |
| Account (Employer) | Account (Employer) | Company Name (slug) | acmecorp |
benevity:acmecorp |
| Campaign (top-level) | Campaign (top-level) | — | — | benevity:benevity |
| Opportunity | Gift Transaction | Benevity Transaction ID | 67GHRPAPCD |
benevity:67GHRPAPCD |
| Opportunity (Matched Gift) | Gift Transaction (Matched Gift) | Transaction ID + _matched | 67GHRPAPCD_matched |
benevity:67GHRPAPCD_matched |
Contacts#
Contacts are keyed by a slugified version of the donor's email address (e.g., benevity:jaboraboraexamplecom).
Accounts (employers)#
Accounts are keyed by a slugified version of the company name (e.g., benevity:acmecorp).
Campaign hierarchy#
Campaigns use a single-level structure. All donations are grouped under a generic Benevity campaign (benevity:benevity).
Donations#
Donations are keyed by the Benevity Transaction ID (e.g., benevity:67GHRPAPCD).
Matched gifts#
Matched gift Donations use the original Transaction ID with _matched appended (e.g., benevity:67GHRPAPCD_matched).