Salesforce Marketing Cloud - Transactional Send Email Journeys
This Friday, we are once again looking at a feature that went live with the July release: the Transactional Send Email Journeys. This new journey type gives SFMC users the option to configure transactional emails that are to be sent via the Transactional Messaging API in the interface; all without the assistance of a developer.
In addition to multi-step and single send journeys, a third journey type is now available with Transactional Send Journeys. The configuration in Journey Builder is extremely simple: The journeys only consist of a Transactional API event as an entry source and an email activity. The latter is configured as usual. During the entry event, a Triggered Send Data Extension can be selected, which records the data of incoming contacts. In addition, an event definition key must be assigned, which should be unique for each journey. This key in turn is then made available to the developer for the API request, which triggers the email delivery.
However, the advantages of Transactional Send Email Journeys are not only that transactional emails can now be configured in the interface. In the journey (as with other journeys), all configurations made are summarized in the email activity, which gives the marketer greater control over the delivery settings. In addition, the performance of the sending can also be seen directly in the email analytics area of the activity — a crucial point, as irregularities in the deliverability of transactional emails are finally visible in the Journey Builder.
We are pleased that with the launch of this feature, the Transactional Messaging API can now be used with less development effort and deliverability monitoring is significantly simplified.
Further information about Transactional Send Email Journeys is available here.
