On this page: Learn how to attach static or personalized PDF files to emails, including the supported campaign types and applicable count, size, and volume limits.
You can attach a static PDF file to the email messages that you send with Journey Optimizer. If you use API-triggered campaigns, you can also attach a personalized PDF file for each recipient.
Note that personalized PDF attachments require additional file retrieval and processing. Campaigns using them may have higher processing latency and lower throughput than campaigns without attachments, particularly when using multiple or larger PDF files.
-
You can send up to 6 messages with a PDF attachment per profile per year, whether the attachment is static or personalized.
-
The maximum allowed file size for each attachment is 5 MB. For emails with personalized attachments, all static and personalized PDF attachments in the email share a combined 5 MB limit by default.
To attach a PDF file to an email message, follow the steps below.
-
Create an email in a journey or a campaign. Learn more
-
From the journey or campaign Content tab, select Add asset from the Attachment section.
-
The Assets Essentials repository displays.
note NOTE When designing messages, you access the Assets Essentials repository directly from within the Journey Optimizer interface. To learn more about the embedded Assets Essentials user interface, refer to Experience Manager Assets Essentials documentation. -
Use the PDF filter in the MIME Type section to restrict selection to the correct file format.
note NOTE Only the PDF format is allowed for attachments. -
Select the file of your choice.
- You can only select one file at a time.
- The maximum allowed file size for each attachment is 5 MB.
-
Once done, the name and size of the selected file display in the Attachment section.
You can remove the selected file using the More actions icon next to the file name.
Attach personalized PDF files for API-triggered campaigns personalized-attachments
You can also attach recipient-specific PDF files to a single email sent through an API-triggered campaign. Unlike a static attachment, each recipient can receive a different file, such as an invoice, a boarding pass, a contract, or a shipping label.
The combined size of all static and personalized PDF attachments in an email is limited to 5 MB by default. Organizations with the applicable PDF Attachments add-on can use a combined limit of up to 10 MB.
-
Personalized PDF attachments are supported only for transactional API-triggered email campaigns.
-
You can include up to five PDF attachments in an email. This limit includes both static and personalized attachments. For example, an email containing one static PDF can include up to four personalized PDFs. If you need to send more, split them across multiple communications.
-
Personalized and static PDF attachments count toward the same quota. Learn more
Personalized PDF attachments must be uploaded to the attachment-specific Data Landing Zone container, then referenced in the API payload. Data Landing Zone is currently the only supported storage location for personalized PDF attachments.
-
Retrieve the Data Landing Zone credentials for your sandbox using
type=ajoemailattachmentsfor the same IMS organization and sandbox as the execution request, as described in the Adobe Experience Platform documentation. Depending on the cloud provider, use the Azure container or AWS bucket and folder returned by the API. -
Generate the PDF files with the tool of your choice, and upload them to your Data Landing Zone container.
Note that Data Landing Zone automatically deletes files after seven days, make sure the PDF files remain available in the container until message delivery and any retries are complete.
-
In the API payload, for each recipient, add an
attachmentsarray containing the file name, content type, and Data Landing Zone path of the PDF to send. Learn how to personalize your API-triggered campaign contentcode language-json "attachments": [ { "name": "invoice-12345.pdf", "contentType": "application/pdf", "source": { "type": "dlzPath", "path": "attachments/invoice-12345.pdf" } } ]Note that
source.pathis the object path relative to the attachment-specific Data Landing Zone container retrieved withtype=ajoemailattachments. Do not include the Azure container name, the AWS bucket or folder, credentials, or a full storage URL.
At send time, Journey Optimizer fetches the file from the specified location and attaches it to the message for that recipient. Personalized PDF attachments are supported for High Throughput campaigns in the primary region. They are not supported during regional failover.
For the full API payload reference, see the Interactive Message Execution API documentation.