The Federated Experience Manager (FXM) is an integrated part of Sitecore and is enabled by default.
To enable FXM functionality on an external website and track visits to that site:
- You must have installed Sitecore xDB.
- You must have access to the backend of the external website to be able to deploy the tracking script on the website.
- Your Sitecore site and the external site must both have the same type of connection – http or https.
- Your license file controls your ability to use FXM, so you must ensure that the appropriate permission is specified in your license file –
- Ensure that the location of the Temp folder that you can specify in the
FXM.BundledJSFilesPathsetting in the Sitecore.FXM.config file is located within the \Website folder.
- Sitecore xDB Cloud Edition
- Sitecore xDB on-premise
FXM supports these internal Sitecore features:
- Experience Profile
- Experience Analytics
- Experience Editor
- WFFM (MVC)
The following content is deployed externally through the Sitecore content mark-up:
FXM has the following limitations:
- On Internet Explorer 11, to ensure that FXM can process web service requests correctly, the host website must have a top-level domain name.
- The Sitecore website and the external website must use the same application level protocol – http or https.
- Tracking of visits does not work if the external website is a single page application (SPA). If the external website is a SPA, all visits are associated with the single URL.
- You cannot use the same fully qualified domain name (FQDN) for a Sitecore site and a non-Sitecore page or site.
- FXM does not currently support:
- Content testing (M/V and A/B testing)
- Path Analyzer
The FXM module embeds standardized code to external websites to activate the functionality. However, this approach is incompatible with certain website functionalities.
FXM does not support external websites that use:
- Cookie-based authentication to website pages.
- Parts of the HTML page that are loaded using AJAX technologies.
- 302 HTTP redirects for navigation.
- Custom ports. You must use the standard HTTP (80) and HTTPS (443) ports.
In the Experience Editor, placeholder content and personalization does not work if the external website uses:
- Loading parts of the HTML page using AJAX technologies.