Transactional messaging operating principle

The Adobe Campaign Transactional messaging module integrates into an information system which returns events to be changed into personalized transactional messages. These messages can be sent individually or in batches via email, SMS or push notifications.

This feature relies on a specific architecture, where the execution instance is separated from the control instance. This distribution ensures higher availability and better load management. For more on this, see Transactional messaging architecture.

NOTE
To create new users for Message Center execution instances hosted on Adobe Cloud, you need to contact Adobe Customer Care. Message Center users are specific operators that require dedicated permissions to access Real time events (nmsRtEvent) folders.

The transactional messaging overall process can be described as follows:

For example, imagine you are a company with a website where your customers can buy products.

Adobe Campaign allows you to send a notification email to customers who have added products to their cart. When one of them leaves your website without going through with their purchases (external event which triggers a Campaign event), a cart abandonment email is automatically sent to them (transactional message delivery).

The main steps for putting this into place are detailed below in this section.

NOTE
Adobe Campaign prioritizes processing transactional messages over any other delivery.