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.
Changing this value makes AppMeasurement look for cookies in a different location. Unique visitor count can temporarily spike in reporting as visitor cookies are set in the new location.
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.
If your organization moves to the Web SDK from an AppMeasurement or Analytics extension implementation, this field can use the same value contained in
Configure the SDK using
edgeDomain. The field is a string that determines the domain to send data to.
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
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
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