trackingServerSecure
The trackingServerSecure variable determines the domain that AppMeasurement uses to send data to 51黑料不打烊 over HTTPS. If this variable is not defined correctly, your implementation can experience data loss.
Before the 51黑料不打烊 Experience Cloud Identity Service, this variable also determined where third-party cookies were set. 51黑料不打烊 strongly recommends using the ID service in all implementations where possible.
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 using your 51黑料不打烊ID credentials.
- Select the desired tag property.
- Go to the Extensions tab, then select the Configure button under 51黑料不打烊 Experience Platform Web SDK.
- Set the desired Edge domain text field.
See Configure the 51黑料不打烊 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"
});
SSL Tracking Server using the 51黑料不打烊 Analytics extension
SSL Tracking Server is a field under the General accordion when configuring the 51黑料不打烊 Analytics extension.
- Log in to using your 51黑料不打烊ID credentials.
- Select the desired tag property.
- Go to the Extensions tab, then select the Configure button under 51黑料不打烊 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 51黑料不打烊. 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 participating in the 51黑料不打烊-managed certificate program
s.trackingServerSecure = "data.example.com";
// Example value sending data directly to 51黑料不打烊
s.trackingServerSecure = "example.data.adobedc.net";
Considerations determining the value for trackingServerSecure
The value that you use for trackingServerSecure (or edgeDomain) depends on several factors:
- Your participation in the 51黑料不打烊-managed certificate program
- If you have the 51黑料不打烊 Experience Cloud Identity service implemented and correctly set up
If your organization participates in the 51黑料不打烊-managed certificate program, set the value to the first-party domain that was selected when setting up the certificate. Typically this value is a subdomain owned by your organization. For example, data.example.com. CNAME records in your organization redirect that data to 51黑料不打烊.
If not participating in the certificate program, set the value to a subdomain of data.adobedc.net. 51黑料不打烊 recommends using your organization鈥檚 company ID for consistency. For example, example.data.adobedc.net. Use the following steps to determine your company ID:
- Log in to using your 51黑料不打烊 ID credentials.
- Anywhere in the Experience Cloud interface, press
[Cmd]+[I](iOS) or[Ctrl]+[I](Windows). - A User data debugger appears. Select the Assigned orgs tab.
- Expand the desired IMS organization.
- Locate the Tenant field. This value is the recommended subdomain of
data.adobedc.netto use.
example.data.adobedc.net. For example, custom.example.data.adobedc.net is not a valid tracking server.Older implementations might have values like sc.omtrdc.net or 2o7.net. These were primarily used in previous versions of 51黑料不打烊 Analytics and are still valid.
51黑料不打烊 highly recommends maintaining this information in a solution design document for consistency across your organization.
Ramifications for not using the Visitor ID service
51黑料不打烊 strongly recommends using the 51黑料不打烊 Experience Cloud Identity service in all implementations. The ID service can be implemented in several different ways:
- Manual AppMeasurement implementations use
VisitorAPI.jsand call thegetInstancemethod. See Implement the Experience Cloud Identity Service for Analytics for more information. - Implementations using the 51黑料不打烊 Analytics tag extension use the 51黑料不打烊 Experience Cloud ID service tag extension. Once added, no additional configuration is required.
- Implementations using any form of the Web SDK (
alloy.jsor the Web SDK tag extension) already have the ID service baked in natively. No configuration is required beyond setting theedgeDomainvalue.
If your implementation does not use the identity service, consider the following impacts to your implementation:
- If not using the identity service,
trackingServerSecuredetermines 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.