Ctrlk
Become a Partner
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Designations / Donation Purposes

Designations (donation purposes) can be created and managed through the connector in several ways, depending on your system setup and preferences.

The Project ID Code used in option 1-3 below typically represents a meaningful code or label used as a donation purpose, often already defined in an external system.

The project name and Project ID Code can be identical. Information on creating ID codes in FundraisingBox is available here.

Once configured, the process runs automatically. No further action is required from the FundraisingBox project team, allowing designations and donation purpose mappings to be created and adjusted flexibly.

Option 1: Using an Existing Salesforce Gift Designation

A designation can be linked by directly referencing an existing Gift Designation in Salesforce. To use this option:

  • A Gift Designation has to be created in Salesforce.

  • The Gift Designation ID (retrievable from the Salesforce URL) has to be used as the Project ID Code in FundraisingBox.

  • The Project ID Code is then linked to a project in FundraisingBox.

This project can subsequently be selected as a donation purpose within donation forms.

Option 2: Using a Unique Custom Field in Salesforce

Alternatively, a designation can be mapped using a custom identifier. For this option:

  • A custom field marked as 'unique' has to be created on the Gift Designation object in Salesforce.

  • A new Gift Designation is created and assigned a value in this unique field.

  • The same value is used as the Project ID Code in FundraisingBox.

This allows flexible mapping without relying on Salesforce record IDs.

Option 3: Mapping via 'Donation Purpose' Field

Another approach is to use preconfigured project mappings within FundraisingBox. In this case, the Project ID Code is transferred automatically:

  • into the Gift Transaction (for one-time donations), or

  • into the Gift Commitment (for recurring donations), where all subsequent transactions will carry the same value,

  • or into the Campaign when created via a P2P fundraising campaign.

Each project created in FundraisingBox must be assigned a corresponding Project ID Code.

Option 4: Mapping via Source ID Codes

As an additional option, Source ID Codes (Information on creating ID codes in FundraisingBox is available here) can be used. These are configured in FundraisingBox and assigned to:

  • donation forms, or

  • P2P fundraising campaigns.

The Source ID Code is then automatically transferred:

  • into the Gift Transaction, or

  • into the Gift Commitment (for recurring donations), where all follow-up donations inherit the same value.

After initial setup, this process is fully automated. This allows sources to be managed and adjusted flexibly without further involvement from the FundraisingBox project team.

Option 5: Using Transaction Custom Fields in FundraisingBox

Designations can also be captured using custom fields defined in FundraisingBox. For this option:

  • A transaction custom field must be created in FundraisingBox. Learn here how to configure custom fields in FundraisingBox.

  • The custom field must be activated in the donation form.

The value entered by the donor can then be transferred via the connector and used for designation mapping in Salesforce.

Values from custom fields are automatically written to the corresponding raw data field. Direct mapping to a specific Salesforce field requires commissioning the FundraisingBox project team.

Last updated