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.
SSL Tracking Server in Adobe Experience Platform Launch
SSL Tracking Server is a field under the General accordion when configuring the Adobe Analytics extension.
- Log in to launch.adobe.com using your AdobeID credentials.
- Click the desired property.
- Go to the Extensions tab, then click the Configure button under Adobe Analytics.
- Expand the General accordion, which reveals the SSL Tracking Server field.
If this field is left blank, it defaults to the value in the trackingServer variable.
s.trackingServerSecure in AppMeasurement and Launch 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 ssl.d1.sc.omtrdc.net .