What is AMPScript usage for transactional messages?

What is AMPScript usage for transactional messages?

• A. TriggeredSend object Create method
• B. TriggeredSend object InvokeCreate function
• C. REST API route /messageDefinitionSends
• D. Landing pages are not supported in Marketing Cloud

Answer: (B)

Transactional messages are delivered in real time through a Triggered Send. To trigger one from AMPScript, you use the TriggeredSend object and, specifically, the InvokeCreate function. You align the invocation with a pre-defined Triggered Send Definition (which links to the email content and the data context) and supply the subscriber data and any personalization attributes. Invoking the creation is what actually sends the message immediately; it activates the defined transactional send. Using a Create method would only set up or define the Triggered Send without delivering it. The REST API route /messageDefinitionSends is a way to trigger a transactional send from external systems, not from AMPScript. The statement about landing pages isn’t the mechanism used for AMPScript transactional messages.

Transactional messages are delivered in real time through a Triggered Send. To trigger one from AMPScript, you use the TriggeredSend object and, specifically, the InvokeCreate function. You align the invocation with a pre-defined Triggered Send Definition (which links to the email content and the data context) and supply the subscriber data and any personalization attributes. Invoking the creation is what actually sends the message immediately; it activates the defined transactional send.

Using a Create method would only set up or define the Triggered Send without delivering it. The REST API route /messageDefinitionSends is a way to trigger a transactional send from external systems, not from AMPScript. The statement about landing pages isn’t the mechanism used for AMPScript transactional messages.