The Save Campaign to Sitecore step initiates a callout from Salesforce to your Sitecore instanceThere are several instances where Salesforce calls into (consumes) an S4S web service hosted on the Sitecore server. Typically this happens when a Salesforce operator clicks on a Sitecore related button. Examples are the "Get Sitecore Analytics" button, "Get Sitecore Page Visits" button or "Save to Sitecore" button. These examples are associated with the S4S Analytics functionality in Salesforce.
If the button functionality fails, it is like the problem will be network related.
- If the Sitecore instance is behind a firewall, your network administrator will have to create a rule allowing callouts from Salesforce. In our experience, the number of IP addresses that these callouts originate from is very limited, most likely one of two possible IP addresses, depending on region of your Salesforce org.
- The best place to determine the SF address(es) is by examining firewall logs or, if traffic is getting through to IIS, through the IIS logs.
This The IIS log entries above is an example of a successful callout from Salesforce at IP 182.50.78.8 to the local instance of Sitecore. In this case, from APNIC region. When the SF Salesforce to Sitecore callout is successful, these lines in the IIS log are generated immediately after initiating a Save Campaign Sitecore related button click action in Salesforce.
You can confirm SF IP Salesforce IP addresses against their lists here. We have found that only a very small subset of these IP address ranges are used for SFDC callouts, and we suggest using rules only for the specific IPs being used in your implementation.