Because identifiers can repeat both within and across the source platforms you connect, MoveData will prefix those identifiers with additional information as a safety mechanism.
Raisely
All IDs are prefixed with raisely:
Object | Area | Example | Use |
Contact | Person UUID |
|
|
Campaign (Campaign Records) | Campaign Profile UUID |
|
|
Campaign (Team and Fundraiser Profile records) | Profile UUID |
|
|
Recurring Donation | Subscription UUID |
|
|
Opportunity | Donation UUID |
|
|
Funraisin'
Object | Area | Example | Use |
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 |
|
|
Funraisin': Multiple Sites
If you have connected multiple Funriasin' sites you must ensure a unique prefix is added for each site. You are able to do this under MoveData → Integrations → Edit Integration.
This is because Funraisin' uses sequential identifiers on a per-site basis and thus identifiers can overlap between sites
MoveData will inject your unique prefix into the above structure. For example, if you add the unique prefix
exampleMoveData will use:Contact:
funraisin:example:5478Campaign (Event):
funraisin:example:event:1Campaign (Team or Fundraiser):
funraisin:example:history:2938Etc
Funraisin': Campaigns
If an Event ID is provided, MoveData will create an equivalent campaign which will parent Team and Fundraiser records like My Event → Joe Smith
If an Event ID is not provided, MoveData will parent Team and Fundraiser records under the generic Funraisin' campaign like Funraisin
'→ Susie's Bake Sale
JustGiving
With the exception of campaigns, all IDs are prefixed with justgiving:
Event IDs are prefixed with
justiving:event:Campaign IDs are prefixed with
justgiving:campaign:Page IDs are prefixed with
justgiving:pages:
Object | Area | Example | Use |
Contact | User ID |
|
|
Campaign (Event records) | Event ID |
|
|
Campaign (Campaign records) | Campaign ID |
|
|
Campaign (Neither Campaign nor Event ID provided) |
|
|
|
Campaign (Team and Fundraiser records) | Page ID |
|
|
Recurring Donation | User ID and Recurring Mandate Creation Date |
|
|
Opportunity | Donation ID |
|
|
JustGiving: Campaigns
If an Event ID or Campaign ID is provided, MoveData will create an equivalent campaign which will parent Team and Fundraiser records like London Marathon → Joe Smith Runs London
If an Event ID or Campaign ID is not provided, MoveData will parent Team and Fundraiser records under the generic JustGiving campaign like JustGiving → Susie's Bake Sale
JustGiving: Recurring Donations
JustGiving does not provide an identifier
The identifier used by MoveData can be derived from the
YYYYMMDDvalue of the Recurring Mandate Creation Date (like20140909)This is prefixed with the User ID and an underscore to create a final value )like
53187580_20140909)
Enthuse
All IDs are prefixed with enthuse:
Object | Area | Example | Use |
Contact | Supporter ID |
|
|
Campaign (Enthuse Created Event) | Company ID |
|
|
Campaign (Charity Created Event) | Event Page ID |
|
|
Campaign (Neither Campaign nor Event record provided) |
|
|
|
Campaign (Team and Fundraiser records) | PF ID |
|
|
Recurring Donation | Schedule ID |
|
|
Opportunity | Payment Transaction GUID |
|
|
Enthuse: Campaigns
If an Event ID or Campaign ID is provided, MoveData will create an equivalent campaign which will parent Team and Fundraiser records like London Marathon → Joe Smith Runs London
If an Event ID or Campaign ID is not provided, MoveData will parent Team and Fundraiser records under the generic JustGiving campaign like JustGiving → Susie's Bake Sale
List of Enthuse Company IDs: https://docs.google.com/spreadsheets/d/1amx23I_8kkepA5s0yPNdCnEHQfj8PzXCUBKslcNtnWM/edit#gid=1139107291 (published and maintained by Enthuse)
Grassrootz
With the exception of campaigns, all IDs are prefixed with grassrootz:.
Campaign IDs are prefixed with
grassrootz:campaign:Team IDs are prefixed with
grassrootz:team:Fundraiser IDs are prefixed with
grassrootz:fundraiser:
Object | Area | Example | Use |
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
All IDs are prefixed with tapraise:
Object | Area | Example | Use |
Contact | Person UUID |
|
|
Agreement | Transaction Origin UUID |
|
|
Payment | Transaction UUID |
|
|
Good2Give
All IDs are prefixed with g2g:
Object | Area | Example | Use |
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 |
|
|
Good2Give: Employers and Charity Projects
When deriving values from Employer Name and Charity Project Name, ensure you convert to lowercase and replace spaces with hyphens (
-)If you have Employer Campaigns and Charity Project Campaigns enabled you can derive value by combining the Employer Name and Charity Project Name with a hyphen (
-where[Employer Name]-[Charity Project Name]likegoogle-special-needs)
DoGooder
All IDs are prefixed with dogooder:
Object | Area | Example | Use |
Contact | DoGooder does not have the concept of a Contact ID | N/A | N/A |
Campaign | Campaign ID |
|
|
Action | Action ID |
|
|