OneCause and DonorDock Integration

OneCause is an online fundraising and event platform built for nonprofit organizations. It supports fundraising activities such as online giving, events, mobile bidding, auctions, peer-to-peer fundraising, ticketing, sponsorships, and more.

The OneCause integration automatically brings fundraising information from OneCause into DonorDock, keeping supporter and gift information together in your CRM without manual imports.

The integration is one-way from OneCause to DonorDock. Changes made in DonorDock are not sent back to OneCause.

Connect OneCause to DonorDock

Setting up the integration has two main parts:

  1. Obtain your OneCause credentials.

  2. Enter those credentials in DonorDock and configure the integration.

Obtain your OneCause credentials

You will need two values from OneCause:

  • API Token

  • Organization ID

To locate these values:

  1. Log in to your OneCause Fundraising Platform account.

  2. Navigate to Settings.

  3. Select My API Tokens.

  4. Click Generate Token.

    • If an API token has already been created, the button may display Regenerate instead.

  5. Copy your API Token.

  6. Copy your Organization ID.

💡 Treat your API Token like a password. Store it securely and avoid sharing it publicly.

Connect OneCause in DonorDock

Once you have gathered your OneCause information using the steps above, log in to DonorDock and follow the steps below to connect the integration.

  1. Open the Settings menu.

  2. Select Integrations.

  3. Locate OneCause in the Apps section.

  4. Click Connect.

  5. Enter your:

    • OneCause Organization ID

    • OneCause API Token

  6. Turn on Enabled.

  7. Configure any additional settings described below.

  8. Click Save.

Once the integration is saved and enabled, DonorDock begins the initial sync automatically.

After the initial sync, OneCause data is synchronized with DonorDock three times each day. Manual or on-demand syncing is not currently available.

Configure the OneCause Integration

The OneCause integration includes additional options that control what information DonorDock imports.

Sync From

The Sync From setting controls the point DonorDock uses when determining which OneCause information should be reviewed during synchronization.

The first sync retrieves the available OneCause history. After that, DonorDock uses an overlapping sync window so recently updated records are reviewed again. This helps capture transactions that may change after they are initially created, such as a check payment that is later marked paid.

Include Free Items

By default, complimentary or $0 OneCause transactions are not synced to DonorDock as Gifts. If you would like these transactions included, you can enable the Include Free Items setting from the OneCause integration configuration.

To enable this setting:

  1. In DonorDock, navigate to Settings > Integrations.

  2. Select the OneCause integration.

  3. Click the Configure button located below the API Key.

  4. Turn on Include Free Items.

  5. Click Save.

Once enabled, complimentary transactions will sync to DonorDock as $0 Gifts with a Gift Type of Other.

💡 Turning on Include Free Items causes the integration to review the full OneCause history again so previously excluded complimentary transactions can also be added.

Sync Company Supporters

By default, OneCause company supporter records are not synced to DonorDock. If you would like company supporters to be created and maintained as Organization Contacts, you can enable the Sync Company Supporters setting from the OneCause integration configuration.

To enable this setting:

  1. In DonorDock, navigate to Settings > Integrations.

  2. Select the OneCause integration.

  3. Click the Configure button located below the API Key.

  4. Turn on Sync Company Supporters.

  5. Click Save.

Once enabled, OneCause company supporters will sync to DonorDock as Organization Contacts whether or not the company currently has a Gift. Synced company information can include the organization name, point of contact, email address, phone number, and address.

How the OneCause Integration Works

Once connected, information flows from OneCause into DonorDock only.

The current OneCause integration can sync:

  • Individual supporters as Contacts

  • Company supporters as Organization Contacts, when enabled

  • Paid activities and transactions as Gifts

  • OneCause funds as Funds

  • Events and fundraising activity as Campaigns

  • Item donations as In-Kind Gifts

The integration processes supporters before Gifts so DonorDock can first attempt to identify the Contact associated with each transaction.

Individual Supporters

Individual OneCause supporters are synced as DonorDock Contacts.

New Contacts created through the integration receive the OneCause Supporter badge.

How Individual Supporters are matched

When a OneCause supporter is synced, DonorDock searches active Contacts in the following order:

  1. The supporter contains a DonorDock Contact ID that matches an existing Contact.

  2. The OneCause Supporter ID matches the OneCause ID already stored on a Contact whose Source is OneCause.

  3. The supporter's email address matches an Individual Contact's:

    • Primary Email

    • Secondary Email

    • Spouse Email

  4. If no match is found, DonorDock creates a new Individual Contact.

Only active DonorDock Contacts are considered during this matching process.

Individual Supporter field mapping

OneCause Supporter

DonorDock Contact

Supporter ID

OneCause Integration ID

First Name

First Name

Last Name

Last Name

Email

Email

Phone

Main Phone

Address

Address 1

City

City

State

State/Province

Postal Code

Postal Code

Country

Country

OneCause

Source

Active

Status

When updating an existing Contact, OneCause address information is written only when the address, city, state, and postal code are all available.

Company Supporters

When Sync Company Supporters is enabled, company supporters are synced as Organization Contacts.

New Organization Contacts receive the OneCause Supporter badge.

How Company Supporters are matched

DonorDock searches active Contacts in the following order:

  1. A DonorDock Contact ID supplied by OneCause matches an existing Organization Contact or a Contact already associated with that OneCause company.

  2. The OneCause Company ID matches the OneCause ID stored on a Contact whose Source is OneCause.

  3. The OneCause Company Name matches the Organization Name of an existing Organization Contact that is not already connected to another OneCause company.

  4. The Company Name matches an older Individual Contact created by the OneCause integration that does not yet have a OneCause ID.

  5. The company's contact email matches the Primary Email, Secondary Email, or Spouse Email of an Organization Contact that is not already connected to another OneCause company.

  6. If no match is found, DonorDock creates a new Organization Contact.

If the OneCause company does not have a Company Name, the company record is skipped rather than creating an unnamed Organization Contact.

When an existing Organization Contact is matched by company name or email, DonorDock preserves existing information whenever possible. Blank OneCause values do not clear existing DonorDock fields, and information from OneCause is used to fill empty fields on the existing Organization Contact.

Company Supporter field mapping

OneCause Company

DonorDock Organization Contact

Company ID

OneCause Integration ID

Company Name

Organization Name

Contact First Name

First Name

Contact Last Name

Last Name

Contact Email

Email

Contact Phone

Business Phone

Address

Address 1

City

City

State

State/Province

Postal Code

Postal Code

Country

Country

Company

Contact Type = Organization

OneCause

Source

Active

Status

The contact name fields represent the primary point of contact associated with the company in OneCause.

Gifts

Paid OneCause activities are synced as Gifts in DonorDock.

Some activities are intentionally excluded from the Gift sync:

  • Failed payments are not synced.

  • Transactions without a payment type, such as unpaid transactions, are not synced.

  • Activities identified as refunds are skipped.

💡 Refunded OneCause activities do not currently cancel or reverse an existing DonorDock Gift.

How Gifts are matched

DonorDock uses the OneCause purchased item ID to identify Gifts that have already been synced.

If OneCause does not provide a purchased item ID, DonorDock creates an internal identifier using information from the transaction so the same Gift can be recognized during future syncs.

If no existing OneCause Gift is found, a new Gift is created.

How Contacts are matched to Gifts

Contact matching occurs when a new Gift is created or when an existing OneCause Gift does not already have a Contact assigned.

If a Contact has been manually assigned to an existing Gift in DonorDock, the integration does not replace that Contact.

Individual Gift matching

For an individual supporter, DonorDock searches active Contacts in this order:

  1. The OneCause Supporter ID matches the OneCause ID stored on a Contact whose Source is OneCause.

  2. A DonorDock Contact ID supplied by OneCause matches an existing Contact.

  3. The OneCause supporter email matches the Contact's:

    • Primary Email

    • Secondary Email

    • Spouse Email

  4. The supporter's Last Name and Address match the Contact's Last Name and Address 1.

  5. Another received OneCause Gift with the same OneCause transaction ID is already assigned to a Contact.

  6. The supporter's First Name and Last Name match a Contact whose Source is OneCause.

  7. If no match is found, a new Individual Contact is created.

New Contacts created during this process receive the OneCause Supporter badge.

Company Gift matching

For a company supporter, DonorDock searches active Contacts in this order:

  1. The OneCause Company or Supporter ID matches the OneCause ID stored on a Contact whose Source is OneCause.

  2. A DonorDock Contact ID supplied by OneCause matches an existing Contact.

  3. The OneCause Company Name matches an Organization Contact's Organization Name.

  4. Another received OneCause Gift with the same OneCause transaction ID is already assigned to a Contact.

  5. If no match is found, DonorDock creates a new Organization Contact.

The Organization Contact can include the company name, address, point-of-contact name, email, and Business Phone. New Organization Contacts receive the OneCause Supporter badge.

Gift Field Mapping

OneCause Transaction

DonorDock Gift

Purchased Item ID

OneCause Integration ID

Payment Date

Gift Date

Created Date

Gift Date when Payment Date is unavailable

Purchased Item Type

Transaction Type

Payment Type

Gift Type

Check Number

Payment ID for checks

Transaction ID

Payment ID for credit card transactions

Activity Price

Received Amount

Covered Cost

Fee Amount

Supporter Paid Ticket Fee

Fees Covered

Activity Value

Non-Deductible Amount

Recurring Indicator

Is Recurring

Recurring Schedule

Recurrence

Fund

Fund

Activity Origin

Campaign

Integration Description

Payment Description

Payment Notes

Gift Note

OneCause

Source

Paid Transaction

Received Status

When a supporter covers applicable transaction costs, the covered cost is recorded as the Gift's Fee Amount and is also included in the Received Amount.

For Raffle and Fixed Price Item purchases, the full Received Amount is treated as the Gift's Non-Deductible Amount.

Transaction Type

The OneCause purchased item type determines the DonorDock Transaction Type.

OneCause Purchased Item Type

DonorDock Transaction Type

Ticket

Event Ticket

Donation

Donation

Offline Donation

Donation

Recurring Donation

Donation

Sponsorship

Donation

Silent Auction

Donation

Live Auction

Donation

Fixed Price Item

Donation

Raffle

Donation

Misc Charge

Donation

Item Donations are handled separately as In-Kind Gifts rather than through the standard paid activity sync.

Payment Type

The OneCause payment method determines the DonorDock Payment Type.

OneCause Payment Type

DonorDock Payment Type

Cash

Cash

Check

Check

PayPal

PayPal

Card

Credit Card

Google Pay

Credit Card

Apple Pay

Credit Card

ACH

Other

Other

Other

Free

Other

Unrecognized payment type

Credit Card

Funds

OneCause Fund information can be connected to DonorDock Funds as Gifts are synchronized.

Only active DonorDock Funds are considered during matching.

DonorDock searches for a Fund in this order:

  1. A DonorDock Fund ID supplied by OneCause matches an existing Fund.

  2. The OneCause Fund ID matches the OneCause ID stored on a Fund whose Source is OneCause.

  3. The OneCause Fund Name matches an existing DonorDock Fund by name.

  4. If no matching Fund is found and OneCause provides a Fund Name, DonorDock creates a new Fund.

  5. If the transaction contains no Fund information, the Gift's existing Fund is left unchanged.

If an existing Fund is matched by name and does not already have a OneCause ID, DonorDock records the OneCause Fund ID on that Fund for future matching.

Campaigns

OneCause Events and Fundraising activity are connected to DonorDock Campaigns when Gifts are synchronized.

Only active DonorDock Campaigns are considered during matching.

Events

When the OneCause transaction originated from an Event, DonorDock looks for:

  1. A Campaign with the same event name, or

  2. A Campaign matching the DonorDock Campaign ID provided by OneCause.

If no match is found, DonorDock creates a new Campaign using the OneCause event name and sets the Campaign type to Event. The OneCause event start date is used as the Campaign Start Date when available.

Fundraisers

When the transaction originated from a Fundraiser, DonorDock searches for a Campaign with the same name.

If no match is found, DonorDock creates a new Fundraising Campaign.

Other OneCause transactions

For other transaction origins, including recurring donations that are not associated with an Event or Fundraiser, DonorDock assigns the Gift to a Campaign named OneCause. If that Campaign does not already exist, it is created automatically.

In-Kind Gifts

OneCause Item Donations are synced separately from paid transaction activity and become In-Kind Gifts in DonorDock.

Item Donations are retrieved for OneCause Events that have been identified through the integration.

How Contacts are matched to In-Kind Gifts

For an Item Donation, DonorDock searches active Contacts in this order:

  1. The OneCause Donor Supporter ID matches the OneCause ID stored on a Contact whose Source is OneCause.

  2. The donor email matches the Contact's Primary Email, Secondary Email, or Spouse Email.

    • If multiple Contacts share the email address, DonorDock gives preference to the Contact whose name also matches the donor's name.

  3. The donor's full name matches a Contact whose Source is OneCause.

  4. If no match is found, DonorDock creates a new Individual Contact.

The new Contact can include the donor's name, email, phone number, and OneCause ID and receives the OneCause Supporter badge.

In-Kind Gift field mapping

OneCause Item Donation

DonorDock Gift

Item Donation

Gift Type = In Kind

Item Donation

Transaction Type = Donation

Item Value

Soft Credit Amount

Created Date

Gift Date

Item Name and Description

Payment Description

Event Name or Event ID

Campaign

OneCause

Source

Synced Item

Received Status

Item Donation

Gift Tag

The Gift's Received Amount is $0, while the fair market value supplied by OneCause is stored as the Soft Credit Amount.

The Gift receives both the OneCause Transaction and Item Donation Gift Tags.

Gift Tags

Every Gift created from a OneCause paid activity receives the OneCause Transaction Gift Tag.

An additional Gift Tag is created from the OneCause purchased item type. Examples include:

  • Ticket

  • Donation

  • Recurring Donation

  • Sponsorship

  • Silent Auction

  • Live Auction

  • Fixed Price Item

  • Raffle

This allows Gifts to be filtered or reported on using the type of OneCause transaction that created them.

Integration History

You can review OneCause sync activity directly from the integration page.

Navigate to: Settings > Integrations > OneCause

The Integration History records information about OneCause records that were:

  • Added

  • Updated

  • Skipped

  • Unable to sync because of an error

A problem with one record does not necessarily stop the rest of the integration from processing. Records that encounter an error are reviewed again during future syncs.

Was this guide helpful?