Skip to main content
Patricia Frontanes
Bonterran
August 14, 2026

What data syncs from OneCause into EveryAction?

  • August 14, 2026
  • 0 replies
  • 38 views

The integration moves key event fundraising data from OneCause into EveryAction automatically, every hour. Here's exactly what comes over and how it maps.

Step 1: Understand what syncs

Contacts

  • Individual supporters sync as Individual contacts in EveryAction. Fields: first name, last name, email (primary, Personal type), phone (primary, Personal/Cell type), address (Home type).

  • Company supporters sync as Organization contacts. The company name goes on the org record; the primary contact's name, email, and phone go on a linked Individual contact. Address goes on the org record.

  • The OneCause Supporter ID is stored as an External ID on the contact — used for matching across syncs and for looking up a specific contact in EveryAction by their OneCause ID.

  • New contacts default to email subscription status not subscribed. Existing email subscription status is never overwritten.

Events

  • OneCause events sync as Event records in EveryAction.

  • Event type: 'OneCause Event' is applied to all synced events by default.

  • Event role: 'Supporter' is applied as the default event role.

  • A source code is automatically created using the event name and applied to all related transactions — the primary way to filter and report on a specific event in EveryAction.

Event sign-ups and tickets

  • When a supporter attends a OneCause event, their sign-up and ticket information syncs as an Event Sign-Up record in EveryAction.

  • Event status: Set to 'Completed' if a check-in date exists in OneCause; otherwise defaults to 'Scheduled'.

  • Ticket type: Syncs as an Event Ticket Category in EveryAction. Created if it doesn't exist yet.

  • Guests without a supporter ID: The system will find or create a contact based on email address if available. If no email, no contact is created.

Contributions (paid activities only)

  • Ticket purchases, donations, and other paid transactions sync as Contribution records in EveryAction.

  • Payment types supported: Card, ACH, Check, Cash, PayPal, Apple Pay, Google Pay, and Other.

  • Contribution status: Syncs as 'Pending' initially. Updates to 'Settled' once OneCause sends settlement data. Cash and check default directly to 'Settled'.

  • Daily financial batch: All synced contributions are grouped into a daily financial batch with 'OneCause Import' in the name for easy identification.

  • Source codes: The OneCause event name is applied as a source code on each contribution.

  • Recurring: If an activity is recurring, a Recurring Commitment is also created in EveryAction.

  • Custom field: A custom contribution field for ‘purchase item type' is created on synced contributions. This gets stored under a 'OneCause’ custom field group.

Event item donations

  • Donated auction items and other event item donations sync as In-Kind contributions in EveryAction.

  • Only syncs when: item status = 'Received' and you have connected the item to a Supporter in OneCause.

  • Item name and quantity are stored in contribution notes. Example: '$50 Apple iTunes Gift Card (Quantity: 2)'.

  • Amount can be $0.00 — a CRM behavior change was made to support this, applicable only when payment method is In-Kind.

Fundraising pages

  • If a contribution came through a OneCause fundraising page, a source code is created using the fundraiser name and applied to the contribution record.

Step 2: Know what doesn't sync and why

Unpaid activities

The integration only syncs paid transactions. Unpaid activities — pledges, items in cart, or anything that hasn't been completed as a payment in OneCause — do not sync to EveryAction. This was a deliberate decision, and it's one customers may ask about. Here's the full reasoning:

  • Unpaid activity is normal and expected in event fundraising. In the days leading up to an event — and especially the day of — there are typically a lot of things sitting unpaid: items in carts, tentative ticket holds, pending sponsorships. Most of these either get paid on event day or get removed. Syncing them to EveryAction before they're resolved would create noise and inaccurate contribution records.

  • Customers told us they only want paid data in their CRM pre-event. When we talked to customers directly, this was the consistent feedback. They're already accustomed to the way event fundraising works and don't expect to see unpaid activity in their CRM. The CRM is for completed transactions.

  • Keeping unpaid activity in OneCause protects event data integrity. We encourage customers to track and run payments for unpaid activity through OneCause even post-event, not pull it to EveryAction manually. This keeps their OneCause event data accurate and complete — which matters when they're planning next year's event. And as payments do come in through OneCause, they'll flow to EveryAction automatically.

Step 3: Understand read-only behavior

Read-Only Behavior After Initial Sync

Once a record syncs into EveryAction for the first time, the integration treats it as read-only. Subsequent changes made in OneCause to that record will not overwrite what's in EveryAction.

This is intentional — it protects edits that customers make directly in EveryAction from being overwritten the next time the sync runs.

Important: Contacts, events, and event sign-ups are fully read-only after their initial sync. If a customer updates a contact in OneCause — adds a phone number, changes an address — that change will not carry over to EveryAction.

Contributions are also read-only, with the following exceptions. These fields will continue to update on existing contribution records as OneCause sends new data:

  • Payment settlement date

  • Payment batch ID

  • Contribution amount (value)

  • Payment status

  • Refund ID

  • Refund date

What do you want to do next?

Not what you are looking for? Return to Understanding the OneCause and EveryAction Integration.

What data syncs from OneCause to EveryAction? | Do contacts sync from OneCause to EveryAction? | Why aren't my unpaid pledges syncing to EveryAction? | How are OneCause contributions recorded in EveryAction? | Why didn't my OneCause contact update in EveryAction after I made changes? | How do auction item donations sync from OneCause to EveryAction? | How do I find OneCause contributions in EveryAction financial batches?