WEBINAR: How to Raise More Money Without Burning Out with Special Guest Presenter Beth Kanter, 8/14/2017 at 3 pm ET. Register >>

Data mapping from Soapbox Events to payment processor and Salesforce

created

The following is a table showing the data mapping of a registration from Soapbox Events to the payment processor and Salesforce. Data is sent to the payment processor ONLY if it is a paid event. Data is sent in the manner described below to Salesforce for BOTH paid and unpaid events.

As you'll see, the different fields for first name and last name in the Contact Information and payment sections of the form are stored in different places. While the majority of time, these are the same, if you are having trouble reconciling data between your payment processor and Salesforce, it is helpful to search for the email address in Salesforce for a transaction in the payment processor. This field is consistent between the two by design.

Data Salesforce Payment Processor
Contact Information:
First Name
Yes - To Lead & mapped to new Contact. Does not update existing Contact. No
Contact Information:
Last Name
Yes - To Lead & mapped to new Contact. Does not update existing Contact. No
Contact Information:
Email Address
Yes - To Lead & mapped to new Contact and Account. Does not update existing Contact and Account. Yes
Contact Information:
Address, if enabled 
Yes - To Lead & mapped to new Contact and Account. Does not update existing Contact and Account. No
Contact Information:
Phone, if enabled
Yes - To Lead & mapped to new Contact and Account. Does not update existing Contact and Account. No
Contact Information:
Organization, if enabled
Yes - To Lead in Company standard field. Creates new Account with this name, if no matching Contact exists. Does not update Contact, if matching Contact exists. No
Ticket Type DEPRECATED: This field is not longer updated due to individual Ticket records being created. See final row of chart. No
Ticket Price DEPRECATED: This field is not longer updated due to individual Ticket records being created. See final row of chart. No
Number of Tickets Yes - To Lead and mapped to Opportunity on conversion; creates one Ticket record for each ticket purchased and populates name field with placeholder values No
Campaign Yes - To Lead for inclusion as Campaign Member. On conversion, makes Contact a Campaign Member and associates Opportunity with Campaign No
Payment Form:
Form of Payment
Yes - To Lead and mapped to Opportunity on conversion Yes, if credit card
Payment Form:
First Name
No Yes
Payment Form:
Last Name
No Yes
Payment Form:
Credit Card Number, Expiration Date, and Security Code
No Yes
Payment Form:
Billing Address
No Yes
Transaction Description Yes - To Lead and mapped to Opportunity on conversion. For Events, the Transaction Description will always be "Registration." Yes, except for Braintree which doesn't capture Transaction Description
Transaction ID Yes - To Lead and mapped to Opportunity on conversion Yes. Generated by payment processor.
Transaction Date Yes - To Lead and mapped to Opportunity on conversion Yes
Receipt Sent (date of transaction) Yes - To Lead and mapped to Opportunity on conversion No
Thank You Sent (date of transaction) Yes - To Lead and mapped to Opportunity on conversion No
Transaction Status Yes - To Lead and mapped to Opportunity on conversion Yes. Generated by payment processor.
IP Address Yes - To Lead and mapped to Opportunity on conversion No
Attendee Info: All standard and custom fields Yes - To Ticket Temp object prior to Lead conversion as one record per attendee; mapped to Tickets object (child of Opportunity) on Lead conversion as one record per attendee No

 

Have more questions? Submit a request
Article is closed for comments.