Sitecore Experience Platform

Browser and session compatibility in FXM

Abstract

An overview of how FXM tracks contacts on different browsers.

Because of the differences between browsers, FXM cannot always track contacts with the same ID across multiple sites.

The following tables list the currently supported options:

CORS support in XMLHtmlRequest 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

Edge

Y

Y

N

Y

Y

Safari on desktop

Y

Y

N

N

Y

Safari on iOS

Y

Y

N

N

Y

Firefox

Y

Y

N

Y

Y

IE 10,11

Y

Y

Y

Y

Only as subpath

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

Edge

Y

Y

Y

N

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

Firefox

Y

Y

Y

Y

IE 10,11

Y

Y - but not for page root

Y (CORS + P3P)

Y (CORS + P3P)

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.