Tracking within Sitefinity Insight is accomplished by collecting and sending information for customer interactions. Each customer interaction consists of the following three types of data (or a subset of them):
Following is an example of an interaction sent by the connector to Sitefinity Insight when a contact visits a particular page:
Subject: User Id Object: Page URL Predicate: Has Visited SubjectMetadata: FristName, Email ObjectMetadata: PageTitle, IsPagePersonalized
As mentioned above, a separate metadata submission request 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 Sitefinity Insight connector maintains a tracking ID of the contact until the moment the connector recognizes the contact's identity. This most often happens when contacts log in to their accounts. At the moment of logging, a subject mapping is sent to Sitefinity Insight. Thus Sitefinity Insight knows that all records associated with this specific tracking ID are related to the actions of the ID of the contact 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.
When you use the Sitefinity Insight connector, you have an option to send additional data to feed advanced content analysis. This is a prerequisite to use the Content recommender feature. For more information, see Content recommender
This data consists of the following:
NOTE: Only publicly available fields are sent. If any of the listed items have permissions that make them not public, Sitefinity CMS does not send them to Sitefinity Insight. The same applies to fields of dynamic content types – only the public fields are sent.
NOTE: If you change the permissions after the data has already been sent to Sitefinity Insight and you want to make sure that newly protected data is no longer stored in Sitefinity Insight, you must sync the data to Sitefinity Insight after the change. To do this, disable and then re-enable the content tracking, as described in the procedure Connect to Sitefinity Insight » Configure content tracking.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.
This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important