Every few years Sitecore takes a giant leap forward and introduces a raft of innovative new features. Sitecore 9 is an expansive new release that has integration partners like our team at FuseIT, excited by features like Headless and xConnect. S4S, the enterprise Sitecore to Salesforce integration from FuseIT has been updated to leverage these features making S4S even more compelling.

This article is about S4S support for Experience Forms, Sitecore’s new way to quickly create web forms. Experience Forms have advanced form editing capabilities, drag and drop, and the ability to create multi-step wizards. Sitecore is indicating that Experience Forms will replace Sitecore Web Forms for Marketing (WFFM) forms in future versions of Sitecore, although both form technologies are supported in Sitecore 9.

There are many reasons you might like to quickly create a web form with Sitecore Experience Forms: 

  • Conference and event registrations
  • Information requests
  • Membership applications
  • Survey or feedback submissions
  • Setting communication preferences
  • Job applications

S4S has always had a wizard to map Sitecore forms to Salesforce objects (usually lead records). The new S4S Mapping Wizard for Sitecore Experience Forms has a range of new features, many because of features added in Sitecore 9.

The process is simple - before using the S4S Mapping Wizard, Sitecore editors create a new Sitecore Experience Form and assign it one of the S4S Save Actions. Editors then open the S4S Mapping Wizard from the Sitecore Launchpad and select the required form to begin the mapping process:

  • Companies with multiple Salesforce instances (orgs) select the destination org for the form data. This means a website with multiple forms can interact with several Salesforce instances.
  • Selecting the org populates the Salesforce Object Owner dropdown list with the Salesforce users in the selected org. This is where the Salesforce workflow can be used to notify the nominated user whenever a web form is submitted.
  • Selecting a Salesforce object, or custom object populates the field mapping section which lets the editor map the Sitecore form fields to Salesforce fields.
  • The Salesforce Object Matching Rule is used to select one or more fields that, if matched, cause an update rather than an insert. This new feature eliminates the need to create a custom save action that does de-duplication checking against Salesforce.
  •  Another feature of the S4S Mapping Wizard is the ability to automatically add leads and contacts to nominated Salesforce campaigns if the form is mapped to one of those objects. A receiver campaign can be selected in the “Map to Salesforce Campaign” section.
  • The S4S Save Action associated with the Sitecore Experience Form can push the form data to Salesforce with, or without, Sitecore analytics. The latter option applies to mapped Salesforce lead or contact records only. If this is required the Sitecore editor can check the ‘Push Sitecore Analytics” checkbox. Note that, the S4S Salesforce package needs to be installed to host the Sitecore analytics details.

With the form data and the visitor's web browsing behavior visible in Salesforce, the salesperson is well placed to initiate an informed dialogue with the visitor, having gained an insight into their needs, based on their browsing activities. If the visitor returns and continues exploring the website in the future, S4S will update Salesforce with real-time analytics.

There are even greater S4S features that let you interact with website visitors in a multitude of ways. These will be described in later articles.