Documentation Analytics Implementation Guide

trackingServerSecure

Last update: October 15, 2026

CREATED FOR:

Admin
Developer

The trackingServerSecure variable determines the domain that AppMeasurement uses to send data to Adobe over HTTPS. If this variable is not defined correctly, your implementation can experience data loss.

NOTE

trackingServer is a retired variant of this variable. It specified the domain for data sent over HTTP; with the prevalence of HTTPS, use trackingServerSecure instead. If s.trackingServerSecure is blank, AppMeasurement falls back to the s.trackingServer value.

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.

Log in to Adobe Experience Platform Data Collection using your AdobeID credentials.
Select the desired tag property.
Go to the Extensions tab, then select the Configure button under Adobe Experience Platform Web SDK.
Set the desired Edge domain text field.

See Configure the Adobe Experience Platform Web SDK extension in the Web SDK documentation for more information.

TIP

If your organization moves to the Web SDK from an AppMeasurement or Analytics extension implementation, this field can use the same value contained in trackingServerSecure (or trackingServer).

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.

Log in to Adobe Experience Platform Data Collection using your AdobeID credentials.
Select the desired tag property.
Go to the Extensions tab, then select 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 Tracking Server. If both SSL Tracking Server and Tracking Server are blank, it defaults to [rsid].data.adobedc.net.

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

The s.trackingServerSecure variable is a string that contains the domain to send data to Adobe. It is domain only; omit protocol, path, port, and slashes. If this variable is blank, it uses the value in the s.trackingServer variable. If both s.trackingServerSecure and s.trackingServer are blank, it defaults to [rsid].2o7.net.

// Example value when using a first-party domain
s.trackingServerSecure = "data.example.com";

// Example value when using a third-party domain
s.trackingServerSecure = "example.data.adobedc.net";

Considerations for determining the value for `trackingServerSecure`

The value that you use for trackingServerSecure (or edgeDomain) depends on how your organization sends data to Adobe:

If your organization uses a first-party domain, such as through the Adobe-managed certificate program, a customer-managed certificate, or a content delivery network (CDN), set the value to that domain. For example, data.example.com.
If your organization uses a third-party domain, set the value to your tenant ID subdomain of data.adobedc.net. For example, example.data.adobedc.net.

See Choose a data collection domain in the CX Enterprise interface and administration guide for details on each option, including how to find your tenant ID.

Adobe highly recommends maintaining this information in a solution design document for consistency across your organization.

Ramifications for not using the Visitor ID Service or Experience Platform Identity Service

Adobe strongly recommends using ECID as the primary form of visitor identity in all implementations. Collecting ECIDs can be implemented in several different ways, depending on implementation type:

Manual AppMeasurement implementations use VisitorAPI.js and call the getInstance method. See Implement the Visitor ID Service for Analytics for more information.
Implementations using the Adobe Analytics tag extension use the Experience Cloud ID Service tag extension, which implements the Visitor ID Service. Once added, no additional configuration is required.
Implementations using any form of the Web SDK (alloy.js or the Web SDK tag extension) automatically include the Experience Platform Identity Service. No configuration is required beyond setting the edgeDomain value.

If your implementation does not use ECIDs, consider the following impacts to your implementation:

If not using the Visitor ID Service or Experience Platform Identity Service, trackingServerSecure determines cookie location. Setting this variable to a third-party domain forces AppMeasurement to use a fallback cookie, as most modern browsers reject third-party cookies.
Internal link tracking and Activity Map might be less reliable.

recommendation-more-help

analytics-help-implement