Raisely sync
What flows from Raisely into Together, how often, and how Live vs. Test donations are treated for compliance.
The Raisely integration uses webhooks for real-time updates and a 15-minute reconcile cron as a backstop. Most data lands within seconds of the donor pressing Donate on Raisely.
What syncs
| Record | Direction | Mapped fields |
|---|---|---|
| Donations | Raisely -> Together | Amount, donation date, payment method, campaign attribution, donor link, Live or Test mode flag, donation status. |
| Donors | Raisely -> Together | First name, last name, email, phone, address. From the Raisely "user" record linked to each donation. |
| Subscriptions | Raisely -> Together | Recurring donation schedules and their state. Renewals show up as donations when they settle. |
| Campaigns | Raisely -> Together | Campaign metadata (name, slug). Used for attribution on each donation and for tracking-code FCA classification. |
| Refunds | Raisely -> Together | Full and partial refunds. Donations are flipped to a refunded state so compliance aggregates stay accurate. |
Direction is one-way (Raisely to Together) today.
Sync cadence
Two paths feed Raisely data into Together:
- Webhooks. Raisely fires an event for each donation, donor update, refund, or subscription change. Together's webhook endpoint processes the event within seconds and writes to the database.
- Reconcile cron. Every 15 minutes, Together fetches anything that changed in Raisely since the last sync watermark. This catches webhook deliveries that Raisely missed or that Together's endpoint was unavailable for.
Most updates land via webhook within a few seconds. The cron is invisible 99% of the time; it only matters during the rare window where webhook delivery fails.
Live vs. Test mode
Raisely tags every donation as Live or Test depending on whether the campaign is in test mode at the time of the donation. Together imports both but treats them differently for compliance.
The Mode filter on the Raisely card at Settings -> Integrations controls behaviour:
| Setting | What happens |
|---|---|
| Live donations only (default) | Test donations are imported but excluded from cap and disclosure tracking. They appear in the donations list with a Test badge. |
| Live and test donations | Test donations count toward cap and disclosure totals. Use this only when your Raisely setup deliberately uses Test mode for production data. |
Most orgs leave this on the default.
Donor matching
Raisely identifies donors by an internal user ID, which Together stores as an external ID on the Together donor record. Subsequent donations from the same Raisely user route to the same Together donor.
If the same email shows up under two different Raisely user IDs (a Raisely-side duplicate), Together creates two donor records and flags them in the duplicate queue at Donors -> Duplicates.
Campaign attribution
Each Raisely donation carries a campaign reference. Together stores the Raisely campaign slug on the donation as its tracking code. You then map those slugs to FCA / non-FCA at Settings -> Integrations under FCA Donation Filtering; see Set up tracking codes.
If your Raisely setup uses a single campaign for everything federal, the simplest config is All codes count as FCA for the Raisely source.
Subscriptions and recurring donations
Raisely subscriptions sync as a separate object, but the practical effect is that recurring donations land in Together's donations list every time they settle. Together infers the recurring relationship from the donor's history rather than treating subscriptions as standalone records.
A subscription paused or cancelled in Raisely stops emitting donations; Together doesn't separately track the subscription's state.
What doesn't sync
- Fundraising profiles (peer-to-peer pages). Together doesn't sync the individual fundraiser profiles. The donations on those pages do sync; they're attributed to the donor who gave, not the fundraiser who hosted the page.
- Posts, updates, comments. Raisely's content layer isn't synced.
- Custom fields on the user record. Not currently mapped. Contact support if a specific custom field is important to you.
Disconnecting
Click Disconnect Raisely on the integrations card. Historical donors and donations are preserved; the Raisely-side webhook is removed and no further data flows. Reconnect later to resume; the reconcile cron will back-fill any donations missed in the gap.
What to do next
- Connect Raisely if you haven't yet: Connect Raisely.
- Set up tracking codes to map Raisely campaigns to FCA categories: Set up tracking codes.
- Read the NationBuilder sync reference if you're comparing the two: NationBuilder sync.