Correctly populate the trackingServer and trackingServerSecure variable

Because of the large amounts of data and clients the Adobe Marketing Cloud has, there are several data centers to accommodate each organization. The following are locations where data is sent to and stored:

  • San Jose, California
  • Dallas, Texas
  • Pacific Northwest, United States
  • London, UK
  • Singapore
When you configure an implementation to send data to Adobe Analytics servers, it is imperative to send it to the correct location. Failure to do so causes inflated visitor counting or data loss.

Identify whether using first- or third-party cookies

If you are using a first-party cookie implementation, it is most likely these steps are already taken care of. If you have not yet started the first-party cookie process, see the Implementing First-Party Cookies white paper.

The individual who initially configures the first-party cookie implementation also defines the domain and subdomain used. For example:

s.trackingServer="stats.example.com";
s.trackingServerSecure="sstats.example.com";

The rest of this article only applies to third-party cookie implementations. Determining data center and subdomain is not necessary, because it is assumed that information already resides in your organization's CNAME records.

Note:

Adobe strongly advises against using s.trackingServerSecure with third-party cookies. First-party cookies allow you to forward data to Adobe's data collection servers using your domain paired with a valid SSL certificate.

Determine your data center

Understanding which data center you're on helps when you are dealing with cookies or linking different types of implementation. To determine which data center you're on, log in to Adobe Analytics and note the subdomain of omniture.com you are on via the browser's URL:

  • If the domain is www.omniture.com or sc.omniture.com, your data center is San Jose.
  • If the domain is www2.omniture.com or sc2.omniture.com, your data center is Dallas.
  • If the domain is www3.omniture.com or sc3.omniture.com, your data center is London.
  • If the domain is www4.omniture.com or sc4.omniture.com, your data center is Singapore.
  • If the domain is www5.omniture.com or sc5.omniture.com, your data center is Pacific Northwest.

Send data to the correct data center

Since a given report suite resides on only a single data center, it is imperative that data is sent to the correct one. Remote Data Collection (RDC) allows image requests to be collected via servers closer to the visitor. These smaller servers significantly reduce image request response time in locations far from Adobe's main data centers. Either RDC or non-RDC domains can be used, but cannot be used interchangeably. Failure to keep consistency with data collection domains causes inflation in unique visitor counts.

  • Non-RDC domains
    • San Jose: 112.2o7.net
    • Dallas: 122.2o7.net
    • (London, Singapore, and Pacific Northwest Data Centers only use RDC)
  • RDC domains
    • San Jose: d1.sc.omtrdc.net
    • Dallas: d2.sc.omtrdc.net
    • Pacific Northwest: sc.omtrdc.net
    • London: d3.sc.omtrdc.net
    • Singapore: sc.omtrdc.net

Note:

All report suites created in 2014 onwards are globally unique, meaning Adobe's servers can route traffic to the correct location without a data center designation. All report suites created or migrated to Singapore or Pacific Northwest are guaranteed to be globally unique, making sc.omtrdc.net always valid.

If you know that your report suite was recently created, using sc.omtrdc.net regardless of data center is permitted for all data centers.

Use the correct subdomain

Data collection requires a unique subdomain to keep visitor data separate across Adobe Marketing Cloud customers. It is prefixed to the data center address, and is generally your Adobe Analytics login company name with all spaces removed. You can technically use whatever subdomain you'd like, however it is highly recommended to be specific enough that:

  • No other Adobe Marketing Cloud customer would use it.
  • You are consistent with the subdomain across all report suites, especially if your organization uses a global report suite.
Some examples of valid third-party cookie domains:
s.trackingServer="example.112.2o7.net";
s.trackingServer="example.d1.sc.omtrdc.net";

If you are not certain on which domain to use, have one of your organization's supported users contact Customer Care.