Scaling and configuring the Universal Tracker Processing service

Current version: 9.1

The Universal Tracker Processing service is an optional role that submits contact and interaction data from the Universal Tracker database to xConnect.

Installation

Refer to to the Universal Tracker installation guide, available with each version of the Universal Tracker on the Downloads site.

Scaling the Universal Tracker Processing service

The following table describes the way you can scale the Universal Tracker Processing service:

Scaling option

Supported

Notes

Combined instance

No

The Universal Tracker Processing service cannot be combined with any other role.

Standalone instance

Yes

You can deploy the Universal Tracker Processing service as a standalone role.

High availability and failover

Yes

You can fail over to a passive instance or set up multiple active instances. Load balancing is not required.

Horizontal scaling for load distribution

Yes

  • You can set up multiple instances that read work items from the same Universal Tracker database.

  • In a multi-instance environment, each instance of the Universal Tracker Processing service can be configured to process only interactions coming from a specified list of channels. For example, you could choose to dedicate an instance to processing only web traffic.

Default topologies and packages

The Universal Tracker Processing service role is not part of any default topologies.

Do you have some feedback for us?

If you have suggestions for improving this article,