In the context of transactional messaging, an event is generated by an external information system and is sent to Adobe Campaign via the PushEvent and PushEvents methods (see Event description).
This event contains data linked to the event, such as its type (order confirmation, account creation on a website, etc.), email address or mobile number, as well as other information that lets you enrich and personalize the transactional message before delivery (customer contact information, language of the message, email format, etc.).
Example of event data:
To process transactional messaging events, the following steps are applied on the execution instance(s):
Once all the steps above are carried out through the execution instance, each targeted recipient receives a personalized message.
For more on the transactional messaging instances, see Transactional messaging architecture.
Events generated by the information system can be collected using two modes:
Calls to SOAP methods let you push events in Adobe Campaign: the PushEvent method lets you send one event at a time, the PushEvents method lets you send several events at once. For more on this, see Event description.
Creating a workflow lets you recover events by importing files or via an SQL gateway (with the Federated Data Access option).
Once they are collected, events are broken down by technical workflows between real time and batch queues of the execution instance(s), while waiting to be linked to a message template.
On the execution instances, the Real time events or Batch events folders must not be set as views, as this could lead to access right issues. For more on setting a folder as a view, refer to this section.
Once the message template is published on the execution instance(s), two templates are automatically generated: one to be linked to a real time event, and one to be linked to a batch event.
The routing step consists in linking an event to the appropriate message template, based on:
The event type specified in the properties of the event itself:
The event type specified in the message template properties:
By default, routing relies on the following information:
The Event history, under Message Center > Event history , groups all the processed events into one single view. They can be categorized by event type or by status. These statuses are:
Pending: The event can be:
Pending delivery: The event was processed and the delivery template is linked. The email is pending delivery and the classic delivery process is applied. For more information, you can open the delivery.
Sent, Ignored and Delivery error: These delivery statuses are recovered via the updateEventsStatus workflow. For more information, you can open the relevant delivery.
Event not covered: The transactional messaging routing phase failed. For example, Adobe Campaign did not find the email which acts as a template for the event.
Event expired: The maximum number of send tries was reached. The event is considered null.
If the delivery of a message on a specific channel fails, Adobe Campaign can resend the message using a different channel. For instance, if a delivery on the SMS channel fails, the message is resent using the email channel.
To do this, you need to configure a workflow which recreates all events with the Delivery error status, and assigns a different channel to them.
This step can only be carried out using a workflow and is therefore reserved for expert users. For more information, please contact your Adobe account executive.