Each event can trigger a a personalized message. For this to happen, you need to create a message template to match each event type. Templates contain the necessary information for personalizing the transactional message. You can also use templates to test the message preview and send proofs using seed addresses before delivering to the final target.
To create a message template, follow the steps below:
Go to the Message Center >Transactional message templates folder in the Adobe Campaign tree.
In the list of transactional message templates, right-click and select New in the drop-down menu or click the New button above the list of transactional message templates.
In the delivery window, select the delivery template suitable for the channel you want to use.
Change its label if necessary.
Select the type of event that matches the message you want to send. Event types destined to be processed by Adobe Campaign must be created beforehand. Learn more
An event type should never be linked to more than one template.
Enter a nature and a description, then click Continue to create the message body.
The definition of the transactional message content is the same as for all deliveries in Adobe Campaign. For instance, for an email delivery, you can create content in HTML or text format, add attachments or personalize the delivery object. Learn more.
Images included in the message must be publicly accessible. Adobe Campaign does not provide any image upload mechanism for transactional messages.
Unlike in JSSP or webApp,
<%= doesn’t have any default escaping.
You have to escape each data coming from the event properly. This escaping depends on how this field is used. For example, within a URL, please use encodeURIComponent. To be displayed in the HTML, you can use escapeXMLString.
Once you have defined your message content, you can integrate event information into the message body and personalize it. Event information is inserted into the body of the text thanks to personalization tags.
To insert personalization tags into the body of an email message, apply the following steps:
In the message template, click the tab that matches the email format (HTML or text).
Enter the body of the message.
In the body of the text, insert the tag using the Real time events>Event XML menus.
Fill in the tag using the following syntax: element name.@attribute name as shown below.
A seed address lets you display a preview of your message, send a proof, and test message personalization before sending the message. Seed addresses are linked to the delivery and cannot be used for other deliveries.
In the transactional message template, click the Seed addresses tab, then click the Add button.
Assign a label to it for easy selection later, then enter the seed address (email or mobile phone depending on the communication channel).
Enter the external identifier: this optional field allows you to enter a business key (unique ID, name + email, etc.) that is common to all applications on your website, used to identify your profiles. If this field is also present in the Adobe Campaign marketing database, you can then reconcile an event with a profile in the database.
Insert test data. Refer to this section.
Click Ok to confirm the creation of the seed address.
Repeat the process to create as many addresses as you need.
Once the addresses are created, you can access their preview and personalization.
Once you have created one or more seed addresses and the message body, you can preview the message and check its personalization.
In the message template, click the Preview tab, then select A seed address in the drop-down list.
Select the seed address created previously to display the personalized message.
You can test message delivery by sending a proof to a previously created seed address.
Sending a proof involves the same process as for any delivery.
Learn more about proofs in this section.
However, to send a proof of a transactional message, you need to carry out the following operations:
To send the proof:
Click the Send a proof button in the delivery window.
Analyze the delivery.
Correct any errors and confirm the delivery.
Check that the message was delivered to the seed address and that its content complies with your configuration.
Proofs can be accessed in each template via the Audit tab.
If you are transitioning from Campaign Classic v7, all deliveries go through the mid-sourcing server.
However, when creating a transactional message template, the routing needed for the template to be successfully used is internal email delivery. This routing prevents you from sending proofs.
Consequently, to send a proof for you transactional message template, you must change the routing from internal email delivery to the mid-sourcing routing account.
Once the proofs have been sent, you must change the routing back to internal email delivery prior to publishing the transactional message template.
When the message template created is complete, you can publish it, which will allow you to send messages linked to real-time and batch events.
Whenever you make any changes to a template, make sure you publish it again for these changes to be effective during transactional message delivery.
Go to the Message Center > Transactional message templates folder of the tree.
Select the template you want to publish.
Once publication is complete, both message templates to be applied to batch and real-time type events are created in the Administration > Production > Message Center Execution> Default > Transactional message templates folder.
Once a template is published, if the corresponding event is triggered, Adobe Campaign will receive the event, link it to the transactional template and send the corresponding transactional message to each recipient.
Once a message template is published , it can be unpublished.
Indeed, a published template can still be called if the corresponding event is triggered: if you are no longer using a message template, it is recommended to unpublish it. This is to avoid sending an unwanted transactional message by mistake.
For example, you published a message template that you only use for Christmas campaigns. You may want to unpublish it after the Christmas period is over, and publish it again next year.
Also, you cannot delete a transactional message template that has the Published status. You must unpublish it first.
To unpublish a transactional message template, follow the steps below.
The transactional message template status changes back from Published to Being edited.
Once unpublication is complete:
Both message templates (applied to batch and real-time type events) are deleted.
They no longer appear in the Administration > Production > Message Center Execution > Default > Transactional message templates folder.
Once a template is unpublished, you can delete it.
To do so, select it from the list and click the Delete button on top right of the screen.