Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This can be useful to identify xDB contacts that are coming from an external system such as Salesforce Marketing Cloud that have not been identified originally through the S4S save action on a form. The Salesforce Marketing Cloud campaign would have a click thorough in the sent email which contains a query string parameter that uniquely identifies the associated Salesforce object such as a Contact or Lead. The pipeline then perform performs the following steps:

  1. Find the unique identifier in the query string. If no unique identifier is found the pipeline finishes.
  2. Try to match a Salesforce object with the unique identifier. If no matching object is found then the pipeline finishes.
  3. Resolve the Salesforce object to an xDB contact.
  4. Populate the Sitecore and S4S facets with the data from the Salesforce object.
  5. Create the link in Salesforce between the xDB contact and Salesforce object to enable Analytics to be pushed to Salesforce.
  6. Update the S4S facet with the data that has been mapped in Salesforce from within S4S personalization

...

The pipeline consists of a number of processors that need to be configured. In addition there are processors that can be commented out if not required e.g. if you only ever need to find the associated Salesforce Contact then the processors to find Salesforce Leads and resolve the xDB contact from a Salesforce Lead  Lead can be commented out.

This pipeline is disabled by default. To enable the pipeline uncomment out the startTracking pipeline in the S4SAnalytics.config configuration file.

...