Configure the collection service

Abstract

How to configure the configuration files that control the Universal Tracker collection service.

There are three configuration files that control the Universal Tracker (UT) collection service:

  1. <website_name>\sitecore\Sitecore.Tracking\Config\config.xml

    This configuration file controls how events that public clients submit to the collection service are mapped to the corresponding xConnect events (Sitecore Marketing definition events). If a public event submits data, and the event type is unknown, there is a risk of data loss or improper parsing.

    You can specify additional types by:

    1. creating an appropriate item and publish it according to the Deploy Marketing definitions topic in the Sitecore Installation guide.

    2. adding the published type to the config.xml file, in the <Settings><Sitecore.Tracking><TypeMappings> section. You must add it as a fully qualified name with the syntax AssemblyName.Namespace.ClassName, AssemblyName. For example, use this code to add a type named event:

      <event>Sitecore.XConnect.Event,Sitecore.XConnect</event>

    Clients can now submit HTTP requests with the type event. For more information on configuring and using types, see Configure custom xConnect Models.

  2. <website_name>\sitecore\Sitecore.Tracking.Plugin.Status\Config\config.xml

    This configuration file controls the UT Status plugin, which displays the status page. By default, the setting LocalAccessOnly is set to true,which means the status controller only accepts requests from the local machine. External requests will return an HTTP 404 (not found) error. Set LocalAccessOnly to false to allow external requests.

  3. <website_name>\sitecore\Sitecore.Tracking.SqlServer\Config\config.xml

    This configuration file is a part of UT SQL. It contains the ConnectionString that specifies the connection to the UT SQL  database.  

    Note

    You must specify the same ConnectionString for the collection service and the processing service.