When an organization uses Soapbox Engage for event registration, orderers (purchasers) can order multiple tickets for an event.  When integrated with Salesforce, each ticket ordered through the Soapbox Engage Events app is represented as a Ticket object record in Salesforce.  These Ticket records contain important information about the ticket purchaser and the ticket holder.

This article outlines the process by which the Events app populates important fields representing the ticket purchaser and the ticket holder.

Identifying ticket purchaser and ticket holder

1. When the ticket orderer and ticket holder are the same:

   • If the ticket holder's first name, last name, and email address match those of the orderer (the person who made the purchase), Soapbox Engage will populate two specific fields on the Ticket object record in Salesforce:
     • Purchaser field: This field is populated with the Contact record of the orderer in Salesforce, indicating who purchased the ticket.
     • Ticket Holder field: This field is also linked to the same Contact record of the orderer, indicating that the purchaser is also the attendee.

2. When the ticket holder is different from the orderer:

   • For tickets within the same order where the ticket holder's information does not match the orderer's information (different first name, last name, or email address), Soapbox Engage will handle the following fields accordingly:
     • Purchaser field: This field is populated with the Contact record of the orderer in Salesforce, indicating who purchased the ticket.
     • Ticket Holder field:  This field ls left blank.