This job sends a prepared message to an email address or a server. The message must first be saved as a prepared message.

This job sends single messages. All of the single messages share the same message ID. This means that only one sendout appears in the outbox. Single messages are evaluated together in the statistics. Statistics for a single message are found in the ​Single Message Statistics Overview​ window. For more information, see Group Messages and Single Messages in Mapp Engage​.

If the prepared message is sent to an email address, the recipient does not have to be a member of the group in which the prepared message is saved. The recipient is not added to the group.

Hint:

This job mainly has a notification function in the system. It is used to inform the responsible user that an event has taken place. For example, a prepared message can be sent to the marketing manager after every finished group sendout. This job cannot be used to send a prepared message to all recipients who complete a certain action. Instead see Send Prepared Message to Contact (C)​

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.

Setting

Setting

Description

​Group Sendout Finished (S)​

​Send Prepared Message to Address (S/C)​

This automation sends a prepared message to a specified address once group sendout is finished. This automation can be used to inform a manager or the group owner that sendout is complete.

​Subscribed to Group (C)​

​Send Prepared Message to Address (S/C)​

This automation sends a prepared message to the specified address every time a new member subscribes to the group. This automation can be used to inform a user or the group owner of a new member.

General

​Name​

Displays the name of the automation that is defined in the ​Edit Event​ window.

​Description​

Displays the description of the automation that is defined in the ​Edit Event​ window.

​Event​

Displays the event that is defined in the ​Edit Event​ window. Every time this event occurs, Engage executes the dependent job.

​Job​

Defines the job. Engage executes this job automatically every time the event occurs. For a list of all available jobs, see ​All Available Event-Based Jobs​.

Define Job​

This area defines the specific parameters of the job.

Setting

Description

​Message​

This drop-down list defines the message. All prepared messages saved in the system are displayed here.

​Address​

This input field defines the address to which the message is either saved or sent. A connection can be established to a server address over FTP (FTP, PFTP (passive FTP), AFTP (active FTP), SFTP, FTPS), SCP , HTTP (HTTP, HTTPS) and SOAP .

This address has the following format: ftp://user:password@host.port/url-path

Example: ftp://joesample:1password@ftp.mapp.com/messages

The server account credentials can be encrypted with Transfer Security records. The user name, password or complete user account are specified with placeholders for ​Transfer Security ​records. The report can be delivered directly to an email address by using the mailto prefix.

This address has the following format: mailto:emailaddress

mailto:joe.sample@mapp.com

  • ​Use Event Parameter:​ When selected, this checkbox sends the prepared message to the user involved in the event.
    Please note that for this job, it is not recommended to use the event parameter for most combinations. Example: An automation combines the event ​Message Link Clicked (C)​ with the job ​Send Prepared Message to Address (C)​, This combination sends a prepared message to the specified address every time a message link is clicked. This combination does not send a prepared message to the recipients who click on the link.

​Parameter​

This area creates parameters that add information from the event into the prepared message. For details see Add Event Data to a Prepared Message​.


Define Delay​

In this area, you can define a time delay between the event and the resulting job. If you define a delay, the system waits the specified amount of time after the event takes place before executing the event-based job. If you do not define a delay, the system executes the job immediately after the event takes place.

Hint:

Engage calculates the selection for an event-based job when the job is executed, not when the event takes place. When you define a delay, the selection is calculated after the delay


  • ​Delay:​ Defines whether there is a delay between the event and the resulting job.

    • ​No: ​There is no delay between the event and the resulting job. When Engage registers the event, the system executes the job immediately.

    • ​Yes: ​Creates a delay between the event and the resulting job.
      ​Unit:​ Defines the unit of time with which Engage calculates the delay.
      ​Value:​ Defines the duration of the delay.

Actions

The following actions are available: