Scaling and configuring the Universal Tracker Collection service role

The Universal Tracker Collection service is an optional role that provides an end point for collecting tracking data. Collected data is stored in the Universal Tracker database and submitted to xConnect by the Universal Tracker Processing service.

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 Collection service

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

Scaling option

Supported

Notes

Combined instance

No

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

Standalone instance

Yes

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

High availability and failover

Yes

You can fail over to a passive instance or set up multiple active instances behind a load balancer.

Horizontal scaling for load distribution

Yes

  • You can set up multiple instances behind a load balancer. In this scenario, all clients write to the same Universal Tracker Collection end point. If necessary, each service can write to its own copy of the Universal Tracker database.

  • You can dedicate clusters of Universal Tracker Collection services to a particular purpose. For example, you can set up two clusters of four load-balanced Universal Tracker Collection services to handle requests from different clients.

Default topologies and packages

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