Given a customer scenario, send and deploy an email campaign to meet the customer requirement.
Several settings need to be defined to send emails with Marketing Cloud. The Send Definition feature can be used to save and reuse such send settings. This is supported for email sends initiated within Marketing Cloud and triggered from external systems.
Emails can be sent directly with send tools provided in Content Builder and Classic Content. In addition, email sends can also be saved in Send Definitions for later sending. Saved Send Definitions can then be started either manually or triggered automatically based on action within or outside Marketing Cloud. The relationship between Templates, Emails, and Send Definitions can be visualized as follows:
Send Definitions can be started manually or triggered via API calls. Consequently, two types of Send Definitions exist:
User-Initiated Send Definitions are started manually or automatically based on events in Marketing Cloud. The definition of what starts a triggered send is maintained in Marketing Cloud, such as in Automation Studio. User-initiated emails can be sent to Subscriber Lists, Groups, Data Extensions with Publication Lists, and Data Filters.
Triggered Send Definitions which are started automatically based on events outside Marketing Cloud. The definition of what starts a triggered send is maintained in external systems using API calls. Triggered emails are sent to individual recipients and can therefore be used to send automated and personalized responses to subscriber activities. Receipts of Triggered emails can be added as Subscribers to Subscriber Lists or Data Extensions, and their Subscriber Status can be updated automatically.
Triggered sends separate email content from emails sends. Like this, the email content and tracking can be maintained in Marketing Cloud, while the logic to trigger email send is maintained in external systems. This allows making changes in email content and tracking emails in Marketing Cloud.
Independent of whether emails are sent directly using Send Flow, or later using user-initiated or triggered Send Definitions, the following information is required to send emails in Marketing Cloud:
Defines the emails to be sent.
Defines the Send Classification and therefore the Send and Delivery Profile to be used.
Defines whether email variables for each send are logged in a Data Extension. This Data Extension must first be created, and the email message must update the Data Extend with AMPscript.
Defines the audience that receives the email. Depending on whether Subscriber Lists or Data Extensions are used, different combinations of Lists, Groups, and Data Extension can be specified.
Defines the test audience that receives the email. Depending on whether Subscriber Lists or Data Extensions are used, different combinations of Lists, Groups, and Data Extension can be specified.
Defines the message format of the email to be sent. The multi-part MIME option specifies that a text and HTML version is sent for emails which are not Text Only.
Defines whether emails should be tracked and the spring location of tracking information.