FREE TRAINING: Join us for Open Office Hours every Tuesday at 3 pm ET or for our weekly training webinars. View Schedule >>

Data mapping from the Classes app to payment processor and Salesforce

created

The following is a table showing the data mapping of a registration from the Classes app when a shopping cart order is submitted to the payment processor and Salesforce.

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
Campaign Yes - To Lead for inclusion as Campaign Member. On conversion, makes Contact a Campaign Member and associates Opportunity with Campaign, This Campaign will be common for all orders processed through the shopping cart. 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. The Transaction Description can be customized on the Shopping Cart tab of the Events > Configuration. 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 and Class Salesforce Campaign 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. The Campaign field on the Ticket Temp and Tickets records is a lookup to the Campaign representing a specific class. No

 

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