Once you have created and published an event (the cart abandonment as explained in this section), the corresponding transactional message is created automatically.
The configuration steps are presented in the Configuring an event to send an event transactional message section.
In order for the event to trigger sending a transactional message, you have to personalize the message, then test it and publish it.
To access the transactional messages, you must have administration rights or appear in the Message Center agents (mcExec) security group. Event transactional messages do not contain profile information, therefore they are not compatible with fatigue rules (even in the case of an enrichment with profiles). See Fatigue rules.
Define an adapted test profile, which will allow you to preview your message and send a proof to check it.
Specify the information to send in JSON format in the Event data used for personalization section. This is the content that will be used when previewing the message and when the test profile receives the proof.
You can also enter the information relating to the profile table. See Enriching the transactional message content.
Click the Content block to modify your message's subject and content. For this example, import an HTML template containing images, the style sheet, and an HTML file. Importing HTML templates is presented in the Importing HTML content section.
Enter your message content. In this example, we have added three personalization fields: last name, last product consulted, total cart amount. The link to the abandoned cart is a link to an external URL that will redirect the person to their cart. This parameter is not managed in Adobe Campaign.
To add fields that you defined when you created your event (see Configuring an event), insert a personalization field in the message content. You can find the fields by selecting Transactional event > Event context.
To enrich the content of your message, add fields by selecting them from the table with which you linked your event. In our example, select the Title (salutation) field in the Profile table.
The steps for inserting a personalization field are detailed in the Adding a personalization field section.
The steps for previewing a message are detailed in the Previewing messages section.
You can check that the personalization fields match the information entered in the test profile. For more on this, see Defining a test profile in a transactional message.
The steps for sending a proof are detailed in the Sending a proof section.
Now, as soon as the "Cart abandonment" event is triggered, it automatically prompts a message containing the recipient's title and last name, the cart URL, the last product consulted, and the total cart amount to be sent.
To access reports concerning your transactional message, use the Reports button. See Reports.
You can suspend publishing your transactional message by using the Pause button, for example, to modify the data contained in the message. The events are therefore no longer processed, but instead kept in a queue in the Adobe Campaign database.
The queued events are kept during a period of time that is defined in the REST API (see REST API documentation) or in the trigger event if you are using the Triggers core service (see Working with Campaign and Experience Cloud Triggers).
When clicking Resume, all of the queued events (provided that they are not expired) are processed. They now contain all of the modifications carried out while the template publication was suspended.
Clicking Unpublish allows you to cancel the transactional message publication, but also the publication of the corresponding event, which deletes from the REST API the resource corresponding to the event that you previously created. Now, even if the event is triggered through your website, the corresponding messages are not sent anymore and they are not stored in the database.
To publish the message again, you need to go back to the corresponding event configuration, publish it, and then publish the message. For more on this, see Publishing a transactional message.
If you unpublish a paused transactional message, you may have to wait up to 24 hours before you can publish it again. This is to let the Database cleanup workflow clean all the events that were sent to the queue. The steps for pausing a message are detailed in the Suspending a transactional message publication section.
The Database cleanup workflow, which runs every day at 4am, is accessible through Administration > Application settings > Workflows.
By selecting a transactional message, you can delete it with the Delete element button even if it has already been published. However, deleting a transactional message can only be done under certain conditions:
For transaction message: To delete a transactional message, the messages should be unpublished and not paused.
If the transactional message is unpublished, the event configuration also needs to be unpublished to successfully delete your transactional message unless another transactional message is linked to the corresponding event. For more information on how to unpublish a transactional message, refer to this section.
Deleting a transactional message that has already sent notifications will also delete its sending and tracking logs.
For transactional message from an out-of-the-box event template (internal transactional messages): To delete an internal transactional message, the messages should be unpublished and not paused.