As you get started integrating Soapbox Engage with Salesforce you may have found yourself asking:
"Do we need to use the Lead object when integrating Soapbox Engage apps with Salesforce?"
If you have, then you're in the right spot! The short answer: Yes.
Soapbox Engage uses the Lead object for Donations, Events, Shop, Classes, Petitions, and Actions apps. Our programming model allows these apps to send data to Salesforce through the Leads object. We rely on that object for various triggers to flow data throughout Salesforce and back to Soapbox Engage. Therefore, it is currently not possible to utilize full Soapbox Engage automation without using the Leads object for those specific apps.
In most circumstances, the Lead record created by Soapbox Engage is immediately auto-converted from a Lead to a new or existing contact by automation contained in the our packages. The automation based on matching criteria used by Soapbox Engage that check fields like name, email, and address between the data submitted and existing contact records. In some instances, information may be similar but not exactly the same as existing data. In these instances, the Lead will not be auto-converted and will instead be marked for review. This ensure clean and accurate data flows through your Salesforce instance.
If you're curious about the data flow or mapping for a certain app these knowledge articles will provide more detail:
Matching criteria for auto conversion of Leads created by Soapbox Engage apps
Donations app
Data mapping from Soapbox Donations to payment processor and Salesforce
Order of operations during donation processing
Events app
Data mapping from Soapbox Events to payment processor and Salesforce
Data mapping from the Classes app to payment processor and Salesforce
Order of operations during event registration processing
Shop app
Data mapping from Soapbox Shop to payment processor and Salesforce
Actions app
Data mapping from the Actions app to Salesforce
Petitions app
Data mapping from the Petitions app to Salesforce