Raisely
J
Written by James Gilray
Updated over a week ago

Integration Summary

Product

Method

Push (Webhooks)

Frequency

Real-Time

Articles

Demonstration Video

Supported Modes

Logic is required to map Raisely notifications to your Salesforce data. To quickly and easily do so we recommend using one of the supported MoveData Extensions.

Fundraising and Donations

Ticketing and Commerce

Forms

Note

  • The Fundraising and Donations Extension is relevant to processing fundraising activity and donation information into Salesforce

  • The Ticketing and Commerce Extension is relevant to processing order information into Salesforce

Setup

Raisely API & Webhooks Adminstration

To set up Raisely you will need a Raisely API Key. To get this:

Next, you will need to create your Raisely Integration in MoveData. To do this, open the MoveData app and select the Integrations tab. Click New Integration and select JustGiving from the list of available integrations. Add a Name and click Save.

MoveData Raisely Configuration Screen

Enter your Raisely API Key. Referring to the Raisely Configurable Options, complete your configuration and click Save to continue.

MoveData Raisely Endpoint URL

The final step is to register the MoveData Integration Endpoint as a target for the Raisely Webhooks. To complete this, return to the API & Webhooks in Raisely.

Raisely API & Webhooks Adminstration

Scroll to the bottom and complete the Add a Webhook section. Paste the MoveData Integration Endpoint into the URL field and register the following events depending on your configuration:

Processor Version

Events

[All]

  • Profile Created

  • Profile Updated

  • Profile Deleted

V1: Donation Only

  • Donation Created

  • Donation Succeeded

  • Donation Updated

  • Donation Refunded

  • Subscription Updated

V2: Donation & Tickets

All V1: Donation Only events plus:

  • Order Succeeded

After you click Add Webhook, you will have successfully have configured Raisely to send notifications to Salesforce using MoveData.

Configurable Options

Processor Version

Determines which outputs will be produced by the MoveData processor.

  • V1: Donation Only

    • Only produces donation schema outputs

    • Ticket Sales are considered donations

  • V2: Donation & Tickets

    • Produces both donation and commerce schema outputs

[V2 Only] Fee Allocation Method

If Processor Version is set to V2: Donation & Tickets, this configures how the gateway and platform fees are applied when a donation and ticket sale are contained within the same transaction.

  • Donation Only

    • Applies fee information on the Donation notification

  • Order Only

    • Applies the fee information on the Order notification

  • Split 50% between Order and Donation

    • Applies 50% of the fee information on each Donation and Order notification

Aggregate Order Line Items

When an order is placed with multiple entries of the same product (e.g. 2 x Adult Ticket), then aggregates into a single line item. This is automatically applied when there are 20 or more of the same product across multiple lines.

Facebook as Standard Donations

Determines whether Facebook Donations are sent through as Offline Donations or as Once-Off Anonymous Donations.

Data Migration

Data Migration is available upon request. This is a custom service provided by MoveData and is delivered by MoveData Professional Services.

  • Requires a CSV export of Raisely donation, profile and order reports

  • Records will only be imported if available via the Raisely API

Additional Field Mappings

Where possible, all fields are mapped to the appropriate schemas. Often there are fields that do not fit explicitly into a schema and these are appended as custom fields. Raisely Questions are dynamically added to Questions entries within the produced schema objects.

Custom Fields

Raisely allows users to add custom fields to their forms. There are two types of custom fields which MoveData supports:

  • Standard fields

  • Special fields

Special fields are listed below. If fields are added with specific Field IDs, MoveData will automatically enact business logic against those fields. For example, if you add the field company and this field has a value, then MoveData will construct an Organisation Account record based on the company value. Standard fields are passed through as a Question as part of the resulting notification.

Attribute Name

Field Type

Description

address

Address Lookup

Sets Address information against the Contact

birthday

Date

Sets Date of Birth information against the Contact

company

Text

Creates an Organisation Account for the company entered and establishes an Organisation Affiliation between the Contact and Organisation Account

salutation

Select Items

Sets Salutation information against the Contact

Reference

Below is a list detailing additional Custom fields sent as part of a notification by schema and object.

All Schemas

Accounts

  • No Custom Attributes

Contacts

Attribute Name

Description

Example

facebookId

Facebook User ID

900619774492636

accessToken

Access Token

d1c44e967940f26f4144921dc9535393

unsubscribedAt

Date & Time when Contact unsubscribed

2023-06-01T22:48:14Z

Campaigns

Attribute Name

Description

Example

type

Raisely Notification Type

donation.updated

path

URL Path

movedata-campaign

grandTotal

Grand Total

1000000

campaignTotal

Total for Profile

1000000

feeTotal

Fees Paid for Profile

23.98

activityTotal

Total activity for Profile

13300

exerciseGoal

Exercise goal for Profile

13300

exerciseGoalTime

Time goal for Exercise for Profile

1648121

exerciseTotal

Exercise for Profile

9300

exerciseTotalTime

Time Exercising for Profile

1642

facebookFundraiserId

Fundraiser’s Facebook User ID

900619774492636

facebookFundraiserUrl

Fundraiser’s Facebook User ID

https://www.facebook.com/donate/900619774492636

Donation Schema

Recurring Donations

  • No Custom Attributes

Donations

Attribute Name

Description

Example

settlementDate

Transaction Settlement Date (when available)

2023-06-01T22:48:14Z

giftAid

UK Gift Aid Flag (when relevant)

true

processorToken

Payment Gateway Card Token

pi_3MEPkiF8wmoXZit32qc5DRLZ

responseCode

Response Code from Payment Gateway

00

gatewayDescription

Payment Gateway Transaction Description

Donation (13564219) of AUD250 from ..

receiptDownloadUrl

Raisely Receipt PDF Link

https://api.raisely.com/v3/receipt/...

item${type}Quantity

Flattened List of Items contained within the Txn - Quantity

13300

item${type}Description

Flattened List of Items contained within the Txn (ie. Ticket Sale, Donation, etc)

1648121

Commerce Schema

Catalog

Attribute Name

Description

Example

photoUrl

Product Photo Url

https://...

type

Raisely Product Type

TICKET

soldCount

Total Number Sold

53

limitCount

Max Number that can be Sold

73

startDate

Start Date that the Product is available for Sale

2023-06-01T22:48:14Z

endDate

Last Date that the Product is available for Sale

2023-06-21T00:00:00Z

Order

Attribute Name

Description

Example

settlementDate

Transaction Settlement Date (when available)

2023-06-01T22:48:14Z

processorToken

Payment Gateway Card Token

pi_3MEPkiF8wmoXZit32qc5DRLZ

responseCode

Response Code from Payment Gateway

00

gatewayDescription

Payment Gateway Transaction Description

Donation (13564219) of AUD250 from ..

receiptDownloadUrl

Raisely Receipt PDF Link

https://api.raisely.com/v3/receipt/...

Order Item

Attribute Name

Description

Example

status

Order Item Status

ISSUED

attendance

Attendance Status

VALID

Other Resources

Did this answer your question?