Universal Tracker Processing service

Version:

The Universal Tracker Processing service is responsible for submitting the data collected by the Universal Tracker Collection service. The service performs pre-filtering, enrichment, and post-filtering on all analytics data before submitting to xConnect.

Supported infrastructure

You can host the Universal Tracker Processing service on:

Refer to the Sitecore compatibility table for compatible versions.

Note

The Universal Tracker Processing service cannot be hosted as an Azure Web Job.

Reference structure

The Universal Tracker Processing service has its place in the Sitecore reference structure. It can be referenced by other roles, and it can also reference other roles.

Illustration showing the Universal Tracker Processing service's place in the Sitecore reference structure.

Referenced by

The Universal Tracker Processing service is not referenced by other roles.

References

The Universal Tracker Processing service references the following roles:

Storage roles

Role nameConnection string nameTypePortNotes
Universal Tracker databaseN/ASQLThe connection string is located in the <root>\sitecore\Sitecore.Tracking.SqlServer\Config\config.xml configuration file.

Application roles

Role nameConnection string nameTypePortNotes
xConnect Collection serviceServiceUrlHTTPS443The connection string is located in the <root>\sitecore\Sitecore.Tracking.Processing.Engine\Config\config.xml configuration file.

The following client certificates are required in a secure production environment:

Role nameConnection stringTypeNotes
xConnect Collection serviceClientCertificateCertificateThe connection string is located in the <root>\sitecore\Sitecore.Tracking.Processing.Engine\Config\config.xml configuration file.

Privacy and security

The Universal Tracker Processing service handles personal data in the following ways:

  • Reads interaction and event data from the Universal Tracker database. Interactions may include a reference to a known contact identifier.
  • Writes interactions and event data to the xConnect Collection service.
If you have suggestions for improving this article, let us know!