Because of the large amounts of data and clients the Adobe Experience Cloud has, there are several data centers to accommodate each organization. The following are locations where data is sent to and stored:
- Pacific Northwest, United States
- London, UK
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:
Typically CNAME records are already set up, and point to a subdomain of sc.omtrdc.net. 2o7.net is also a valid domain, primarily used in previous versions of Adobe Analytics.
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.
Since the migration of the San Jose and Dallas data centers, sc.omtrdc.net is a valid trackingServer value for all implementations. Each organization has a pre-defined subdomain so cookie values are kept unique, which is typically your login company name with spaces removed.
For example, a valid third-party tracking server would be:
If your organization uses DTM or Launch, the trackingServer variable (including subdomain) is automatically populated for you. If you are using a legacy Analytics implementation and are unsure about what subdomain to use, have a Support delegate contact Customer Care.
Adobe recommends using Launch for existing and new implementations.
Do not use any subdomains deeper than example.sc.omtrdc.net. For example, custom.example.sc.omtrdc.net is an invalid tracking server.