IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
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.
Tracking within Progress Sitefinity Digital Experience Cloud is accomplished by collecting and sending information for customers interactions. Each customer interaction consists of the following three types of data (or a subset of them):
Progress Sitefinity Digital Experience Cloud connector uses the interaction data model to collect data. The sentence is the data unit that holds the information of what activity was completed on the website, by whom, and when. An interaction is comprised of:
Following is an example of an interaction sent by the connector to the Progress Sitefinity Digital Experience Cloud when a contact visits a certain page:
Subject: User Id Object: Page URL Predicate: Has Visited SubjectMetadata: FristName, Email ObjectMetadata: PageTitle, IsPagePersonalized
A separate metadata submission request, as mentioned above, may be of two kinds – subject and object. The model of the subject metadata request contains the subject identifier and a collection of key and value pairs, holding the data related to this subject. The model of the object metadata request contains the object identifier, the predicate on which the tracking occurred, and of course – the collection of key and value pairs holding the data related to the object.
SubjectMetadata: FirstName, Email ObjectMetadata: PageTitle, IsPagePersonalized
Very often, when users first arrive on a website, their identity is unknown. To track contact interactions, the Progress Sitefinity Digital Experience Cloud connector maintains a tracking ID of the contact until the moment the contact's identity is recognized by the connector. This most often happens when contacts log in their accounts. At the moment of logging, a subject mapping is sent to the Progress Sitefinity Digital Experience Cloud and thus Progress Sitefinity Digital Experience Cloud knows that all records associated with this specific tracking ID are related to the actions of the ID of the contact who is logging in. From this point on, the connector uses the user ID for associating actions to this contact. Once the contact logs out, the connector gets back on using the tracking ID already related to this specific contact.
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