Keela

The Keela & Raisely integration streamlines data syncing between the two platforms, helping your organisation manage campaigns more effectively and engage with donors post-campaign.

With this integration, essential campaign, transaction, and contact data from Raisely are automatically synced into Keela, giving you a complete picture of your supporters.

Check out this Keela Integration Set-up Guide if you'd like to find out more about the set-up!


Supported Countries

The integration is available for organisations based in:

  • 🇦🇺 Australia
  • 🇳🇿 New Zealand
  • 🇨🇦 Canada
  • 🇺🇸 United States
Note for New Zealand organisations: Make sure your default currency is set to NZD in Keela.

Key Features

  • Automatic One-Way Sync: Data flows from Raisely into Keela after integration is connected
  • Campaign Data: Raisely fundraising campaigns are mirrored in Keela.
  • Transaction Data: Donations and ticket purchases (including offline donations) are recorded in Keela 
Note: Test data is not synced to Keela to ensure clean data while testing campaigns
  • Contact Data: Donor information is synced to maintain unified supporter profiles
  • Recurring Donation Support: Recurring transactions are structured as series in Keela
  • Receipts: Raisely receipts are accessible directly from Keela
  • Soft Credits: Fundraiser profile owners are soft credited for donations made to their profile page
  • Multi-Currency Support: Supports multi-currency syncs from Raisely. The currency shown in Keela is based on your default Keela currency.
  • Minimal Configuration: The integration uses default settings for a smooth setup
  • Campaign Goal Currency Conversion: Goals created in a different currency are converted to your Keela organisation’s primary currency, using the exchange rate at the time of creation

Current Limitations

  • One-Way Sync Only: Changes made in Keela won't reflect in Raisely.
  • Core Fields Only: Only key contact and transaction fields (Name, Email, Address, Phone) are synced. Custom fields are not supported.
  • Ticket Categorisation: Ticket revenue appears under Purchase in Keela.
  • No Historical Sync: Only data created after integration setup will sync.
  • Matched Giving Not Synced: Matched donations in Raisely won’t be automatically attributed to matched donors in Keela.

Managing Duplicate Contacts in Keela

If a Raisely contact already exists in Keela, you have two options:

Option 1: Replace only empty fields in Keela with Raisely data
Option 2: Replace all fields in Keela with Raisely data


Editing Associations in Keela

You can edit associations (like Impact Areas) for Raisely transactions directly in Keela:

  1. Open a Raisely transaction in Keela
  2. Click the pencil icon next to the transaction
  3. Choose the association (e.g. Impact Area)
  4. Click Save

Note: Campaigns and soft credits must still be edited in Raisely. Bulk editing is supported for:
  • Impact Area
  • Source
  • Keywords
  • Dedications

Troubleshooting Tips

Common Issues & Fixes

### accordion

## expand

# Data not syncing?

  • Confirm your API key or OAuth connection is active
  • Ensure data was created after integration setup
  • Allow up to 5 minutes for the sync to complete

## expand

## expand

# Duplicate contacts?

  • Review Keela’s merge settings (default: only update empty fields)
  • Use Keela’s import tool to handle pre-integration contacts

## expand

## expand

# Missing or partial data?

  • Check transaction type: ticket sales appear under Purchase, not Donation

## expand

## expand

# Receipt issues?

  • Keela doesn’t generate receipts for Raisely transactions
  • You can issue receipts directly from Raisely’s admin panel

## expand

### accordion


Future Enhancements

We’re working on exciting improvements, including:

  • Fund and ticket bundle mapping
  • Workflow and automation triggers
  • Email communication sync for deeper donor insights

Need Help?

If you have questions or need help with the integration, contact our support team. We're here to help you get the most out of Keela & Raisely.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.