Set Up a Transactional Message
When setting up Transactional emails, consider what user behaviors and other circumstances require a direct response message. You can use transactionals to automatically manage critical responses to user actions, such as to confirm sign ups, provide purchase receipts, or confirm messaging opt-outs and opt-ins.
When a transactional message is sent, the user is added to your Sailthru database–that is, a user profile is created for the user–if the user did not yet exist.
If an attempt is made to send a transactional email to an email address that has opted out of all emails, the API responds with an error code. In this case, a best practice would be to inform the user that they have unsubscribed from all email communication and encourage them to opt-in again if they wish to receive emails.
- From the Communications menu, select Templates.
- Once you create and name your new template, you will see the Template Editor which has multiple tabs.
- You will need to modify the Code tab to set the template as a Transactional Template.
For more information, see Build a Template.
See Abandoned Shopping Carts for information on coding templates for abandoned shopping cart reminders.
It is a Sailthru best-practice recommendation to test any new transactional template to ensure its creative layout, subject line, and other template code renders as expected, and that it is sent in response to the expected behaviors. Additionally, you may want to A/B test any new template(s) to determine which one achieves a higher open rate or lift.
Once your transactional message is set up, you can access Transactional Reporting through the Analytics section of My Sailthru.
Note that if you delete a transactional template, its reporting data will no longer be available.