Universal Tracker Processing service

Abstract

Overview of Sitecore Universal Tracker Processing supported infrastructure, references, scaling, and privacy and security.

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 name

Connection string name

Type

Port

Notes

Universal Tracker database

N/A

SQL

The connection string is located in the <root>\sitecore\Sitecore.Tracking.SqlServer\Config\config.xml configuration file.

Application roles

Role name

Connection string name

Type

Port

Notes

xConnect Collection service

ServiceUrl

HTTPS

443

The 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 name

Connection string 

Type

Notes

xConnect Collection service

ClientCertificate

Certificate

The 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.