Which of the following is NOT a field when creating a Triggered Send Definition?

Which of the following is NOT a field when creating a Triggered Send Definition?

• A. Name
• B. Key Identifier
• C. Data Extension
• D. Multipart MIME

Answer: (C)

Triggered Sends are defined by identifying information and how the invite is invoked, not by the data that will be sent to recipients. When you create a Triggered Send Definition, you typically set a descriptive name and a unique key so the trigger can be called reliably. The actual recipient data and how it maps into the email content come from the payload provided at trigger time, or from a data source that’s used during the send, rather than from a field you fill in on the Triggered Send Definition itself. That’s why a Data Extension isn’t entered as a field in this definition—the data extension is a data source used by the send, not a metadata field you configure here. Multipart MIME, on the other hand, relates to how the email content is delivered (the HTML/text parts) and is a delivery/content setting rather than a data field for the trigger.

Triggered Sends are defined by identifying information and how the invite is invoked, not by the data that will be sent to recipients. When you create a Triggered Send Definition, you typically set a descriptive name and a unique key so the trigger can be called reliably. The actual recipient data and how it maps into the email content come from the payload provided at trigger time, or from a data source that’s used during the send, rather than from a field you fill in on the Triggered Send Definition itself. That’s why a Data Extension isn’t entered as a field in this definition—the data extension is a data source used by the send, not a metadata field you configure here. Multipart MIME, on the other hand, relates to how the email content is delivered (the HTML/text parts) and is a delivery/content setting rather than a data field for the trigger.