This event executes a job when a single message is sent to a recipient.

Single messages are messages that are sent to only one recipient at a time, rather than to a whole group. This includes:

  • Single messages sent with one of the following time-based automations: ​

    • Send Most Recent Message(s) to Selection​

    • Send Prepared Message to Address​

    • Send Prepared Message to Selection

    • ​Send Previous Message to Selection​

  • Single messages sent with one of the following event-based automations:

    • ​Send a Previous Message to Users​

    • Send Most Recent Message(s) to Users​

    • ​Send Prepared Message to Address

    • ​Send Prepared Message to Users​

  • Single messages and transactional messages sent via API.

  • Mapp Engage system messages.


Hint:

The designation (C) means contact-related. In general, you only combine contact (C) events with contact (C) jobs. For more information, see Contact (C) vs. System (S) Automations​

General

​Name​

Defines the name of the automation. The name is used to identify the automation in the system. The maximum length is 100 characters.

​Description​

Provides information about the automation. The description makes it easier to identify the automation in the system.

​Event​

Selects the type of event that, when combined with a job, forms the automation. Every time this event occurs, the system executes the dependent job. The job is defined in the ​Edit Event-based Job​ window.

Recommended Automations​

An automation is a combination of an event plus a resulting job. The following combinations are recommended. It is possible to create other combinations, as well, but not all combinations of events and jobs result in meaningful system behavior.

  • Single Message Sent (C) + Send HTTP Request (C): This automation sends an HTTP request every time a single message is sent. For example, the request includes the user ID, single message ID and sendout time. This automation is used to track individual single message sendout. By using the ​Log Responses​ option it is possible to determine whether single message sendout was successful or produced an error.

  • Single Message Sent (C) + Store Data in Profile Attribute (C): This combination stores information in a contact's profile when a single message is sent. For example, this information could be the message ID or the job processing date.

  • Single Message Sent (C) + Delete Contact (C): This automation deletes a contact, including email address or mobile number and all profile data, when he is sent a single message. Example: the single message is an unsubscribe confirmation and you want to permanently delete the contact from your system.

Define Event​

This area defines the specific parameters of the event.

  • Group Name: This drop-down list restricts the event to single message sendouts in one specific group. If you select a group, three additional bullet points appear:

    • Any Message: The event includes all future single message sendouts in this group, as long as the sendout takes place when the automation is running.

    • Scheduled/Sent: Do not select this option for this event.

    • Prepared Message: The event includes all single message sendouts of the selected prepared message. This includes all future sendouts of the prepared message, as long as the sendout takes place when the automation is running.

  • Message Category: This drop-down list restricts the event to sendouts in a specific message category. (Hint: Since message categories are not group-specific, you can use a message category to create an automation that reacts to sendouts in multiple groups at once.)

  • Status: This drop-down list limits the event to successful, skipped, or failed single message sendouts.

    • Successful: The single message was successfully sent to the Mapp EngageMTA (Message Transfer Agent).

    • Skipped: The single message was skipped and not sent to the Mapp EngageMTA.
      A message can be skipped during sendout for several reasons. For example, if the recipient is on a blacklist or Robinson list, or if the recipient does not have an address stored in the user profile.

    • Failed: The single message was not successfully sent to the Mapp EngageMTA. Failure occurs due to a system or database problem, not a problem with the email address.

  • Recipient: This input field limits the event to single messages sent to one specific recipient. Use the ​Search​ button to search for a recipient in the system.

Define Selection​

  • Selection: This drop-down list defines a selection. This limits the event to recipients who receive a single message and fulfill the selection criteria. Use the to search for a selection in the system.

Actions

The following actions are available: