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 (refer to Event description). It contains data linked to the event, such as its type (order confirmation or account creation on a website for instance), email address or mobile number, as well as other information that lets you enrich and personalize the transactional message before delivery. This can be customer contact information, the language of the message or the email format.
Example of event data:
To process transactional messaging events, the following steps must be applied:
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: which means the event may 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. Refer to 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 Message Center 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.