This section describes one solution to configure tracking and mirror page URLs per brand, for transactional messages in Adobe Campaign.
config-<instance>.xml
).To configure multibranding, you need to configure both execution instances and control instance. In the execution instances, follow the steps below:
Create one external account per brand.
Creating an execution instance type external account is presented in the Control instance section.
Extend the nms:extAccount schema to add the tracking URL:
<attribute advanced="true" desc="URL of the tracking servers" label="Tracking server URL"
length="100" name="trackingURL" type="string"/>
Extending an existing schema is presented in the Extending a schema section.
Modify the nms:extAccount form:
<container label="Message domain branding" type="frame">
<static type="help"> These parameters are used to override the DNS alias and addresses used during message delivery. When not populated, the values of the 'NmsServer_MirrorPageUrl' and 'NmsEmail_DefaultErrorAddr' options are used.</static>
<input xpath="@mirrorURL"/>
<input xpath="@trackingURL"/>
<input img="nms:sendemail.png" menuId="deliveryMenuBuilder" type="scriptEdit">
xpath="errorAddress"/>
</container>
Modify the NmsTracking_OpenFormula and NmsTracking_ClickFormula options to use the external account instead of a global option.
To do this, replace:
<%@ include option='NmsTracking_ServerUrl' %>
with:
<%@ value object="provider" xpath="@trackingURL" %>
These changes could lead to conflicts when upgrading. You may need to manually merge these formulas with their new version.
On the control instance, you need to link delivery templates and external accounts. To do this, you need to: