Choose a data collection domain
Your data collection domain is the hostname that your implementation sends data to. All Adobe CX Enterprise products that use Adobe data collection (such as Adobe Analytics, Customer Journey Analytics, Adobe Experience Platform, Adobe Target, and Adobe Journey Optimizer) rely on this domain.
Data collection domain options
data.example.comdata.example.comdata.example.comThird-party data collection domain third-party
If you don’t use a first-party domain, send data to a subdomain of data.adobedc.net. Adobe recommends using your organization’s tenant ID as the subdomain. For example, example.data.adobedc.net. This domain is also the recommended origin when you route data collection through a CDN.
- Third-party domains always use the default RDC type.
- Do not use any subdomains deeper than
example.data.adobedc.net. For example,custom.example.data.adobedc.netis not a valid data collection domain. - Older implementations might use domains such as
sc.omtrdc.netor2o7.net. While these domains are still valid, Adobe recommends usingdata.adobedc.netwhere possible.
Find your tenant ID tenant-id
- Log in to Adobe CX Enterprise using your Adobe ID credentials.
- Anywhere in the CX Enterprise interface, press
[Cmd]+[I](macOS) 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 your tenant ID.
Your tenant ID is different from your IMS organization ID, which ends in @AdobeOrg. Each IMS organization has one tenant ID. If your company uses multiple IMS organizations, each organization has its own tenant ID.
Update your implementation update-implementation
When you change your data collection domain, update every implementation that sends data to Adobe:
- Web SDK tag extension: Update the Edge domain field when configuring the extension.
- Web SDK (alloy): Update the
edgeDomainproperty within theconfigurecommand. - Adobe Analytics extension: Update the SSL Tracking Server field when configuring the extension. Make sure that you also have the Visitor ID Service tag extension installed. See Visitor identification using the Analytics tag extension for more information.
- AppMeasurement: Update the
trackingServerSecureconfiguration variable. Make sure that you also have the Visitor ID Service implemented usingVisitorAPI.js. See Visitor identification using AppMeasurement for more information. - Other implementations: Update the data collection domain in any other implementation that sends data to Adobe, such as mobile apps or server-side implementations.
If your implementation doesn’t use the Visitor ID Service or the Web SDK, changing your data collection domain changes the domain of visitor cookies, and returning visitors can be counted as new visitors.
If your site uses multiple implementation methods and you cannot update all of them simultaneously, consider configuring a grace period. See Visitor ID Service migration considerations for additional steps on how to prevent visitors from being counted as new visitors across your site.