The following is a table showing the data mapping of a registration from Soapbox Shop 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. If Organization (see below) is not enabled, "[First Name] [Last Name]" from the Contact Information form are written to the Company standard field on the Lead & mapped to new Account. | No |
Contact Information: Last Name |
Yes - To Lead & mapped to new Contact. Does not update existing Contact. If Organization (see below) is not enabled, "[First Name] [Last Name]" from the Contact Information form are written to the Company standard field on the Lead & mapped to new Account. | No |
Contact Information: Email Address |
Yes - To Lead & mapped to new Contact and Account. Does not update existing Contact and Account. | Yes |
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 | No |
Soapbox Order Id | Yes - To Lead and OLI Temp object and used for moving product records from OLI Temp to Opportunity Products object on conversion. Generated by Soapbox. | 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 |
Yes - To Lead & mapped to Opportunity and new Contact and Account. Does not update existing Contact and Account. | Yes |
Shipping Form: Shipping Address |
Yes - To Lead & mapped to Opportunity on conversion | Yes |
Shipping Form: Shipping Note |
Yes - To Lead & mapped to Opportunity on conversion | Yes |
Shipping Form: Shipping Note |
Yes - To Lead & mapped to Opportunity on conversion | Yes |
Transaction Description | Yes - To Lead & mapped to Opportunity on conversion | Yes, except for Braintree which doesn't capture Transaction Description |
Transaction ID | Yes - To Lead & mapped to Opportunity on conversion | Yes. Generated by payment processor. |
Transaction Date | Yes - To Lead & mapped to Opportunity on conversion | Yes |
Transaction Status | Yes - To Lead & mapped to Opportunity on conversion | Yes. Generated by payment processor. |
IP Address | Yes - To Lead & mapped to Opportunity on conversion | No |
Product Info: All standard fields | Yes - To OLI Temp object prior to Lead conversion as one record per product ordered; mapped to Opportunity Products standard object (child of Opportunity) on Lead conversion as one record per product ordered | No |