Sitecore to Salesforce® Integration

CMS to CRM integration is a revolution in customer experience! Like when the sales team tweaks a CRM contact record to create a personalized experience for the contact when they next browse the website. The integration means data can be shared across your business from a single data source so key information, like leads, suppliers, customers, partners and members, is never isolated in databases invisible to other. The CRM data becomes the single source of truth for your entire organization and much more likely to be up-to-date, particularly if individuals update their personal data on a profile page in the company website.

The S4S connector from FuseIT integrates Sitecore with Salesforce® CRM. Among it's many uses, organizations can collect leads (or contacts) from the website, and push the form data, along with Sitecore DMS data and browsing analytics, to the CRM allowing fast and easy qualification. This extends Salesforce® based marketing applications like ExactTarget, Marketo, Eloqua and Pardot with Sitecore specific information. S4S has a great integration with Sitecore Web Forms for Marketers and a mapping wizard making this very easy.

If your website has a registration process new users can be automatically assigned a role so they have selected views of information on your website. The roles, along with a landing page, can be managed manually in the CRM record. Of course, any change in Salesforce® is immediately available in Sitecore and vice-versa.

With the website visitor/customer data available in Salesforce® you can choose who, across the organization, benefits from access to this information - typically marketers processing leads and generating sales.

Read the S4S white paper


Integration Business Value

After connecting Sitecore to Salesforce®, your marketing team will discover new ways to work with customers without leaving their familiar Salesforce® environment. There are potentially thousands of opportunities. Here is just one:

  • Use Sitecore profiling and pattern cards to learn about anonymous website visitors.
  • Render targeted content that matches their profile all the time inviting them to fill in a lead form.
  • Create a new lead in Salesforce® and show the Sitecore behavior. Let your sales team adjust the visitors experience when they return.
  • For more advanced control, let customers login to the website with credentials stored in their Salesforce contact (or lead) record.
  • Marketers can land the customer on a selected web page set in their Salesforce® contact record.
  • Marketers can change the look and feel of each customers website experience by changing profile settings in Salesforce® contact record.
  • From Salesforce®, marketers can send emails to customers inviting them to visit the company website.
  • When the customer browses the website, they are tracked and their behavior recorded in both Sitecore and Salesforce®.

Marketers can stay in Salesforce® and have full control over what individual users experience when visiting your website.

A common usage of S4S is lead or contact creation from a Sitecore web form. This is a trivial task using the S4S Web Forms for Marketers (WFFM) wizard that allows the creation of any Salesforce® object from a WFFM form.

Other integration examples are the creation, viewing or editing of Salesforce® documents, leads, contacts, opportunities or any custom object from the website.

About S4S

S4S lets Sitecore users seamlessly exchange information with Salesforce®. By integrating these two feature packed super-systems, the connector opens a new world of opportunities for marketing your products and services.

From within Salesforce®, marketers can control how the company website looks and behaves for individual visitors. Tailored web content can be shown to individual website users based on settings in their Salesforce® contact or lead record. This versatility presents many opportunities to deliver personalized browsing on the public network.

Rendering targeted content to individual customers is not the only leverage S4S offers. With real-time bi-directional communication, almost any object in either system can be made visible to the other. For example, Salesforce® documents can be made accessible on the website to anonymous or selected users with access permissions. Even website login credentials can be stored and controlled in Salesforce contact (or lead) records.

S4S fully supports the integration of Salesforce® campaigns and Sitecore EXM with our S4S EXM module which uses Sitecore's advanced email processing engine to send tailored emails to bulk recipients.

Please see the following videos to help you understand how S4S works:

S4S is ideal for clients requiring strong web content management with Salesforce®. S4S allows feature sharing across the platforms and the ability to maintain and publish content and information from one location. For more information please download the S4S brochure.

Web Forms for Marketers Support

S4S has advanced support for pushing web form data to Salesforce® using Sitecore's Web Forms for Marketers (WFFM) web forms. Using Sitecore's WFFM is the easiest way to create Salesforce® records from web forms. The entire form setup can be undertaken by non-technical Sitecore users.

Sitecore users first create a WFFM web form then use the simple S4S mapping wizard to map the form fields to the matching fields of any Salesforce® object. When a visitor completes the form on your website, the captured data is pushed to the mapped Salesforce® object, along with any attachments if that is required.

If the mapped object is a Salesforce® lead or contact, Sitecore analytics data (DMS) can also be pushed, along with the form data, so a complete picture of the visitors behavior is visible and reportable in the new Salesforce® record. Even better, users can edit the analytics data in Salesforce® so the returning visitor will be given the required unique experience on the website.

The S4S mapping wizard also has an option to automatically add new leads and contacts to an existing Salesforce® campaign. This makes it very easy to create targeted marketing lists if your site has multiple capture forms. The adjacent image shows how a Sitecore WFFM is mapped to a Salesforce® contact record.


You can also use the S4S mapping wizard to create a WFFM form that requests a user name and password from the visitor. The credentials are saved to Salesforce® and can, using the S4S Security Connector, enable the visitor to login to the website using the user name and password. In this situation, Salesforce® is the single source of truth and the credentials are never saved in Sitecore.

S4S uses the Partner API to communicate with Salesforce®. A dedicated API user is assigned in Salesforce® so when new records are created using the S4S mapping wizard, the "Created By" field will always be the API user. It is easy to control the user's security permissions at a granular level against each Salesforce® object.



Sitecore 7.5 and beyond supports big data and takes personalized browsing or "experience" to new levels. These recent versions make it possible to quickly capture huge volumes of visitor data using a NoSQL architecture that can incrementally scale to huge volumes of data. Once the data has been collected, a subset of intelligent information is pushed to the SQL Server Analytics DMS database where it is available for macro or micro reporting.

S4S leverages this wealth of information by making it available in Salesforce® lead and contact records. Armed with this data the sales team is empowered with a far greater understanding of how visitors are using your website. This enables the team to approach and begin interacting with visitors and customers with more knowledge than has been possible to date. Because key data is persisted in Salesforce® it is easy to identify prospects with high levels of engagement using Salesforce® reports.

Sitecore for Salesforce® Use Cases

S4S opens up a world of possibilities - some typical uses cases are listed below.

Case 1 - Salesforce® contact created from a Sitecore lead form

  • Dave, a Sitecore administrator, creates a lead form using the Sitecore Web Forms for Marketers (WFFM) wizard.
  • Dave uses the S4S WFFM wizard to map each form field to its contact equivalent in Salesforce®.
  • Visitor, Susan, fills out the form on the website. She also uses the form to upload a document.
  • When Susan submits the form a new Salesforce® contact is created and populated with the form data. The document is attached to the record.
  • The contact record is populated with Susan's analytics and pattern data that tracks her behavior back to when she first visited the website.
  • Sitecore forms can be mapped to other Salesforce® objects like leads, cases, opportunities or custom objects.

Case 2 - Sales team change the experience of Sitecore website visitors

  • Prospect, Mike, comes to the website as an unknown visitor.
  • Mike triggers several Sitecore goals then submits a lead form.
  • Using S4S, a lead record is created in Salesforce®.
  • Mike's goals, pages visited, page durations, Sitecore pattern data and much more are exposed in the record.
  • Geo-location lookup also shows Mike's location in Salesforce®.
  • Bram, a member of the sales team, views the analytics data and armed with this information, speaks to Mike and learns even more about his interests. He adjusts Mikes Sitecore profile and pattern keys in Salesforce® so the next time he visits the website he has a more relevant experience.

Case 3 - Web-to-Custom object capture from a Sitecore Apply Now form

  • Candidate, Peter, fills out an Apply Now web form on the website.
  • Using S4S, a custom object record is created in Salesforce® populated with the form data.

Case 4 - Show Salesforce® Reports on the Sitecore website

  • Customer, Susan, visits the website and navigates to the Reports page.
  • Susan selects and views the required Sitecore report.

The following cases require the included Security Connector module to be installed.

Case 5 - Salesforce® Contacts are Sitecore Users

  • Contact, John, logs into the website using credentials stored in his Salesforce® contact record.
  • John's Sitecore role can also be set in his Salesforce® contact record.
  • In Sitecore administrator, John appears as a normal Sitecore user even though his member and profile information is only stored in Salesforce®.
  • Salesforce® leads can also be assigned as Sitecore users in the same way.

Case 6 - Salesforce® Contact details updated from the Sitecore website

  • Contact, John, logs into the website and edits his personal information.
  • Using S4S, John's contact details in Salesforce® are updated.

Case 7 - Website users view Salesforce® documents

  • Bram, logs into the website and navigates to a Show Files page. He sees this page because of his "Salesman" role set in Salesforce®.
  • Bram clicks the “Show All Documents” button.
  • Using S4S, files listed in the Salesforce® Document tab are listed.
  • Bram clicks on a file, the latest product price list, which opens with its associated program.

Case 8 - Sitecore users see forms pre-populated from Salesforce®

  • Field Engineer, Daniel, visits the website, logs in and navigates to the Technical Support page.
  • He sees this page because of his role set in Salesforce®.
  • His companies customers are listed based on a report from Salesforce.
  • He selects a customer and navigates to the list of products the customer uses. S4S has pulled this information from Salesforce®.

Case 9 - Marketers drive customer website experience from Salesforce®

  • Bram is a salesman who wants Susan, a customer, to buy a widget.
  • Bram goes to Susan's Salesforce® contact record and selects the widget from a drop down list.
  • Susan logs into the website. Her home page is now the widget page.
  • Her Sitecore profile equates to her Salesforce® contact record so the website behaves accordingly.
  • The website will assign high values to the widget and render promotions for this product.

Case 10 - Administrators view Salesforce® campaign members in Sitecore

  • Dave, a Sitecore administrator, wants to include Salesforce® contacts in his Sitecore ECM email campaign.
  • He creates a campaign in Salesforce® and populates it with a contact list.
  • Dave clicks the 'Visible In Sitecore' check box in the campaign record.
  • In Sitecore desktop, Dave can see the campaign in the Role Manager.
  • He adds the role members to the Opt-In role of his ECM email campaign.
  • Dave sends emails to the Salesforce® contacts from Sitecore ECM.

Getting Started

If you want to install S4S please check the minimum requirements first.

S4S Basic Minimum Requirements


  • A Salesforce® instance able to install packages and use the Partner API (typically Enterprise, Unlimited or Performance Editions)
  • For Developer and Sandbox Editions S4S will work for ten years without licensing (and 30 days against a Salesforce® production edition).
  • For the Professional Edition (which does not have sandboxes or Partner API access out-of-the-box), S4S will work for 30 days in production. Professional Edition does not support APEX classes and triggers for native user name and password automation.


  • S4S supports all the latest releases of Sitecore. It has been tested on all Sitecore versions since 6.0.2 Rev. 090507 (Recommended minimum).
  • The Web Forms for Marketers module is not required but WFFM related functionality will not work without it.
  • Access to the websites configuration files is required during installation.
  • Note: FuseIT offer free installation assistance to Sitecore partners and prospective customers.

S4S EXM Minimum Requirements

Unlike S4S, this optional module does not support all versions of Sitecore. Please contact us for more details.

Licensing Options

FuseIT provide a range of licensing options to best match your needs. Please navigate through the flow chart to determine the license you require. We offer both perpetual and subscription payment models.

Get the Latest Evaluation

Contact us and tell us your Sitecore version. We will provide a download link to a full version of S4S that works against your Salesforce® Sandbox or Developer Edition.

Time in New Zealand

Our Saturday is Friday in the US

Ready to join the integration revolution?
Get started and enjoy the benefits sooner