1:1 Personalized marketing at scale using Sitecore Connect for Salesforce Pardot

 

Sitecore connect for pardot
The 3 pillars of personalized marketing at scale are:

  1. Robust Digital Experience Platform (DXP)
  2. Marketing automation platform
  3. CRM
The key to achieving real time personalized marketing requires breaking data silos by integrating systems, building customer profiles iteratively and across channels, collecting the right data, identifying the right KPIs for measurement of success and aligning KPIs with business goals,

The Sitecore connect for Salesforce Pardot is a Sitecore connector that provides bi-directional syncing of real time interactions tracked across channels by both Sitecore and Pardot. It offers real time personalization using Sitecore based on a number of data facets available in both Sitecore and Salesforce Pardot.

It offers the following features:
  1. Integrate multiple instances of Pardot with a single instance of Sitecore.
  2. On-demand bi-directional syncing of marketing data.
  3. Uses email as a unique identifier between Sitecore Contacts and Pardot Prospects.
  4. Creates new contacts and updates existing contacts.
  5. Personalize Sitecore based on Pardot field values.
  6. Custom tab in Sitecore xProfile for viewing Pardot data.
  7. Custom fields created in Pardot for Sitecore form data, interactions and search keywords.
  8. Custom submit action for Sitecore Forms to post data to Pardot.
  9. Pardot activity types are created in Sitecore Marketing Control Panel as Goals for tracking and attribution.
  10. Custom scheduler in Sitecore for nightly sync.
You can request the connector from Sitecore's Marketplace.


Comments

Post a Comment

Popular posts from this blog

Is Rendered Item Valid XHtml Document Could not find schema information warnings during publish item Sitecore 7.2

Image
Note: Since we now live in the HTML5 world, the simple resolution to any XHtml validation errors is to remove the XHtml validation rules on  System->Settings->Validation Rules->Global Rules item. Sitecore should update it's validation rules to be relevant to HTML5. This make the rest of this post obsolete :). I created a simple approval workflow in Sitecore 7.5 and tried to approve an item for publishing and found a bunch of validation errors in the Validation Results. Most of them were related to the "Is Rendered Item Valid XHtml Document" section which looked like this: The problems were related to violations of the W3C HTML5 recommendation An important note here is: The element containing the character encoding declaration must be serialized completely within the first 1024 bytes of the document. Adding the following xmlns attribute to the Html tag fixed most of the errors: <html lang="en" xmlns="http://www.w3.org/1999/
Read more

Sitecore Tabbed Select Rendering dialog

Image
If you aren't already doing this, you should be! Found an interesting module (unable to find it on Sitecore Marketplace) to show renderings grouped into tabs while using the Select Rendering dialog from page editor. The idea is to go from this: To: The approach is promising with a few updates: Tried implementing it by inheriting from SelectRenderingForm and it did not work. No rendering items were being listed. Had to decompile Sitecore.Client.dll and copy the code from Sitecore.Shell.Applications.Dialogs.SelectRendering.SelectRenderingForm Had to comment the following line in OnLoad  this.Renderings.InnerHtml = this.RenderPreviews((IEnumerable<Item>)renderingOptions.Items); Found a few issues with the styles, could have be an updated style sheet for Sitecore 7.5, but had to add the following attributes to the tabstrip Background="white" Padding="0px" style="position:absolute; width:100%;top:0px" Here is a detailed description of my implementati
Read more

RESOLVED: Solr Exceptions - Document contains at least one immense term in field

If you implemented Solr with Sitecore using Solr 5.x, you may run into the following error when indexing extremely large content in string fields: org.apache.solr.common.SolrException: Exception writing document id <xxxuniqueid> to the index; possible analysis error. Caused by: java.lang.IllegalArgumentException: Document contains at least one immense term in field="<xxxfieldname>" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[10, 9, 9, 10, 32, 32, 32, 32, 32, 32, 82, 84, 82, 83, 32, 70, 97, 99, 105, 108, 105, 116, 121, 32, 10, 32, 32, 32, 32, 84]...', original message: bytes can be at most 32766 in length; got <intgreaterthan32766> Caused by: org.apache.lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes can be at most 32766 in length; got <intgreaterthan32766> This is due to the fa
Read more