Setting up Raisely
This guide walks you through connecting your Raisely fundraising platform to MoveData. Once connected, donation, profile, subscription, and order data flows into Salesforce in real time.
| Field | Detail |
|---|---|
| Product | Raisely |
| Method | Push (Webhooks) |
| Frequency | Real-time |
Demonstration#
Supported extensions#
This integration requires the Fundraising and Donations extension. The Commerce extension is supported for order events when using Processor V2.
Before you begin#
- You need access to the MoveData app in Salesforce.
- You need administrator access to your Raisely account.
- You should have at least one active Raisely campaign.
Part 1: Create the integration in MoveData#
Step 1: Open the Integrations tab#
In Salesforce, open the MoveData app and click the Integrations tab.
Step 2: Start a new integration#
Click New Integration.
Step 3: Select Raisely#
Choose Raisely from the list of available platforms.
Step 4: Name your integration#
Enter a descriptive name for your integration (for example, "Raisely — Main Campaign") and click Next.
Step 5: Open your Raisely API settings#
In a separate browser tab, log in to Raisely. Navigate to Settings > API & Webhooks.
Step 6: Copy your API key#
Locate your API key on the API & Webhooks page and copy it to your clipboard.
Step 7: Paste the API key into MoveData#
Return to Salesforce and paste the API key into the API Key field.
Step 8: Configure processor options#
Choose your preferred processor settings. See Integration settings below for a full description of each option. Click Save to finish creating the integration.
After saving, check the Notifications tab in MoveData to confirm the integration is processing correctly.
Part 2: Connect a campaign via webhook#
One webhook per campaign
Every Raisely campaign you want to connect to MoveData needs its own webhook configured in the campaign settings. If a campaign does not have the webhook added, MoveData will not receive any data from it.
Repeat the steps below for every Raisely campaign you want to connect.
Step 1: Open your Raisely integration#
In the MoveData app, click the Integrations tab, then open the Raisely integration you created in Part 1.
Step 2: Copy the integration URL#
Locate the MoveData Integration URL on the integration detail page and copy it.
Step 3: Open campaign webhook settings in Raisely#
In Raisely, open the campaign you want to connect. Navigate to Campaign Settings > API and Webhooks.
Step 4: Add a new webhook#
Click Add Webhook (or the equivalent button), then paste the MoveData integration URL into the webhook URL field. Save the webhook.
Step 5: Verify the connection#
Return to MoveData and open the Notifications tab. You should see a webhook registration event confirming the connection is active.
Raisely events#
Once connected, Raisely sends the following events to MoveData via webhooks. MoveData processes each event and creates or updates the corresponding Salesforce records.
| Object | Events |
|---|---|
| Profile | Created, Updated, Deleted |
| Donation | Created, Succeeded, Updated, Refunded |
| Subscription | Updated |
| Order | Succeeded |
Note
MoveData processes only the events listed above. Any other Raisely webhook events are silently ignored.
Salesforce records created#
MoveData creates different Salesforce records depending on your data model.
| Raisely data | Nonprofit Success Pack (NPSP) | Nonprofit Cloud |
|---|---|---|
| Supporter | Contact | Person Account |
| Company | Account | Account |
| Campaign / Page | Campaign (with hierarchy) | Campaign (with hierarchy) |
| Fundraiser role | Campaign Member | Campaign Member |
| Donation | Opportunity | Gift Transaction |
| Subscription | Recurring Donation | Gift Commitment |
| Order | Opportunity | Opportunity |
Raisely profiles use a three-level hierarchy: Campaign, Team, and Individual. MoveData maps this to a Salesforce campaign hierarchy, with each level becoming a child campaign under a parent.
Integration settings#
You can adjust these settings on the integration detail page in MoveData. Each option controls how MoveData processes incoming Raisely data.
| Setting | Options | What it does |
|---|---|---|
| Processor Version | V1: Donation Only (default) V2: Donation & Tickets |
V1 processes all Raisely data except orders. V2 also processes ticket and order data — choose V2 if your campaigns sell tickets or merchandise. |
| Fee Allocation Method | Donation Only Order Only (default) Split 50/50 |
Controls how platform fees are allocated across donation and order records. Only available with V2. |
| Aggregate Order Line Items | Retain Individual (default) Combine Where Product is Same |
Determines whether order line items stay separate or merge when they share the same product. Only available with V2. |
| Facebook as Standard Donations | Offline Donation (default) Once-Off Anonymous |
Decides how MoveData treats donations originating from Facebook fundraisers. |
| Use Notification over Profile for Addresses | Prioritise User Profile (default) Prioritise Notification Data |
Controls whether MoveData uses the supporter's stored profile address or the address included in the webhook notification. |
| Recurring Currency Mode | Subscription Currency (default) Settled Currency |
Controls the currency reported on the recurring donation for FX donations (where the donor pays in one currency and the campaign settles in another). Leave on Subscription Currency so the recurring entity reflects the donor's own currency. Switch to Settled Currency for NPSP orgs whose existing Recurring Donations are stored in the org's settled currency and do not have Salesforce multi-currency enabled — otherwise NPSP will reject the child donation as a currency mismatch. Only affects FX donations; same-currency donations are unchanged. |
Bulk data import#
MoveData only processes data from the time your integration is connected. If you need historical Raisely data imported into Salesforce, MoveData offers a professional import service. For details on how this works, pricing, and how to request an import, see Data imports.
Custom field reference#
Raisely supports several categories of custom fields. MoveData handles each category differently when mapping data into Salesforce.
Special custom fields
These Raisely custom fields trigger specific behaviour in MoveData when present on a profile:
| Field Name | Behaviour |
|---|---|
address |
Maps to the Contact's mailing address in Salesforce. |
phone |
Maps to the Contact's phone number in Salesforce. |
birthday |
Maps to the Contact's birthdate in Salesforce. |
company |
Creates an Organisation Account in Salesforce and establishes an Organisation Affiliation between the Contact and the Account. |
salutation |
Maps to the Contact's salutation field in Salesforce. |
Admin custom fields
Any other custom fields you create in Raisely appear in MoveData as Questions variables.
For example, a field called howDidYouHearAboutUs with a value of "Google" becomes available as the variable Questions_HowDidYouHearAboutUs: Google.
You can use these variables in your extension flows and field mappings.
System custom fields — Contact
| Field | Description |
|---|---|
facebookId |
Facebook User ID |
accessToken |
User access token |
unsubscribedAt |
Date and time when the contact unsubscribed |
preferredName |
User's preferred name |
System custom fields — Campaign
| Field | Description |
|---|---|
type |
Raisely profile type (e.g., GROUP, INDIVIDUAL) |
apiSource |
Raisely notification type (e.g., profile.created) |
path |
URL path for the campaign |
grandTotal |
Grand total for the campaign |
campaignTotal |
Total for the profile |
feeTotal |
Fees paid for the profile |
activityTotal |
Total activity count |
exerciseGoal |
Exercise goal for the profile |
exerciseGoalTime |
Time goal for exercise for the profile |
exerciseTotal |
Exercise completed for the profile |
exerciseTotalTime |
Time exercising for the profile |
System custom fields — Donation
| Field | Description |
|---|---|
transactionId |
Raisely transaction ID |
apiSource |
Raisely notification type |
settlementDate |
Transaction settlement date |
ipAddress |
Donor IP address |
ipAddressTimezone |
Timezone derived from IP address |
customerId |
Payment gateway customer ID |
giftAid |
UK Gift Aid flag |
processorToken |
Payment intent token |
transactionToken |
Balance transaction token |
responseCode |
Response code from payment gateway |
gatewayDescription |
Payment gateway transaction description |
receiptDownloadUrl |
Raisely receipt PDF link |
cardMethodType |
Payment method type (e.g., card, apple_pay) |
System custom fields — Recurring (Subscription)
| Field | Description |
|---|---|
status |
Original Raisely subscription status (OK, FAILED, CANCELLED, PAUSED) |
System custom fields — Catalogue
| Field | Description |
|---|---|
photoUrl |
Product photo URL |
type |
Raisely product type (e.g., TICKET) |
totalSold |
Total number sold |
totalAvailable |
Maximum number available for sale |
startDate |
Start date for product availability |
endDate |
End date for product availability |
System custom fields — Order
| Field | Description |
|---|---|
settlementDate |
Transaction settlement date |
processorToken |
Payment gateway card token |
responseCode |
Response code from payment gateway |
gatewayDescription |
Payment gateway transaction description |
receiptDownloadUrl |
Raisely receipt PDF link |
System custom fields — Order Item
| Field | Description |
|---|---|
status |
Order item status (e.g., CONFIRMED) |
attendanceStatus |
Attendance status (e.g., ATTENDED) |
Other resources#
- MoveData Raisely Integration — overview of supported features and Salesforce record mapping
- Raisely Help Centre — general Raisely support and documentation
- Raisely Salesforce Integration — Raisely's guide to connecting with Salesforce via MoveData
- Raisely Webhooks — how to configure webhooks in Raisely
- Raisely Developer Portal — API reference, webhook documentation, and authentication guides
- Raisely Available Webhook Events — complete list of webhook events and payload formats
- Raisely Data Fields Explained — field definitions for donations, profiles, and campaigns
- Raisely Status Page — platform uptime and incident history
- Raisely Changelog — product updates and new features