Transactional emails are triggered by a user's interaction with your own site or app. Examples include order confirmations, monthly invoices and password resets. You can send transactional email in one of two ways:
Send supplied email content to one or more recipients
Send an existing Message to one or more recipients
Some ways transactional messages can be used include but are not limited to:
- Account related messages
- Purchase related messages
- Alerts of account activity
Plus many more that a Contact might need to be notified about directly.
Benefits of Transactional Email
When you want to send a single email to an individual this is faster than using other Batch methods.
As with other Message Sends and Campaigns, we provide reporting for Transactional Groups in product. You have visibility over deliverability, opens, link clicks and Contact Message history.
Lists and Contacts
When you submit a Transactional API method you must supply a List ID for an existing List. The Contact(s) you send Transactional messages to will be saved to the List if they don't exist or updated if they do. We must save contacts in the List in order to track statistics for reporting.
Wildcards and Stored Fields
Content in both the saved Message and in the supplied email supports wildcards and conditional content. When you submit a Transactional API method, you can supply additional fields per contact that are to be used in the message content.
Additionally, as part of the API payload you can specify to save certain contact fields along with the contact. In doing so, if these fields do not exist in the List already, they will be created for you.
Groups and Reporting
The Transactional API methods require a Group Name parameter. This name is used primarily to group together multiple Transactional sends over time in to a single report. For example, if you provide the Group Name "Password Resets" for all of your messages relating to a user resetting their password, all those sends will be visible in the same report in the system.
Just like any other report, these Transactional Group reports can also be shared.
Transactional API methods have a limit of 100 Contacts per call and Messages must not exceed 250kb.
There is a limit of 1000 unique Group Names allowed.
Due to the method in which links are tracked, if you provide a wildcard as a link URL in your content, that field must be saved against the Contact in the List in order for the link to work correctly.