trackingServerSecure

Adobe collects data on your site by receiving an image request generated by the visitor. The trackingServerSecure variable determines the location an image request is sent over HTTPS. It also determines the location visitor cookies are stored. 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 Adobe 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"
});

SSL Tracking Server using the Adobe Analytics extension

SSL Tracking Server is a field under the General accordion when configuring the Adobe Analytics extension.

If this field is left blank, it defaults to the value in the trackingServer variable.

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

The s.trackingServerSecure variable is a string that contains the location to send image requests. It is almost always a subdomain of your site. Modern privacy practices in browsers commonly make third-party cookies unreliable. If this variable is blank, it uses the value in the s.trackingServer variable.

The value for this variable is almost always a first-party domain, such as data.example.com. 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.trackingServerSecure = "data.example.com";

CNAME records usually point to a subdomain on data.adobedc.net, sc.adobedc.net or 2o7.net.