Skip to main content

Configure Online Fundraising Forms to Send Data to Donorfy

Set up Online Fundraising forms so donations and supporter data map correctly into Donorfy.

Cristina Gruita avatar
Written by Cristina Gruita
Updated this week

ll referenced values such as campaigns, funds, channels, and descriptions must already exist in Donorfy and must match exactly, including spaces and letter casing. Donorfy does not create missing records automatically.

For general information about creating OF forms, please see their documentation.


Understand How the Integration Works

Online Fundraising forms can include hidden fields that are not visible to donors but are used to pass structured data into Donorfy.

These fields use a Reference value to tell Donorfy where the data should be mapped, and an Options value to supply the data itself.

This approach ensures that donations are attributed correctly to campaigns, funds, departments, and other Donorfy entities.


Use Standard Online Fundraising Fields

The following Online Fundraising default fields automatically map to the Constituent record in Donorfy and do not require any configuration.

  1. First name.

  2. Last name.

  3. Email address.

  4. Phone number.

  5. National ID.

  6. Address line 1.

  7. Address line 2.

  8. City.

  9. Postcode.

  10. Organisation name.

πŸ“ŒNote: These fields should remain visible on donor-facing forms unless there is a specific reason to hide them.


Configure Basic Donorfy Mappings

Basic mappings set properties on Donorfy records at the point they are created. These values persist in Donorfy and are not overwritten by future donations.

πŸ“ŒNote: Fields can be hidden on the form if donors do not need to see them.

Acknowledgement

  1. Set the reference to Donorfy_AcknowledgementId.

  2. Enter the acknowledgement description exactly as shown in Donorfy.

Data maps to: RPI, Transaction.

Bank

  1. Set the reference to Donorfy_BankId.

  2. Enter the bank description exactly as shown in Donorfy.

Data maps to: RPI, Transaction.

Campaign

  1. Set the reference to Donorfy_CampaignId.

  2. Enter the campaign name exactly as shown in Donorfy.

Data maps to: RPI, Transaction, RPI Payment, Constituent.

Channel

  1. Set the reference to Donorfy_ChannelId.

  2. Enter the channel description exactly as shown in Donorfy.

Data maps to: RPI Payment, Transaction.

Constituent Type

  1. Set the reference to Donorfy_ConstituentType.

  2. Enter the constituent type description exactly as shown in Donorfy.

Data maps to: Constituent.

Collection References

You can store up to five free-text references against the RPI.

  1. Use Donorfy_CollectionReference1 through Donorfy_CollectionReference5.

  2. Enter any text value.

Data maps to: RPI.

Constituent Matching

Providing a constituent ID or number allows Donorfy to match the donation without duplicate detection.

  1. Set the reference to Donorfy_ConstituentId.

  2. Enter the Donorfy constituent ID or number.

This field is intended for operator-assisted forms only and should not be exposed to donors.

Data maps to: Constituent.

Department

  1. Set the reference to Donorfy_DepartmentId.

  2. Enter the department description exactly as shown in Donorfy.

Data maps to: RPI Allocation, Transaction Allocation.

Fund

  1. Set the reference to Donorfy_FundId.

  2. Enter the fund description exactly as shown in Donorfy.

Data maps to: RPI Allocation, Transaction Allocation.

Gender

  1. Set the reference to Donorfy_Gender.

  2. Enter the gender description exactly as shown in Donorfy.

Data maps to: Constituent.

Product

  1. Set the reference to Donorfy_ProductId.

  2. Enter the product description exactly as shown in Donorfy.

Data maps to: RPI Allocation, Transaction Allocation.

Fundraising Page

Adding a fundraising page creates a soft credit and updates the page total.

  1. Set the reference to Donorfy_FundraisingPageId.

  2. Enter the fundraising page entity ID.

Data maps to: Transaction.


Configure Advanced Donorfy Mappings

Advanced mappings allow you to store additional structured or conditional data against donations and constituents.

Custom Fields (RPI)

You can store up to ten custom RPI fields.

  1. Use Donorfy_CustomField1 through Donorfy_CustomField10.

  2. Enter any text value.

Data maps to: RPI.

Custom Fields With Custom Names (RPI)

Custom-named fields are stored in Additional Info.

  1. Set the reference to Donorfy_CustomField_{Name}.

  2. Enter any text value.

Data maps to: RPI.

Custom Fields (Transaction)

You can store up to ten custom transaction fields.

  1. Use Donorfy_CustomPaymentField1 through Donorfy_CustomPaymentField10.

  2. Enter any text value.

Data maps to: Transaction.

Custom Fields With Custom Names (Transaction)

  1. Set the reference to Donorfy_CustomPaymentField_{Name}.

  2. Enter any text value.

Data maps to: Transaction.

Communication Channels

Communication channel fields control consent and preferred channel for new constituents.

  1. Set the reference to Donorfy_Channel_{ChannelName}.

  2. Use Yes, No, On, or Off as the value.

Preferred channel is set using the first β€œYes” value found in this order: Email, Phone, Address.

Data maps to: Constituent.

Communication Purposes

  1. Set the reference to Donorfy_Purpose_{PurposeName}.

  2. Use Yes, No, On, or Off as the value.

Data maps to: Constituent.

Tags (Single)

Apply a single tag using a category and name.

  1. Set the reference to Donorfy_Tag_{TagCategory}_{TagName}.

  2. Use Yes or No as the value.

Data maps to: Constituent.

Tags (Multiple)

Apply one of several tags from the same category.

  1. Set the reference to Donorfy_Tag_{TagCategory}.

  2. Add multiple tag names separated by commas.

Data maps to: Constituent.

⚠️Important:
The Online Fundraising integration is a Professional-only feature. Danish Essential subscribers, please contact us to find out more about upgrading.

Other requirements: the integration only applies to Online Fundraising version 4 and later. Prior versions cannot be integrated.

Did this answer your question?