Date: Fri, 29 Mar 2024 08:13:37 +0000 (UTC) Message-ID: <557464994.19.1711700017026@0012a8d4ca57> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18_1014477189.1711700017025" ------=_Part_18_1014477189.1711700017025 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This pipeline enables an xDB contact to be resolved from a Sales= force object identified by a particular query string parameter in the page = request URL.
This can be useful to identify xDB contacts that are coming from an exte= rnal system such as Salesforce Marketing Cloud that have not been identifie= d originally through the S4S save action on a form. The Salesforce Marketin= g Cloud campaign would have a click thorough in the sent email which contai= ns a query string parameter that uniquely identifies the associated Salesfo= rce object such as a Contact or Lead. The pipeline then performs the follow= ing steps:
When the previous steps have been completed the Sitecore content will pe= rsonalize based on the xDB and the associated S4S facet data.
|
Note: This pipeline can use se= veral Salesforce API calls to find the associated Salesforce object, determ= ine if the link between the xDB contact and the Salesforce object is presen= t, create the link if not present, get the field mapping for personalizatio= n and populate the S4S facet from those fields. Consider an alternative sol= ution if you frequently dispatch large email campaigns and your current API= consumption is high. |
The pipeline consists of a number of processors that need to be configur= ed. In addition, there are processors that can be commented out if not requ= ired e.g. if you only ever need to find the associated Salesforce Contact t= hen the processors to find Salesforce Leads and resolve the xDB contact fro= m a Salesforce Lead can be commented out.
This pipeline is disabled by default. To enable the pipeline uncomment t= he startTracking pipeline in the S4SAnalytics.config&= nbsp;configuration file.
<star= tTracking> <processor type=3D"FuseIT.S4S.WebToSalesforce.Pipelines.StartTracking.= ResolveXdbContactFromSalesforce, FuseIT.S4S.WebToSalesforce" patch:after=3D"processor[@type=3D'Sitecore.Analytics.Pipelines= .StartTracking.TrackerInitialized, Sitecore.Analytics']"> </processor> </startTracking>