Collect data through the connector


Tracking within Sitefinity Insight 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):

  • Send interactions that describe contacts actions on the website.
  • Send additional data (metadata) related to the objects or subjects in the tracking scenarios.
    Sending of metadata may be as a part of the interaction or as a separate request.
  • Send subject mappings, that is, relate two subjects that the system has recognized as representing one and the same contact.

Send interactions

Sitefinity Insight 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:
  • Subject – the identifier of the visitor who performed the action.
  • Object – the entity which is the target of the executed action.
  • Predicate – the name of the action (the verb).
  • Additional data about the subject or the object. This data is optional and consists of key-value pairs.

Following is an example of an interaction sent by the connector to Sitefinity Insight when a contact visits a certain page:

Subject: User Id
Object: Page URL
Predicate: Has Visited
SubjectMetadata: FristName, Email
ObjectMetadata: PageTitle, IsPagePersonalized

Send metadata

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

Send contact mappings

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 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 Sitefinity Insight and thus Sitefinity Insight 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.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Get started with Integration Hub | Sitefinity Cloud | Sitefinity SaaS

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.

Web Security for Sitefinity Administrators

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.

Foundations of Sitefinity ASP.NET Core Development

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.

Was this article helpful?