NOTE: Sitefinity Digital Experience Cloud (DEC) was renamed to Sitefinity Insight as a part of the Sitefinity 13.0 release. However, Sitefinity CMS and its documentation prior to version 13.0 continue using the former name - Digital Experience Cloud.
You connect each Sitefinity CMS instance separately and to a specific data center. If you are working in multisite mode, you can choose a specific data center to track each of the sites. That is, to track the sites separately.
Prior to connecting your Sitefinity CMS instance to Digital Experience Cloud you must first specify the desired DEC deployment URL. The URL determines the DEC API server location which will be used for storing and querying your instance-specific information.
The DEC API server location must correspond to the location specified, when your DEC account has been created. By default, Sitefinity CMS is configured to connect to the DEC deployment, hosted in the US. If you have created your DEC account in the US, you can skip this step and proceed to the Connect to DEC section below.
To specify the desired DEC deployment address:
Once you configure the desired DEC deployment address you must proceed by connecting to Digital Experience Cloud by providing your DEC credentials. To connect:
IMPORTANT: Progress Sitefinity Digital Experience Cloud uses these credentials to make API calls to the server. Therefore, we recommend that you use a DEC account, specifically created for this purpose, instead of using a personal account.
NOTE: By clicking Connect, you accept the terms and conditions for working with DEC.
As a result, you can see the connector details and usage statistics.
NOTE: By default, Sitefinity CMS-tracked data is labeled as Website. In Digital Experience Cloud, you can see all data sources reporting to your data center in the data center's Data integration tab page. You can modify the connection name and thus the label of the Sitefinity data source by navigating in Sitefinity to Administration » Settings » Advanced settings » DigitalExperienceCloudConnector and editing the value in the Connection name field.
In case you lose connection between Sitefinity CMS and DEC, to troubleshoot the problem, make sure you investigate the following potential issues.
Login to your server to validate the connectivity to DEC.
You must modify your system’s firewall settings. Make sure the outbound internet connectivity of the Sitefinity CMS server is not restricted for the following addresses:
In addition, make sure that the access to the DEC deployment URLs is not restricted:
Try to login to DEC with your current user. In case access is denied, enter the correct credentials in the DEC connector configuration.
NOTE: Another reason for not seeing the data center in the Data centers dropdown is that you are not logged in with the proper user that has permissions to work with this data center.
In case you are working with multiple websites on one Sitefinity CMS instance, you can select which specific Sitefinity CMS site(s) to track. For example, you may want to exclude from your data a subset of sites that are not relevant to your marketing department and their data can dilute the results from the other sites you want to track. In addition, you can isolate customer journey data for individual websites powered by a single Sitefinity CMS instance in specific data centers in Digital Experience Cloud. Thus, digital marketers can get data-driven insights that are specific to the brand or website they manage.
By default, all Sitefinity CMS sites in multisite environment are tracked. To select one or more specific sites to track and in which data center to store site data:
NOTE: Once you associate a site with a data center, you cannot associate it with another data center. You can, however, associate more than one site with one and the same data center.
Once you are done, the selected sites automatically start sending data to Progress Sitefinity Digital Experience Cloud.
To track Sitefinity CMS websites and their sub-domains, you configure the tracking cookie sf-data-intell-subject to be visible to all relevant applications:
As a result, the cookie is visible to all systems hosted on sub-domains, for example sitefinity.com and partners.sitefinity.com.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity