What do the facets mean in Sitecore XConnect?
Facets are piece of information that enriches a contact or an interaction. For contacts, facet include their full name, and address, other contact details. For interactions, facets might include the geographic location of the interaction happened. Each facet may contain: Few pre-defined facets are Personal Information, Email, Avatar, Addresses.
What happens if Sitecore analytics is not enabled?
If anyone of these is null, Sitecore won’t start the Tracker. If the Sitecore.Context.Site is null or Site.Tracking ().EnabledTracking is false, Sitecore will throw a Debug Log of “Cannot start tracking, analytics is not enabled for site”
Which is an example of an interaction in Sitecore?
In the following example, an interaction with a single goal is added to a new contact, Interactions includes Facets are piece of information that enriches a contact or an interaction. For contacts, facet include their full name, and address, other contact details.
Which is default hostname for Sitecore analytics tracker?
The Analytics.ClusterName which is set in the Sitecore.Analytics.Tracking.config needs to be a legitimate, resolvable hostname. The default “default-cd-cluster” is not enough to promote a working solution. This value has to be a DNS name that all Sitecore Servers can reach (e.g. cd.cluster.domain.com for example).
What’s the difference between XDB and Sitecore XConnect?
Sitecore xConnect overview – Contacts, Interactions, Facets. When sitecore 9 got introduced I felt that xDB got replaced with xConnect in sitecore 9 and assumed xConnect is a logical collection of databases to store our website interactions, all other user specific data. After exploring came to know that xDB is different from xConnect.
How does XConnect tracker and facet keys work?
Facet keys are case sensitive. Tracker is responsible for tracking a contact’s activities on your website and submitting that interactions data to xConnect at the end of the each session. xConnect and the tracker both works together but they are separate components. xConnect Client API is the only possible way to work with user experience data.