When the transactional message is ready to be sent, it can be published.
The steps to publish, pause, unpublish and delete a transactional message are detailed below.
Only users with the Administration role can access and publish transactional messages.
The chart below illustrates the overall transactional messaging publication process.
Once you have edited and tested your transactional message, you can publish it. Simply click the Publish button.
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 or a list of products if you defined a product listing, and the total cart amount to be sent.
To access reports concerning your transactional message, use the Reports button. See Dynamic 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 the REST API documentation) or in the trigger event if you are using the Triggers core service (see About Adobe 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 the event, and then publish the 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.
Once a transactional message has been unpublished, or if a transactional message has not been published yet, you can delete it from the transactional message list. To do this:
However, deleting a transactional message can only be done under certain conditions:
Make sure the transactional message has the Draft status, otherwise you will not be able to delete it. The Draft status applies to a message that has not been published yet, or that has been unpublished (and not paused).
Transactional messages: Unless another transactional message is linked to the corresponding event, if the transactional message is unpublished, the event configuration also needs to be unpublished to successfully delete your transactional message. For more on this, see Unpublishing an event.
Deleting a transactional message that has already sent notifications will also delete its sending and tracking logs.
Transactional messages from an out-of-the-box event template (internal transactional messages): If an internal transactional message is the only one associated with the corresponding internal event, it cannot be deleted. You must first create another transactional message by duplicating it or through the Resources > Templates > Transactional message templates menu.