trackingServer
Adobe 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.
- Log in to Adobe Experience Platform Data Collection using your AdobeID credentials.
- Click the desired tag property.
- Go to the Extensions tab, then click 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.
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"
});
Tracking Server using the Adobe Analytics extension
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.
- Click the desired tag property.
- Go to the Extensions tab, then click the Configure button under Adobe Analytics.
- Expand the General accordion, which reveals the Tracking Server field.
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.
Determine the value for trackingServer
The value for this variable depends on if you use first-party cookies or third-party cookies. Adobe strongly recommends using first-party cookies in your implementation.
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 cookies
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 Adobe 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 Adobe Analytics and are still valid.
example.data.adobedc.net
. For example, custom.example.data.adobedc.net
is not a valid tracking server.