Once you have created and published an event (the cart abandonment as per the example above), the corresponding transactional message is created automatically.
The configuration steps are presented in the Configuring an event to send a profile 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. Fatigue rules are compatible with profile transactional messages. See Fatigue rules.
The steps for creating, personalizing and publishing a profile transactional message are the same as for an event transactional message. See Event transactional messages.
Also, as opposed to configurations based on real-time events, you have direct access to all profile information to personalize your message. See Inserting a personalization field.
For more information on accessing the logs, see Monitoring the delivery.
For any profile that has opted out, the Blacklisted address typology rule excluded the corresponding recipient.
This rule is part of a specific typology that applies to all transactional messages based on the Profile table.