Download presentation
Presentation is loading. Please wait.
1
Sitecore to Salesforce Integration
S4S Demo This is a technical discovery of S4S, the FuseIT Sitecore to Salesforce integration. The ideal audience for this presentation are developers, solution architects or any other person who wants to understand the connector at a technical level [click]
2
Fuse Information Technology Ltd
Enterprise integrations driving business profitability Before we start the walkthrough, I’d like to let you know who we are and how we know about the Salesforce to Sitecore integration space [click]
3
FuseIT Incorporated 1992 60 global customers serviced by 10 specialists Salesforce Consulting and ISV Partner Integration products Custom development (mainly US based clients) Sitecore Technology Gold Partner Some Sitecore web development HPE IMAP Gold Partner HPE Records Manager (TRIM) integration FuseIT has been around since 1992 but we really focused on building integration products after we became Salesforce and Sitecore partners in Although we are based in New Zealand our perspective has always been global. Our team of 10 is very experienced and have been with us many years. Staff turnover is low, probably due to our location being in the sunniest part of New Zealand [click] We do a lot of work in Salesforce with several clients in the States, mainly in California where the times zones work well for us. [click] We are well known in the Sitecore space having helped sign deals with large customers who insisted on Sitecore having a robust Salesforce integration. [click] We also work with HPE Enterprise on some integrations with Sitecore and Salesforce [click]
4
Selection of Customers
Our customers are from across the globe and in many verticals. They include Fortune 500 companies like American Express and United Health Group. [click]
5
Where are our customers?
Miller Group Microsystems United Health Group Ruuki Stratasys Allianz American Express Stanley Black & Decker Sydney Airport
6
S4S SooT M4S S2T T4S Connector Suite Connectors
We have many enterprise connectors between different technologies. Note that our G4S and S4S connectors are very similar but S4S has Sitecore specific features. Our other key Sitecore connector is called SooT which extends Sitecore with the secure document handling. It does this by integration with HPE Records Manager, also known as TRIM [click] Sitecore and TRIM, and ASP.NET applications are all built on Microsoft stacks [click] We also have M4S that works well with S4S and integrates Sitecore to MongoDB. We will see more on that soon [click] But for now, lets look at why we need to integrate at all T4S
7
S4S Business Rewards Quickly create web forms and map them to Salesforce objects Auto-add web leads to nominated Salesforce campaigns Capture browsing analytics in Salesforce (know your customer) Better filter and identify Salesforce leads - targeted campaigns Personalize web content from Salesforce Rationalize Salesforce licensing (save $150 per month per user) Centralize governance, administration and oversight Create a single source of data Complete, Relevant, Accurate, Timely, and Accessible data So obviously S4S solves these problems and quite a few more like quickly mapping Sitecore web forms to Salesforce, and, at the same time, adding them to a nominated campaign. Say your company hosts a round table in Vegas and needs to promote the event on the company website. In Sitecore, a registration from can be quickly created and mapped to the Salesforce leads object and a nominated campaign. Any registrant completing the form, will become a new lead in Salesforce and added to the selected campaign. This process saves a lot of time and can be done entirely from Sitecore. [click] When a Sitecore form is completed we can choose to push the Sitecore analytics, visit by visit, into Salesforce. [click] All this data in Salesforce means we have a much better idea of who we are talking to. It also means we have more criteria to create accurate reports and campaigns in Salesforce [click] Its possible to personalize implicitly and explicitly and we will cover this shortly [click] We can create web portals [click] Control, administer and track web functions from within Salesforce [click] Make Salesforce the data source so any data that Sitecore produces is pushed to Salesforce [click] The connector has been built so Sitecore developers can complete projects faster and without risk. We connect our FuseIT developers directly to your developers to make implementation as easy as possible
8
Web Forms for Marketers Email Experience Manager
What is S4S 2 S4S Connection Interface Users Contacts Roles Connection Interface Accounts Profiles Partner API Opportunities Reports S4S Documents Leads Custom Forms Products Web Forms for Marketers Campaigns Cases Experience Manager Custom Objects Instant bi-directional connectivity
9
Web Forms for Marketers
Create and Update Salesforce Objects Contacts Accounts Partner API Opportunities S4S Documents Visitor submits a web form Leads Update custom objects Products Web Forms for Marketers Campaigns Cases Cases First, the basics. Here is the process when a visitor submits a web form to create a new Salesforce object. Walkthrough Custom Objects S4S Wizard maps forms to Salesforce Upload documents to Salesforce attachments
10
Web Forms for Marketers
Create Salesforce Leads or Contacts Sitecore behavior is visible in Salesforce Contacts Contacts Form data Goals reached Accumulated goal points Pages visited count Profile Cards Pattern Cards Partner API S4S Reportable Visitor submits a web form Leads Actual pages visited Duration on each page Date of visit Visitor IP View on demand Web Forms for Marketers Sitecore saves navigation behavior Sitecore XDB For “people” objects, the process pushes the Sitecore analytics. Walkthrough
11
Web Forms for Marketers
Implicit Personalization from Salesforce Control personalization from Salesforce Contacts Contacts Form data Goals reached Accumulated goal points Pages visited count Profile Cards Pattern Cards Partner API S4S Leads Sitecore Visitor ID Web Forms for Marketers Sitecore XDB Once the intelligence is in Salesforce, we can push the data back to Sitecore so returning visitors will get a sales driven web experience. Walkthrough
12
Web Forms for Marketers
Implicit Personalization from Salesforce Sitecore renders a tailored experience Contacts Contacts Partner API Form data Goals reached Accumulated goal points Pages visited count Profile Cards Pattern Cards S4S Leads Sitecore Visitor ID Web Forms for Marketers Sitecore XDB Implicit personalization means that Sitecore will change the returning visitor’s experience as they continue to browse. This allows the most recent behavior to be surfaced in Salesforce. Walkthrough
13
Sitecore Portal and Explicit Personalization
Single data source Users Contacts Roles Profiles Roles Partner API Control website experience from Salesforce Profiles S4S Leads Members of your sales team or privileged customers can access Salesforce data via dedicated portal pages only accessible after authentication. Walkthrough
14
Tell S4S to Authenticate from Salesforce
With S4S you can choose to overrides the ASP.NET membership, role and profiles providers that Sitecore natively uses for authentication. Looking at the ASP.NET login control you can see that Salesforce contact credentials can be accessed by adding the Salesforce domain name prefix to the username. After that, you can deal with the logged in user exactly as you would deal with any Sitecore that would exist in the core database. Note that the user details do not exist in Sitecore, only Salesforce. In the Sitecore role and user manager accessed from the Sitecore Desktop, the Salesforce contract will appear normally. ,
15
S4S Email Experience Manager
Optional add-on module for Sitecore EXM users Overcome Salesforce limits – 500/1000 s per day Compile marketing lists in Salesforce Dispatch choices: Dispatch directly from Salesforce via EXM or Send lists to EXM for dispatch from Sitecore Track recipient behavior in Salesforce The only commercial extension to S4S is the E4S EXM module which supports the Sitecore Experience Manager. Natively Salesforce only allows up to s a day to be sent. Most companies need to extend this capability and using Sitecore EXM is a powerful way to do it. The latest versions of Sitecore EXM can process huge numbers of s The S4S EXM module uses standard Salesforce campaigns as a starting point and allows operators to dispatch s entirely from Salesforce or just send them to Sitecore for dispatch there. As you would expect, the recipient behavior, whether they ignore or open s, or advance to the website from the is all tracked back to Salesforce. [click]
16
S4S EXM Functionality S4S EXM Reportable Partner API
and website behavior in the campaign member record Extend the campaign capabilities of Salesforce Contacts Opt Out Goals reached Accumulated goal points Pages visited count Actual pages visited Duration on each page Date of visit S4S EXM Reportable Partner API Leads Campaigns Experience Manager Sitecore XDB Walkthrough
17
Constraints Imposed by Salesforce
Consider API Request Limits when architecting your solution If limits are exceeded, API is closed for 24 hours Enterprise edition 5 licenses - limit is 5,000 requests per day 150 licenses - limit is 150,000 requests per day 15,000 licenses - limit is 1,000,000 requests per day I want to mention API limits that are imposed by Salesforce as architects need to be aware of them when designing a solution. The consequence of the exceeding the limits is complete API closure for 24 hours so you would not want to push data to Salesforce every time a visitor went to a new web page. Many of the invisible features of S4S relate to providing tools to help developers keep the API count down The API limits relate to the number of Salesforce users you have and the Salesforce edition. For Enterprise edition, with 150 licenses you get around 150,000 API requests per day [click]
18
Caching Features Enterprise caching
Schema (metadata): Cache Salesforce object fields and data types to significantly improve performance and reduce the API count Entity: Cache Salesforce sObjects with configurable expiration times Configure S4S to use System.Net.Cache Query result paging support Batch results to Salesforce to reduce API count Automatically bulkifies operations to and from Salesforce Configure S4S to use MongoDB advanced caching Advanced synching engine is highly configurable Significantly reduces Salesforce API calls Very fast login as there is no requirement to go to Salesforce MongoDB caching doubles as Salesforce real time offline storage Enables the bulk distribution of Salesforce data using REST S4S has many mechanisms to reduce the number of API calls and improve performance. Foremost is Schema Caching where standard and custom objects and fields in Salesforce are cached. When you retrieve data from Salesforce, Entity Caching localizes the data so additional calls for the same records will not consume or increment the API count. [click] Sitecore uses System.Net.Caching and it can also be used by S4S to store query results like when paging through web grids showing lists of records [click] Calls to Salesforce can be batched where, instead of retrieving a single record, S4S will pull several thousand on the same call so they can be scrolled through in Sitecore without additional API calls. S4S methods let developers retrieve multiple objects in the same API call. [click] We covered M4S that lets you cache to MongoDB. System.Net.Caching will cover 99% of your needs so we only recommend M4S if you have additional data needs like offline access or super fast login. [click]
19
Other Features Status page at Provides full data type mapping Standard Salesforce objects are strongly typed Use the T4 generator to create strongly typed classes for custom objects or Access custom objects and fields directly by name Supports proxy servers for connection to Salesforce Handles Salesforce case insensitivity Utilizes standard Sitecore logging Fails gracefully if Salesforce goes offline or becomes inaccessible Predictive recursive descent parser processes complex SOQL queries Establishes and controls session state Can establish sessions using SessionId and ServerUrl for embedding in customers Salesforce instances OAuth support There are many other features built into the connector. The status page is useful if you need to know S4S is till operational and the connection to Salesforce is working. Full data type mapping is a large part of S4S. Standard objects and fields are strongly typed in ASP.NET out of the box. Custom fields or objects can be reference by string name or you can use our SFDC Explorer tool to generate strongly typed C# classes to develop against. [click] Other important features include integrated logging with Sitecore, and failing gracefully when Salesforce goes down. You can get an idea of the extensive development of S4S by reviewing the release notes on our website. [click]
20
Email Automation Integration
Salesforce Automation Systems Marketing Cloud aka Exact Target (owned by Salesforce) Pardot (owned by Salesforce) Eloqua, Marketo, Hubspot, Act-On etc. Sitecore Integration Web form and personalization data S4S Salesforce Map Salesforce fields to the targeted automation systems [click]
21
S4S Installation Salesforce
Unlimited and Enterprise Editions. Requires a dedicated API user Install packages depending on functionality Sitecore Usually installed by Sitecore Partner or in-house Sitecore developers Technical assistance from FuseIT is included (if needed) Timing Considerations Developers need to absorb, design, implement, test and deploy Test against production early - allows time to tweak architecture [click]
22
What Next Download now and start development Determine which License
Based on domain names, Salesforce instances and need for S4S EXM Complete Legalities Customer submits License and Maintenance Agreement Partner and customer submit Technical Form Customer submits Purchase Order Form Invoicing FuseIT invoice Production license is issued when payment is received [click]
23
Sitecore Salesforce Connect
Compare Connectors Salesforce Web to Lead or Case FuseIT S4S Free JavaScript code that creates Salesforce leads and cases Exposes Salesforce Org Id to the public via “View Source” Paid connector with many OOTB features Enterprise proven professional product Ongoing upgrades support new Sitecore releases Salesforce development support from FuseIT Works with all Salesforce standard and custom Can be installed in any Salesforce instance with API access Includes Starter kit and implementation code examples Includes an operational status page to show configuration Full error reporting to the Sitecore log file Full Sitecore EXM support with the S4S EXM module No performance issues and tools to optimize performance Secure password encryption on in Salesforce Multiple offline Salesforce backup features Partner API is easy to configure, proven over time, and optimized for large data sets Uses Salesforce packages so easy to manage Salesforce .NET SDK Free ASP.NET example code for connecting to Salesforce Hefty development effort required to learn and debug integration Sitecore Salesforce Connect Free open source application (no care and no responsibility) No upgrade path to support new releases of Sitecore Sitecore centric features. No OOTB analytics support. Works with Salesforce contacts (and campaign members) only Can only be installed in Salesforce production instances No ongoing support, code examples, error trapping or reporting Walkthrough
24
FuseIT SFDC Explorer Tool to help Sitecore developers write advanced integration functionality. Used by around 2000 users globally. Download and see more here. SOQL Query: Run SOQL queries against Salesforce. The results can be exported to an Excel file. Relationships: View Salesforce object relationships. Find Entity: Search for the Salesforce object associated with a Salesforce ID. Apex Tests: Run Apex tests synchronously or asynchronously. Show the code coverage for the selected tests along with what tests have passed and failed. Test log is can be viewed for the selected tests. Apex Test's Queued: Shows the queued Apex tests when the tests are running asynchronously. Apex Logs: Allows users to view the Apex logs for the Salesforce instance. Data Export: Iterate through a data export and copy the selections to a nominated server. Anonymous Apex: Run apex statements anonymously and show the output of the statements. WSDL Parser and Apex Generator: Lets developers select only the Apex methods needed, generate the Apex classes, then publish the classes.
25
S4S Overview Rock Solid Connection Engine
Customer driven feature additions since 2009 Proven by enterprises companies Software releases track all Sitecore and Salesforce versions Quick to market Developers do not need to know Salesforce Features to mitigate Salesforce API constraints Guidance from FuseIT ensures project success Maintenance plans that include updates and support A quick review S4S is an enterprise grade connector that has overcome many of the with [click]
26
Further Information www.fuseit.com
Terry Humphris Annastashia Cambridge Daniel Ballinger YouTube Channel CEO Sales & Marketing Executive Sitecore Developer and Salesforce MVP Search for FuseIT S4S [click]
27
MongoDB as a Super Cache
M4S as a Super Cache S4S can use the Salesforce to MongoDB connector (M4S) Advanced caching engine for Salesforce – improves performance Significantly reduce the API calls to Salesforce Doubles as offline storage for Salesforce Configurable for real time synchronisation Bulk access Salesforce data via RESTful services Bulk process Salesforce data by .NET applications Transparently handles custom objects and fields View Salesforce data with MongoDB client interfaces Use MongoDB toolsets to extract business intelligence M4S is a new product that works with S4S. It serves as an advanced cache and reduces the impact when Salesforce goes offline. Essentially M4S instantiates Salesforce into a MongoDB instance so any calls to the Salesforce cloud become local calls – a real boost in performance. [click] M4S helps reduce the number of calls to Salesforce. [click] Because your key data is in MongoDB, you can still access it when Salesforce goes down. [click] You can configure M4S to localize all, or only some, Salesforce objects. M4S will work with or without scheduled synchronization. MongoDB is updated whenever data is pulled from Salesforce. [click] Because there are no API constraints bulk processing is possible [click] MongoDB deals easily with the dynamic nature of the Salesforce schema [click] And you can explore your Salesforce data with standard MongoDB interfaces like MongoVUE or RoboMongo. Alternatively you can use one of the Big Data tools like Spring Data, GridGain and Jaspersoft to capture Business Intelligence. [click]
28
S4S with M4S S4S M4S MongoDB improves performance and lowers API count
Web Services Oracle SQL Server M4S can share limitless data to external systems S4S Partner API M4S M4S uses a scheduled task to synch selected Salesforce objects to MongoDB MongoDB improves performance and lowers API count
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.