Sitecore's FXM Browser Update

by Dustin Collis, Partner and Chief Information Officer at NavigationArts, now an EPAM company

Creating a 360-degree view of a customer has been the highly sought after Holy Grail of digital marketing for the last decade. Achieving a full view of a customer and their interactions across multiple digital touch points while unifying their dialogue with the brand has shown to increase engagement, revenue, and satisfaction. To do this, Sitecore created an integrated tool called the Federated Experience Manager (FXM).  

Sitecore’s elegant Federated Experience Manager (FXM) has enabled end-to-end engagement value tracking of a user journey across disparate sites and applications not on Sitecore. Like all things that live on the client side, FXM is also affected by the nuances of browser standards, cookies, and cross-domain scripting. While the value proposition is in full force for any marketing group, expectations should be set correctly.

In this post on the Sitecore documentation site (still in Beta), you’ll see that FXM has differentiated capabilities depending upon which browser a user has selected and if you are tracking a journey cross-domain. 

Table 1

  CORS support in XMLHttpRequest Object CORS with cookie sending support  Requires P3P headers for cross domain requests Third party cookie access enabled by default Session cookies path support
Chrome y y n y y
FireFox y y n y y
Safari on desktop y y n n y
Safari on iOS y y n n y
IE 8, 9 n (use XDomainRequest with restrictions) n y y only as sub path
IE 10, 11 y y y y only as sub path



Table 2

  External site on same domain External site on same domain under path External site on sub domain External site on separate domain
Chrome y y y y
FireFox y y y y
Safari on desktop y y y n - fallback to unique contact per site with CORS + cookie setting in ext. domain
Safari on iOS y y y n - fallback to unique contact per site with CORS + cookie setting in ext. domain
IE 8, 9 y y - but not for root page y (CORS + cookie setting in ext. domain) n - fallback to unique contact per site with CORS + cookie setting in ext. domain
IE 10, 11 y y - but not for root page y (CORS + p3p) y (CORS + p3p)

 

The tables above, from the Sitecore site, identify specific features and capabilities depending on a number of facets. The key outcome listed in the post by Sitecore is:

“If the external site and the Sitecore site are hosted on different domains:

  • For Chrome and Firefox – FXM can successfully track the same contact across both websites.
  • For Safari and iOS or any version of IE – FXM assigns each contact a unique contact ID per website.”