...
- S4S Generic Mapping: This Save Action maps WFFM fields to any object in Salesforce. For Salesforce lead or contact objects you can use the wizard to automatically add the visitor to a Salesforce campaign. No S4S Salesforce packages are required for this functionality.
- S4S Push Visitor: This Save Action maps WFFM fields to Salesforce Contacts or Leads only. This action pushes the form data to Salesforce, and the Sitecore xDB data associated with the visitor's activities on the website. This requires several receiver fields in Salesforce that are installed with a Salesforce package.
- S4S Identify and Push Visitor: Similar to S4S Push Visitor, this Save Action uses the field data in the nominated identifier field with the Sitecore Identify() method to determine if the current visitor has visited previously on another device. The visitors Sitecore Contact record will then reference all the other devices (and cookies) used on previous visits. If the visitor is authenticating into Sitecore it is useful to add the Identify() method to the login control and nominate the username (or email address) as the identifier. This increases the chance that Sitecore will match previous visits and push the visit analytics to Salesforce.
 | IMPORTANT: Save Actions with “Push Visitor” in the action name require an Analytics Package to be installed in Salesforce. The package adds the required receiver fields to store the Sitecore analytics data. |
| IMPORTANT: If your website has multiple WFFM forms that require Push Visitor save actions, ensure all forms use the same save action e.g. all forms should use S4S Push Visitor save actions, or all forms should use S4S Identify and Push Visitor save actions. |
In the Sitecore tree, Save Actions are installed at
...