All Collections
Sync and Exports
Understanding Ticket Configuration for Events Sync
Understanding Ticket Configuration for Events Sync

Learn how events sync pushes data to Raiser's Edge based on each ticket configuration.

Sweta Kumari avatar
Written by Sweta Kumari
Updated this week

Understanding how event registrations on Almabase are pushed to RENXT can be made clear with an example.

A registration from an event shows a total amount of $129. This was divided as:

  • Ticket 1 - $10

  • Ticket 2 - $19

  • Library gift ticket - $100

A breakdown of the different ticket configuration

All payments (tickets and gifts) are pushed as one gift

  • Under the 'Payment' section, all the ticket components are added to one.

  • Adding it up to $129.

  • If the tickets and donations are associated with different funds, gifts split will be created.

Ticket payments and Gifts are pushed as separate gifts

  • Tickets fees and donations are added as two different gifts:

    • One for the total of both tickets.

    • Another for donation.

Each ticket payment and gifts are pushed as individual gifts

  • Each ticket fee and donation are added as separate gifts.

  • In the example, two tickets and a donation become three gifts to RENXT.

Only RSVP status for guests

  • Payment details are not sync to RENXT.

  • It only sends the RSVP status for the person who registered.

Only gifts (via gift tickets) are pushed

  • This ignores ticket fees.

  • Only the payments received as donations are sent to RENXT.

  • So, the $100 donation is sent, not the total $129.

Please write to us at or through the Intercom Chat 💬 if you have any queries or concerns😄.

Did this answer your question?