Get started with transactional messaging about-transactional-messaging
Overview overview
Transactional messaging (Message Center) is a Campaign module designed for managing custom trigger notifications generated from events sent by an external information system.
As part of the transition from Campaign v7 to v8, the Campaign Classic documentation set has been streamlined and reorganized. Common features are now available exclusively in the Campaign v8 documentation set. To learn more about transactional messaging, refer to the Campaign v8 documentation.
This section covers the transactional messaging architecture and configuration of the control and execution instances, specific to on-premise and hybrid deployments.
Transactional messaging operating principle 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.
Key steps key-steps
The main steps when creating and managing personalized transactional messages in Adobe Campaign are summarized below.
Steps to perform on the control instance
On the control instance, you must perform the following actions:
- Create an event type (Campaign v8 documentation).
- Create and design the message template (Campaign v8 documentation). You must link an event to your message during this step.
- Test the message.
- Publish the message template (Campaign v8 documentation).
Event processing on the execution instance
Once you designed and published the transactional message template, if a corresponding event is triggered, the main steps below are performed on the execution instance:
- When the event is generated by the external information system, the relevant data are sent to Campaign via the PushEvent and PushEvents methods. See Event collection (Campaign v8 documentation).
- The event is linked to the appropriate message template. See Routing towards a template (Campaign v8 documentation).
- Once the enrichment stage is complete, the delivery is sent. See Delivery execution (Campaign v8 documentation). Each targeted recipient receives a personalized message.