Boost recurring donations this giving season with the new upsell prompt!The following is a table showing the data mapping of a donation transaction from Soapbox Donations 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: 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 |
| Custom Fields #1 - 4, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Anonymous, if enabled | Yes - To Lead in Anonymous Donation field and mapped to Opportunity on conversion | No |
| Newsletter Sign Up, if enabled | Yes - To Lead in Newsletter Opt In field to trigger workflow to update associated fields on Lead for mapping to Contact | No |
| Amount | Yes - To Lead in Donation Payment Amount field and mapped to Opportunity on conversion | Yes |
| Payment Frequency | Yes - To Lead as Soapbox Donation or Soapbox Recurring Donation record type and mapped to Opportunity record type | Yes |
| Campaign | Yes - To Lead for inclusion as Campaign Member. On conversion, makes Contact a Campaign Member and associates Opportunity with Campaign | No |
| Tribute Type (In Honor or In Memory), if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Tribute Name, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Type, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification First Name, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Last Name, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Email, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Mailing Address, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Mailing City, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Mailing State, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Mailing Postal Code, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Mailing Country, if enabled | Yes - To Lead and mapped to Opportunity on conversion | No |
| Notification Message, if enabled | Yes - To Lead and mapped to Opportunity on conversion | 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 |
Yes, in part - Credit Card Expiration Month, Credit Card Expiration Year and Credit Card Last Four Digits saved to Lead & mapped to Opportunity |
Yes |
| Payment Form: Billing Address |
Yes - To Lead & mapped to new Contact and Account. Does not update existing Contact and Account. | Yes |
| Transaction Description | Yes - To Lead and mapped to Opportunity on conversion | 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. |
| Subscription 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 |