Campaign: multibranding in multi-cell Message Center setup

This article describes how to configure multibranding for clients using multiple Message Center instances and why even when using the same transactional email template, URLs in the email content may not show the exact same subdomain for different recipients.

Description description

Subdomain configuration

When we delegate and configure a new subdomain via the Control Panel to send transactional messages and we have multiple Message Center instances (RTs), it is important to remember that the subdomain will be configured with each RT instance linked to your marketing instance via external accounts. However the SAN (Subject Alternative Names) created for tracking ‘t’, mirror pages ‘m’ and resources ‘res’ will be created automatically with a number matching the RT instance number. For example:

https://instanceName-rt-prod9.campaign.adobe.com –> https://t9.email.subdomain.com/
[br>https://instanceName-rt-prod10.campaign.adobe.com –](br>https://instanceName-rt-prod10.campaign.adobe.com --) https://t10.email.subdomain.com/ [br>https://instanceName-rt-prod11.campaign.adobe.com --](br>https://instanceName-rt-prod11.campaign.adobe.com –) https://t11.email.subdomain.com/
[br>https://instanceName-rt-prod12.campaign.adobe.com –](br>https://instanceName-rt-prod12.campaign.adobe.com --) https://t12.email.subdomain.com/ [br>https://instanceName-rt-prod16.campaign.adobe.com --](br>https://instanceName-rt-prod16.campaign.adobe.com –) https://t16.email.subdomain.com/
[br>https://instanceName-rt-prod17.campaign.adobe.com --`](br>https://instanceName-rt-prod17.campaign.adobe.com --`)` https://t17.email.subdomain.com/

In each Message Center instance, the Deployment wizard Tracking configuration and Access from the internet configuration is set with the subdomain configured for this instance as the external URL (for tracking and mirror pages etc.).

To use the new subdomain correctly you need to be familiar with the concept of the multibranding in Adobe Campaign Classic.

Multibranding in the Message Center

If you are using multiple brands to send your communications you need to create external accounts (under Administration -> Platform -> External accounts) in the marketing instance and in the Message Center instances for each brand/subdomain you are planning to use. By default customers can’t access the Message Center instances directly so you might need to ask Support or Professional Services consultants to help you with that part.

The external accounts for each brand need to have the matching internal names in the marketing and Message Center instances. For example if you create an external account with an internal name email_subdomain3_com in the marketing instance, you need to create the same account in the Message Center instance, also having email_subdomain3_com for internal name in RT.

The external accounts in the Message Center are set up with Tracking server URL, Mirror page URL as well as the Error address. For example:

When you create your transactional message template you need to link it with the external account created for the selected brand. You can do it in the Delivery template properties General tab, using the Routing drop down at the bottom. Once you save and publish the template, it will appear in all Message Center instances linked with the marketing instance and will be sent via the external accounts configured in each instance.

Each Message Center instance acts as an individual sending/execution engine. When events are triggered to the load balancer endpoint, they can randomly reach any RT instance under this load balancer. This means that the reached instance will process the received event, link it with the message template published in the RT instance and prepare a message based on the template configuration, including the branding configuration set up in the external account.

Resolution resolution

Recipients receive their email messages.

As a result events that hit different RT instances for the same message template will be processed in the different RTs and messages prepared by them with the specific branding configuration. This means that tracked URLs and mirror pages can show as m9. or t9. in an email received from one RT (RT9) or m10. or t10. when received from another RT (RT10).

Examples of mirror pages URLs:

https://m9.email.subdomain.com/nl/jsp/m.jsp?c=%409JQ%2FS433ldT598A0UZgmjbqlopaflwLhjFpnhc1489gqaPeafhudnglAs%3D

vs

https://m10.email.subdomain.com/nl/jsp/m.jsp?c=%89Powq1%2FS486dT59wtyakq0UZgjywp56qlopaflwLhjFpRgayeWmf14s%3D