Ensure Configuring Consent Capture is complete.

Business admins can customize the email template of the confirmation email used for double opt-in and consent via confirmation email. The email contains the list of channels for which the HCP is opting in and a link which displays a confirmation message when selected.

To properly set up a consent confirmation email, business admins must perform the following steps:

1. Ensure one of the following features is configured:
   • Using Double Opt-In
   • Capturing Consent Using Confirmation Emails for All Channels
2. Define the confirmation message.
3. Create the email content.
4. Link the email template to the appropriate consent header.

Defining the Confirmation Message

1. Navigate to Business Admin > Objects > Multichannel Messages.
2. Select Create.
3. Select the double_opt_in__v object type.
4. Populate at least the following fields:

• name__v
• message_identifier__v
• consent_confirm_html_file__v — Defines the HTML for a confirmation step before confirming consent. This prevents the recipient’s systems from unintentionally confirming opt-in consent for an HCP. Include the following tokens:
  • {{confirmConsent}} — Displays a confirmation button. Must use the following format:
    Copy

    Confirmation button example

    <form method="post">
                                            <input type="submit" name="{{confirmConsent}}" value="Confirm Consent">
                        </form>

    Selecting this button redirects users to the confirmation message, which displays the content defined in the html_message_file__v field.

    

  • {{consentList}} — Displays the list of consent types and lines to opt-in
• html_message_file__v — Defines the HTML for the confirmation message

Populating the consent_confirm_html_file__v field is optional. If the field is empty, selecting the link in the email automatically opts the user in and redirects them to the page rendering the confirmation message defined in the html_message_file__v field.

Creating the Email Content

Next, create an email template in Vault PromoMats/MedComms with the Email Receipt email template type. The HTML of the email template must reference the message_identifier__v of the appropriate multichannel_message__v record using the {{approvedEmailAction}} token. See Tracking Multichannel Activities from Approved Emails for more information about using the token. Admins can also use the {{insertConsentLines}} token to display all opted in consent lines and their consent types in the email. Syncing the email template to CRM creates an approved_document__v record with the email_receipt__v object type and the email_html__v field populated.

To host the additional confirmation step and the confirmation message in a custom landing page, admins can include a landing page URL in the {{approvedEmailAction}} token in the email template.

Linking the Email Template and Consent Header

Finally, create a multichannel_route__v record with the appropriate object type to link the email template to the consent lines.

For double opt-in:

1. Navigate to Business Admin > Objects > Multichannel Routing.
2. Select Create.
3. Select the double_opt_in_confirmation__v object type.
4. Enter the following information:

• approved_document__v = approved_document__v record for the confirmation email template
• country__v = country__v on appropriate consent_header__v record
• language__v = language__v on appropriate consent_header__v record
• object__v = multichannel_consent__v
• record_type_name__v = object_type__v name of the appropriate consent_type__v record

For capturing consent for all channels:

1. Navigate to Business Admin > Objects > Multichannel Routing.
2. Select Create.
3. Select the consent_confirmation__v object type.
4. Enter the following information:

• approved_document__v = approved_document__v record for the confirmation email template
• country__v = country__v on appropriate consent_header__v record
• language__v = automatically populated with the language__v value from the approved_document__v record
• object__v = multichannel_consent__v
• record_type_name__v = Empty

Additionally, to define a multichannel_route__v record to use when a consent_header__v record does not have a multichannel_route__v record with a matching language__v field, select the Default check box.

In 24R1, business admins can only create one multichannel_route__v record each for the double_opt_in_confirmation__v and consent_confirmation__v object types. In a future release, business admins will be able to create multiple records for different country and language combinations.

Using the Appropriate Multichannel Route Record for Double Opt-In

The following logic determines which multichannel_route__v record with the double_opt_in_confirmation__v object type is used:

• The multichannel_route__v record matching the consent header’s language
• If one does not exist, the record matching the account’s language is used
• If one does not exist, the record matching the user’s language is used
• If one does not exist, the default record is used

Using the Appropriate Multichannel Route Record for Consent Using Confirmation Emails

If there are multiple multichannel_route__v records with the consent_confirmation__v object type for the same country, the following logic determines which record is used:

• The multichannel_route__v record matching the consent header’s language
• If one does not exist, the record matching the account’s language is used
• If one does not exist, the record matching the user’s language is used
• If one does not exist, the default record is used
• If no default record is set, the first record returned is used

Admins can enable custom sharing rules on the multichannel_route__v object for Vaults with end users in different countries using the same language. This allows users to sync only the records for their respective countries and prevents the selection of a record with the matching language but the incorrect country.

After an HCP selects the link from the confirmation email, they must select the confirmation button to confirm their consent. Opt-in consent is confirmed only after the HCP selects the button and the confirmation message displays.