Transactional messaging and standard messaging compared

Deliver constructs and sends transactional messages differently than it does standard personalized message. During a standard messaging run, the system processes potentially large volumes of individually personalized messages. However, for transactional message, Deliver performs the same personalization operations for multiple web service requests, but each request processes only one message at a time.

You can enable any standard Deliver messaging for transactional message. Most messaging features available to standard messagings remain available when you enable the messaging for transactional message. Content elements available in standard message, such as personalization fields, text, images, HTML snippets, and hyperlinks are also available in transactional email message. However, some differences exist in the messaging features available in standard and transactional message.

The following table compares key features available in standard and transactional email message.

Comparison of features in standard messagings and transactional messagings.

Feature Standard messaging Transactional messaging
Transmit HTML, HTML and text, and text-only versions. X X
Output List Table (OLT) to specify personalization data

X

OLT contains all recipient data used to personalize email.

Not used.

Can be used for testing.

OLT personalization fields X X
Built-in personalization fields X X
Constant personalization fields (constants) X X
Conditional content X X
Advanced scripting for email X X
Message preview X

X

Preview not available for attachments.

Messaging results appear in standard Deliver performance reports X X
Track links in email messages X X
Tracking Audience ID as a contact attribute X X
Use personalization fields for contact tracking X X
Additional URL parameters for link tracking X X
Global email suppression X
Email attachments X