Identifiers are not always unique within source platforms, and can also repeat between different source platforms. Because of this, the integration will prefix identifiers with additional information as a safety mechanism. To find your identifiers, download the equivalent report from your source platform.
Helpful Tip
Often organisations will have integrations installed in a sandbox before enabling in Production. In this case, you can create a report for the records in your sandbox and view the identifier values and copy across to Production.
Raisely Syntax
Identifiers are prefixed with raisely:
Object | Identifier | Example | Value |
Contact | Person UUID |
|
|
Campaign (Campaign Records) | Campaign Profile UUID |
|
|
Campaign (Organisation, Team and Fundraiser Profile records) | Profile UUID |
|
|
Recurring Donation | Subscription UUID |
|
|
Opportunity | Donation UUID |
|
|
Funraisin' Syntax
Identifiers are prefixed with funraisin: and other information (like event, history) depending on the nature of the record in Funraisin'.
Object | Identifier | Example | Value |
Contact | Member ID |
|
|
Campaign (Event records) | Event ID |
|
|
Campaign (Event ID not provided) |
|
|
|
Campaign (Team and Fundraiser records) | History ID |
|
|
Campaign (Page records) | Page ID |
|
|
Recurring Donation | Scheduled Donation ID |
|
|
Opportunity | Donation ID |
|
|
Note: Funraisin Campaigns
Where an Event ID is provided, the integration will use that event as the parent campaign and nest teams and fundraisers underneath. Where an Event ID is not provided (such as with DIY fundraisers or pages), the integration will parent the records under a generic Funriasin' campaign.
Note: Multiple Funraisin Sites
If you connect multiple Funraisin sites you must ensure a prefix is configured in your Funraisin integration settings. This is because Funraisin uses sequential identifiers on a site-by-site basis and, without prefixing, identifiers could overwrite eachother. If you set up a prefix of test, MoveData will incorporate that prefix into the below structure like funraisin:test:event:1, funraisin:test:history:2938.
JustGiving Syntax
Identifiers are prefixed with justgiving: and other information (like event, pages) depending on the nature of the record in JustGiving.
Object | Identifier | Example | Value |
Contact | User ID |
|
|
Campaign (Event records) | Event ID |
|
|
Campaign (Campaign records) | Campaign ID |
|
|
Campaign (Event / Campaign ID not provided) |
|
|
|
Campaign (Team and Fundraiser records) | Page ID |
|
|
Recurring Donation | User ID and Recurring Mandate Creation Date |
|
|
Opportunity | Donation ID |
|
|
Note: JustGiving Campaigns
Where an Event / Campaign ID is provided, the integration will use that event as the parent campaign and nest teams and fundraisers underneath. Where an Event / Campaign ID is not provided (such as with DIY fundraisers), the integration will parent the records under a generic JustGiving campaign.
Note: JustGiving Recurring Donations
JustGiving does not issue an identifier for recurring donations and as such you need to calculate it yourself. The identifier can be derived from the YYYYMMDD value of the Recurring Mandate Creation Date (like 20250101) which is prefixed with the User ID and underscore (_) to create an identifier like 53187580_20140909.
Enthuse Syntax
Identifiers are prefixed with enthuse:
Object | Identifier | Example | Value |
Contact | Supporter ID |
|
|
Campaign (Event records) | Company ID |
|
|
Campaign (Campaign records) | Event Page ID |
|
|
Campaign (Event / Campaign ID not provided) |
|
|
|
Campaign (Team and Fundraiser records) | PF ID |
|
|
Recurring Donation | Schedule ID |
|
|
Opportunity | Payment Transaction GUID |
|
|
Note: Enthuse Campaigns
Where an Event / Campaign ID is provided, the integration will use that event as the parent campaign and nest teams and fundraisers underneath. Where an Event / Campaign ID is not provided (such as with DIY fundraisers), the integration will parent the records under a generic Enthuse campaign.
Grassrootz Syntax
Identifiers are prefixed with grassrootz: and other information (like campaign, team) depending on the nature of the record in Grassrootz.
Object | Identifier | Example | Value |
Contact | AccountId |
|
|
Campaign (Campaign Records) | Campaign ID |
|
|
Campaign (Team records) | Team ID |
|
|
Campaign (Fundraiser records) | Fundraiser ID |
|
|
Recurring Donation | Subscription ID |
|
|
Opportunity | Donation ID |
|
|
TapRaise Syntax
Identifiers are prefixed with tapraise:
Object | Identifier | Example | Value |
Contact | Person UUID |
|
|
Agreement | Transaction Origin UUID |
|
|
Payment | Transaction UUID |
|
|
Good2Give Syntax
Identifiers are prefixed with g2g:
Object | Identifier | Example | Value |
Contact | Good2Give Donor ID | | |
Account | Employer Name |
|
|
Campaign (Good2Give Parent) |
|
|
|
Campaign (Employer Campaign Enabled) | Employer Name |
|
|
Campaign (Charity Project Campaigns Enabled) | Charity Project Name |
|
|
Campaign (Employer Campaigns and Charity Project Campaigns Enabled) | Employer Name and Charity Project Name |
|
|
Opportunity | Donation Confirmation Number |
|
|
Note: Employer Name and Charity Projects
When deriving values from Employer Name / Charity Project Name, ensure you convert values to lowercase and represent any space () characters with hyphens (-). In the case of Employer and Charity Project campaigns being enabled, combine the Employer Name and Charity Project name with a hyphen like [Employer Name]-[Charity Project Name] / google-special-needs.
DoGooder Syntax
Identifiers are prefixed with dogooder:
Object | Identifier | Example | Value |
Contact | DoGooder does not have the concept of a Contact ID | N/A | N/A |
Campaign | Campaign ID |
|
|
Action | Action ID |
|
|
Note: DoGooder Contacts
DoGooder does not have the concept of a contact identifier. In that scenario, given no identifier is present for the account, the integration can only use your Salesforce Duplicate Rules.