You can send transactional messages based on customer marketing profiles, which allows you to:
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 transactional messages, you must be part of the Administrators (all units) 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.
The differences are listed below.
Go the transactional message that was created to edit it.
In the transactional message, click the Content section. In addition to the transactional template, you can also choose any email template targeting Profile.
Select the default email template.
Similar to all marketing emails, it includes an unsubscription link.
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.
Save your changes and publish the message. See Publishing a transactional message.
Once the message is published and your site integration is done, you can monitor the delivery.
To view the message delivery log, click the icon at the bottom right of the Deployment block.
For more information on accessing the logs, see Monitoring the delivery.
Select the Sending logs tab. In the Status column, Sent indicates that a profile has opted in.
Select the Exclusions logs tab to view recipients who have been excluded from the message target, such as addresses on denylist.
For any profile that has opted out, the Address on denylist 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.