ÃÛ¶¹ÊÓƵ

trackingServer

ÃÛ¶¹ÊÓƵ collects data on your site by receiving an image request generated by the visitor. The trackingServer variable determines the location an image request is sent. If this variable is not defined correctly, your implementation can experience data loss.

Edge domain using the Web SDK extension

The Web SDK uses Edge domain to handle both Tracking Server and Secure Tracking Server. You can set the desired Edge domain value when configuring the Web SDK extension.

See Configure the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK extension in the Web SDK documentation for more information.

Edge domain manually implementing the Web SDK

Configure the SDK using edgeDomain. The field is a string that determines the domain to send data to.

alloy("configure", {
  "edgeDomain": "data.example.com"
});

Tracking Server using the ÃÛ¶¹ÊÓƵ Analytics extension

Tracking Server is a field under the General accordion when configuring the ÃÛ¶¹ÊÓƵ Analytics extension.

If this field is left blank, it defaults to [rsid].data.adobedc.net.

s.trackingServer in AppMeasurement and the Analytics extension custom code editor

The s.trackingServer variable is a string that contains the location to send data.

Considerations for determining the value for trackingServer

You can choose to use ÃÛ¶¹ÊÓƵ’s tracking server domains (e.g. adobedc.net) or you can go through a special process to setup a tracking server that matches your sites domain (e.g. data.mydomain.com), also known as a CNAME implementation. Having a trackingserver that matches your site domain may have some benefits depending on other aspects of your implementation. When the tracking server does not match the domain of the current page, cookies set by AppMeasurement must be set as third-party. If the browser does not support third party cookies, this mismatch can interfere with certain Analytics functionality:

First-party cookies

If you use a first-party cookie implementation, it is likely that someone in your organization has already completed the first-party cookie process. See First-party cookies in the Experience Cloud in the Core Services user guide for more information on the first-party cookie process.

The individual who initially configures the first-party cookie implementation also defines the domain and subdomain used. For example:

s.trackingServer = "data.example.com";

Third-party tracking server

If you use a third-party cookie implementation, the value for trackingServer is a subdomain of data.adobedc.net. For example:

s.trackingServer = "example.data.adobedc.net";

Pick a subdomain unique to your organization, unlikely to be picked by another organization that uses ÃÛ¶¹ÊÓƵ Analytics. The visitor namespace assigned to your organization is recommended. Make sure that all implementations in your organization use the same tracking server. It can be helpful to maintain this information in a solution design document.

Your organization may already be using a 3rd party tracking server in the sc.omtrdc.net or 2o7.net domains. These were primarily used in previous versions of ÃÛ¶¹ÊÓƵ Analytics and are still valid.