You can attach one or more files to an email delivery.
To avoid performance issue, it is recommended not to include more than one attachment per email. The recommended threshold can be configured from the list of Campaign Classic options.
There are two possible cases:
This type of configuration is generally carried out in the delivery templates. For more on this, refer to About templates.
To avoid performance issues, images included in emails cannot exceed 100 KB. This limit, set by default, can be changed from the NmsDelivery_MaxDownloadedImageSize
option. However, Adobe strongly recommends to avoid large images in your email deliveries.
Adobe also recommends to limit the size and number of attached files. By default, you can only add one file as an attachment to an email. This threshold can be configured from the NmsDelivery_MaxRecommendedAttachments
option.
Learn more in the list of Campaign Classic options.
To attach a local file to a delivery, follow the steps below.
You can attach several files to a delivery. Attachments can be in any format, included zipped format.
Click the Attachments link.
Click the Add button.
Click File… to select the file to be attached to the delivery.
You can also directly drag and drop the file in the delivery Attachments field, or use the Attach icon from the delivery wizard toolbar,
Once the file is selected, it is immediately uploaded onto the server to be available at the time of delivery. It is listed in the Attachments field.
When you create a calculated attachment, the name of the attachment can be computed during analysis or delivery of each message and can depend on the recipient. It can also be personalized and converted to PDF.
To create a personalized attachment, follow these steps:
The following options are available:
If the attachment is a local file, select the option: File name is specified when creating the delivery template. The file is selected locally and uploaded onto the server. Follow the steps below:
Select the file to upload in the Local file field.
Specify the label if necessary. The label replaces the filename when viewed in messaging systems. If nothing is specified, the filename is used by default.
If necessary, select Upload file on the server, and then click Update on server to start the transfer.
The file is then available on the server to be attached to the different deliveries created from this template.
The option The file content is personalized and converted into PDF format at the time of delivery for each message lets you select a file with personalization fields, such as the last name and first name of the intended recipient.
For this type of attachment, apply the following configuration steps:
Select the file to upload.
Specify the label if necessary.
Select Upload file on the server, and then click Update on server to start the transfer.
You can display a preview. To do this, select a recipient.
Analyze your delivery and then start it.
Each recipient receives a personalized PDF attached to the delivery.
You can calculate the attachment name during the delivery preparation. To do this, select the option The file name is calculated during delivery analysis (it cannot depend on the recipient).
This option is used only when the delivery is sent by an external process or a workflow.
Specify the label you wish to apply to the attachment.
Specify the access path of the file and its exact name in the definition window.
The file must be present on the server.
Analyze and then start your delivery.
The filename computation can be seen in the analysis log.
When selecting the attachment, you can choose the option The file name is calculated during delivery for each recipient (it can depend on the recipient). You can then map recipient personalization data with the name of the file to send.
This option is used only when the delivery is sent by an external process or a workflow.
Specify the label you wish to apply to the attachment.
Specify the access path of the file and its exact name in the definition window. If the filename is personalized, you can use the Personalization fields for the relevant values.
The file must be present on the server.
Analyze and then start your delivery.
In the example below, the attached file was chosen according to its name as defined using the merge fields.
For the first two options, you can choose Upload file on the server by selecting the appropriate option. The Update the file on the server link lets you start uploading.
A message tells you that the file has been uploaded to the server:
For a change of file, a warning message is displayed:
The Advanced tab lets you define advanced options on attached files:
You can define filter options to avoid sending the attached file to all recipients. The option Enable filtering of recipients who will receive the attachment activates an input field used to define a recipient selection script, which must be entered in JavaScript.
You can script the name of the file in order to personalize it.
Enter your text in the window and use the personalization fields available in the drop-down list. In the following example, the filename is personalized to contain today’s date and the name of the recipient.