---
schema_version: "1"
id: 597f61d0a403520124a8dd7667f3b34ff1e1d5dd3d61d92186fb39c6c6ec839c
title: Define the Send Definitions Configured in Marketing Cloud Engagement
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/vaccine_packages_hv_define_send_defintions_mc.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.vaccine_packages_hv_define_send_defintions_mc.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c878d854d1b03b2a5dde238f03ddf530eb0350eeb432e567517b8de3225f9ff8
description: Use Occasion objects to define the send definitions for email notifications configured in Marketing Cloud Engagement. When the criteria you define in the send definitions are met, Engagement sends email notifications to users. The context of the email that Engagement sends depends on the criteria specified in the send definition, as defined by the Occasion objects.
products:
  - Salesforce Platform
release: "264"
---
# Define the Send Definitions Configured in Marketing Cloud Engagement

Use Occasion objects to define the send definitions for email notifications configured in Marketing Cloud Engagement. When the criteria you define in the send definitions are met, Engagement sends email notifications to users. The context of the email that Engagement sends depends on the criteria specified in the send definition, as defined by the Occasion objects.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

Make sure that you configured Engagement to send customer Health Verification notifications.

Every time a Health Verification record is created or edited, the system checks to see if an email confirmation must be sent to the person who submitted the Health Verification form.

The Email Mapping object specifies the combination of Health Verification record Status and Method values required to send an email to the user.

The Email Mapping record also specifies the classic email templates to be used for the Header, Body, and Footer values.

The email templates must be written using merge field markup %%FieldName%% rather than { !FieldName}

The send definition includes the Definition Key. The API uses the Definition Key to determine whether to send a confirmation email or a status update email, and in what language to send it.

Here’s how it works at run time.

1. A user submits their Health Verification form on your site.
2. The system generates and stores a Health Verification record for the user.
    
    An agent can begin working on the verification request.
3. The Health Verification record includes data about selections that the user made when submitting the form. The Health Verification record also includes status information based on any work the agent has done processing the request.
    
    Each Occasion Email Mapping that is configured in Health Verification email maps to an Engagement Send Definition.
4. When data from the Health Verification record matches the configuration criteria from the Occasion Email Mapping object, Engagement sends an email.

![Diagram of the workflow for health verification custom metadata](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-vaccine_cloud-264-0-0-production-enus/efba81cf-4df2-478b-9074-4524c9b354ed/vaccine_cloud/images/vaccine_pkg_hv_custom_mdata_65.png)

This table lists and defines the Occasion Email Mapping fields.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="Email Mapping Field Definitions">
        <caption>Email Mapping Field Definitions</caption>
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d3593e122">Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d3593e125">Definition</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Occasion</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p style="margin-bottom:0;">Related Occasion Record</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Verification Method</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p style="margin-bottom:0;">Method the Health Verification record requires to trigger the
                email.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Verification Status </td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p style="margin-bottom:0;">Status the Health Verification record requires to trigger the
                email.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Marketing Cloud Definition Key</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p style="margin-bottom:0;">Name of the Send Definition Key for the journey in
                Engagement.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Verification Site URL</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p style="margin-bottom:0;">Optional parameter that can be passed to Engagement and used
                within the Email template to link users back to the org.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Language</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p style="margin-bottom:0;">Form language</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Email Template Header Name</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p>Name of the Classic Email template that can be used as HTML
                content for the header in the Engagement template.</p>
              <ul>
                <li>Email templates can only be 4,000 characters. When a
                  template exceeds 4,000 characters, Engagement truncates the
                  content and the HTML breaks, giving unexpected results.</li>

                <li>You can’t use Merge Fields in the Classic Email Templates.
                  The merging of values occurs within the Engagement template
                  only. Use the Email Template as an HTML editor.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Email Template Body Name</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p>Name of the Classic Email template that can be used as HTML
                content for the body in the Engagement template </p>
              <ul>
                <li>Email templates can only be 4,000 characters. When a
                  template exceeds 4,000 characters, Engagement truncates the
                  content and the HTML breaks, giving unexpected results.</li>

                <li>You can’t use Merge Fields in the Classic Email templates.
                  The merging of values occurs within the Engagement template
                  only. Use the Email template as an HTML editor.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e122 ">Email Template Footer Name</td>

            <td data-label="Definition" class="slds-cell-wrap" style="vertical-align:top;" headers="d3593e125 ">
              <p>Name of the Classic Email template that can be used as HTML
                content for the footer in the Engagement template. </p>
              <ul>
                <li>Email templates can only be 4,000 characters. When a
                  template exceeds 4,000 characters, Engagement truncates the
                  content and the HTML breaks, giving unexpected results.</li>

                <li>You can’t use Merge Fields in the Classic Email templates.
                  The merging of values occurs within the Engagement template
                  only. Use the Email template as an HTML editor.</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

The Occasion Email Mapping object serves as a bridge for Classic HTML templates, which is an out-of-the-box feature, and the Engagement Email template. It specifies the Engagement Email template (Definition Key), and the Classic HTML email header, footer, and body.

Safety Cloud uses the template to pass content into the Engagement Email, which is eventually sent to the scheduled batch job to the related person account records.

Use the Occasion Email Mapping object to create the mappings between classic email templates and Engagement emails decoratively, as described here.

1. From the App Launcher, type Occasion Email Mappings, and then select Occasion Email Mappings.
2. Select a preconfigured mapping.
    
    ![Screenshot showing the Email Template Fields on the Occasion Email Mapping page](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-vaccine_cloud-264-0-0-production-enus/efba81cf-4df2-478b-9074-4524c9b354ed/vaccine_cloud/images/safety_cloud_img_template_fields.png)
    
    The values specified in the Email Template Header Name, Email Template Body Name, and Email template Footer Name fields reference the API names of Salesforce Classic Email templates.
    
    The Engagement Definition Key serves as the reference ID that connects the Salesforce Org and its related Engagement journey. The content is passed to the email in Engagement and Engagement sends the email to the person who’s health status is verified.

#### See Also

- [Set up Marketing Cloud Engagement to Send Customer Health Verification Notifications](https://help.salesforce.com/s/articleView?id=service.vaccine_packages_send_hv_notifications_mc.htm&release=264.0.0&type=5 "Prepare and send COVID-19 health verification notifications such as confirmation and status updates to your customers. Send notifications using Content Builder and Journey Builder in Marketing Cloud Engagement.")
- [Set up an Email Template for Health Verification](https://help.salesforce.com/s/articleView?id=service.vaccine_packages_setup_email_templates_hv.htm&release=264.0.0&type=5 "You can use Occasion Email Mapping to set up an email template for Health Verification. The template determines the content of the Health Verification email.")
- [Schedule the Confirmation and Verification Emails](https://help.salesforce.com/s/articleView?id=service.vaccine_packages_hv_schedule_notifications_mc.htm&release=264.0.0&type=5 "With the Developer Console, you can schedule the SendConfirmationEmails and the SendVerificationEmails Apex class")