The goal of this document is to provide an overview of the GiveGab (GG)-EveryAction (EA) API integration as well as outline the steps that need to be taken to enable this integration.

Overview

The GiveGab-EveryAction API integration syncs donation data over from GiveGab’s platform to EveryAction’s CRM platform. For clients who have this enabled, the data will sync every 30 minutes and will send over data for any donations created in the prior 30 minutes.

Limitations

  • Currently, the GiveGab-EveryAction integration is only available to single nonprofit organizations fundraising on GiveGab, or single organization or higher education Giving Days where one organization is receiving all of the funds.

  • It is advised that organizations using this integration do not allow donors to make super-anonymous donations. Currently, these donations will be anonymized when they are sent to EveryAction's CRM.

Terminology

  • Contacts

    • The contacts data model in EveryAction is equivalent to GiveGab’s users table.

    • This is where donor data will be mapped to in the data sync

  • Contributions

    • The contributions data model in EveryAction is equivalent to GiveGab’s donations table.

    • This is where donation data will be mapped to in the data sync.

  • Source Codes

    • These are used to categorize a contribution.

For detailed documentation on these and other concepts within EveryAction’s API please reference their docs.


Data mappings

CSV column Name

EA Field Name

Notes

Donor Info

FirstName

FirstName

LastName

LastName

Email

Email

Phone

Phone

AddressLine1

AddressLine1

AddressLine2

AddressLine2

City

City

StateOrProvince

StateOrProvince

ZipOrPostal

ZipOrPostal

CountryCode

CountryCode

Contribution Info

N/A

ContributionStatusID

Always the word "Settled"

DonationId

GatewayAccountTransactionID

GiveGab donation id

DateReceived

DateReceived

Amount

Amount

CodeID

CodeID

PaymentTypeID

PaymentTypeID

"Credit Card" for online donations, "Cash" for offline

N/A

Designation

EventId

Custom field

EventName

Custom field

Giving Day title if present, otherwise campaign title

SupportArea

Custom field

P2pId

Custom field

P2pName

Custom field

DonorDisplayName

Custom field

UtmSource

Custom field

UtmMedium

Custom field

UtmCampaign

Custom field

UtmContent

Custom field

UtmTerm

Custom field

TotalFees

Custom field

DonorCoveredFees

Custom field

GivegabDonationType

Custom field

GivegabPaymentMethod

Custom field

StripeAccountId

Custom field


How to enable the GiveGab-EveryAction integration

Below is an outline of what is needed to enable this integration, as well as some suggested timelines for setting this up ahead of your campaign/giving day.

  1. Request an API key

    1. To request an API key, submit a support request through EveryActon's Support Request system outlined here.

    2. When making the request, you will want to ask for the "GiveGab" integration type to be added to your committee.

  2. Securely share the API key and Application Name with GiveGab

    1. Once the API keys are generated, you will need to securely share the API key and “Application” name with GiveGab so that we can enable the integration for that particular partner.

  3. Add source code

    1. Next, you will need to add a source code that matches the GiveGab database name for your giving day (gorges2021) or is the campaign slug for peer-to-peer campaigns being run on GiveGab . If you need help finding your database name or campaign slug, write into the GiveGab Customer Success team via customersuccess@givegab.com or by writing into the blue chat bubble.

  4. Add custom fields to Committee in EveryAction

    1. Once the source code has been added, you will need to add custom fields to your Committee in EveryAction. The custom fields that need to be identified are listed above where the “EA field name” says “Custom Field”.

    2. The custom fields should match the exact formatting of the value in column A of the above chart.

    3. Note that there is a limit of 50 custom fields in EveryAction per Committee. It is not required that we send over any custom fields. At the very least, it would be advisable to send over the payment/financial-related custom fields.

  5. Make a test donation

    1. Once the integration is fully enabled, make a test donation to ensure that the data successfully syncs over to your EA tenant.

Did this answer your question?