Subdomain configuration from the Control Panel is available in beta, and subject to frequent updates and modifications without notice.
This capability is not available for Campaign v8.
A subdomain is a division of your domain that can be used to isolate your brands, or various types of traffic (transactional messages, marketing information, etc.).
Let’s take the example of the “mybrand.com” domain, that is used to send both transactional and marketing communications. In this situation, you can decide to set up two subdomains:
By doing so, you will help preserve the reputation of your domain and other subdomains. For example, if the “marketing.mybrand.com” subdomains ended up being added to the block list by Internet Service Providers due to bad deliverability, this would prevent the whole “mybrand.com” domain and the “info.mybrand.com” subdomain from being added to the block list.
Subdomain configuration allows you to configure a sub-section of your domain (technically a “DNS zone”) for use with Adobe Campaign. Available setup methods are:
Full subdomain delegation to Adobe Campaign (recommended): The subdomain is fully delegated to Adobe. Adobe is able to deliver the Campaign as a managed service by controlling and maintaining all aspects of DNS that are required for delivering, rendering and tracking of email campaigns.
Use of CNAMEs: Create a subdomain and use CNAMEs to point to Adobe-specific records. Using this setup, both Adobe and the customer share responsibility for maintaining DNS.
The table below provides a summary of how these methods work, as well as the implied level of effort:
|Configuration method||How it works||Level of effort|
|Full delegation||Create the subdomain and namespace record. Adobe will then configure all DNS records required for Adobe Campaign.
In this setup, Adobe is fully responsible for managing the subdomain and all the DNS records.
|CNAME, custom method||Create the subdomain and namespace record. Adobe will then provide the records to be placed in your DNS servers and will configure the corresponding values in Adobe Campaign DNS servers.
In this setup, both you and Adobe share responsibility for maintaining DNS.
Additional information on domain configuration is available in this documentation.
If you have any question regarding subdomain configuration methods, reach out to Adobe Deliverability team, or eventually contact Customer Care to request Deliverability consulting.
When setting up subdomains for Campaign Classic instances, you are required to select the use case for which the subdomain will be used (see Setting up a new subdomain).
Possible use cases are:
Marketing communications: communications that are intended for a commercial purpose. Example: sales email campaign.
Transactional & operational communications: transactional communications contain information aimed at completing a process that the recipient has started with you. Example: purchase confirmation, password reset email. Organizational communications relate to the exchange of information, ideas, and views within and outside the organization, with no commercial purpose.
Breaking down your subdomains according to use cases is a best practice for deliverability. By doing so, the reputation of each subdomain is isolated and protected. For example, if your subdomain for marketing communications ends up being added to the block list by Internet Service Providers, your transactional communications subdomain will not be impacted, and will keep being able to send communications.
You can configure a subdomains for both Marketing and Transactional use cases:
If you are using Campaign Classic, Control Panel allows you to see what RT/MID instances are connected to the Marketing instance that you are working with. For more on this, refer to the Instance Details section.