Configuring Contact Point Consent Settings

The Contact Point Consent Configuration settings page is available in the D365 Marketing Model driven-app included with the Anthology Reach solution.

The Contact Point Consent Configuration settings are a list of default OOTB configurations that are used by the Contact - Create Realtime Marketing Contact Point Consents workflow to automatically create consent records. For information on the Contact - Create Realtime Marketing Contact Point Consents workflow, see Managing Consent for Email and SMS (Real-time Journeys)

When managing consent across various communication channels, it is crucial to maintain accurate and up-to-date consent records for each channel. Here’s how you can effectively handle consent for different channels:

Automated Consent Record Generation: Configure rules to automatically generate consent records when certain events occur. For example, creation of a contact record, updates to existing contact details (such as phone numbers or email addresses), or changes in contact preferences (e.g., 'Do Not Email' or 'Do Not SMS' field updates) can trigger the creation of consent records with a status of Not Set. This ensures that consent records are always in place and can be customized as needed.

Example: Suppose you want to create a Contact Point Consent Configuration that triggers the creation of consent records. For instance, when a contact is created, the system should automatically generate a consent record for the email and phone number associated with that contact based on the configured compliance profile, including its associated purpose and enforcement model. If consent is not explicitly collected from the contact touchpoint, the initial Consent Status should be set to Not Set.

To meet the above requirement, you can create a Contact Point Consent Configuration record with the following field values:

Channel Compliance Profile Purpose Topic Enforcement Model Create Consent
Email default Commercial   Restrictive Yes

Once consent records are created, you can manage and customize consent for each contact touch point separately.

The following topics provide information on OOTB Contact Point Consent Configuration settings and the steps to edit/create these settings:

Add a Contact Point Consent Configuration

Prerequisite - Users performing this task must have the CMC – Business Unit Administrator and CMC – Global Business Administrator roles. For more information, see Security Roles.

Reach users can either edit the sample configurations or create new configurations as per their requirement to create consent records. Perform the following steps in the Marketing model-driven app in the Reach environment to add a Contact Point Consent Configuration record:

  1. In the Settings area click Contact Point Consent Configuration under the Consent configuration (Reach) sub-area.

  2. Click New.

  3. In the New Contact Point Consent Configuration page specify the following details:

    1. Channel - Select the channel for which the consent record must be created.

    2. Compliance Profile - Select the required Compliance Profile.

    3. Purpose - Select the purpose associated with the Compliance Profile.

    4. Topic - Select the topic associated with the consent purpose linked to the Compliance Profile.

    5. Enforcement Model - Select the enforcement model for the consent purpose linked to the Compliance Profile.

    6. Create Consent - It can be set to one of the following values:

      • Yes - Indicates a consent record need to be created.

      • No - Indicates a consent record need not be created.

    7. Consent Status - Indicates the status for the consent record. It can have one of the following values.

      • Not Set

      • Opted In

      • Opted Out

    8. Contact Preference Field - Comma separated list of schema names of the Contact Preference fields, which will be used by the workflow for creating the consent record.

    9. Contact Preference Field Value - Comma separated list of values of the Contact Preference fields.

  4. Click Save to save the Contact Point Consent Configuration record.

Note: To edit an existing Contact Point Consent Configuration record, select the record and click Edit, and update the required field values.

Sample Contact Point Consent Configurations Shipped Out-Of-The-Box

The following table provides information on the Contact Point Consent Configuration records that are shipped out-of-the-box (OOTB).

Name Channel Compliance Profile Purpose Topic Enforcement Model Create Consent Consent Status Contact Preference Field Contact Preference Field Value
Email - default - Commercial - Disabled Email default Commercial   Disabled No Not Set donotbulkemail, donotemail Allow, Allow
Email - default - Commercial - Non-Restrictive Email default Commercial   Non-Restrictive Yes Not Set donotbulkemail, donotemail Allow, Allow
Email - default - Commercial - Restrictive Email default Commercial   Restrictive Yes Not Set donotbulkemail, donotemail Allow, Allow
Email - default - Tracking - Disabled Email default Tracking   Disabled No Not Set msgdpr_donottrack Allow
Email - default - Tracking - Non-Restrictive Email default Tracking   Non-Restrictive Yes Not Set msgdpr_donottrack Allow
Email - default - Tracking - Restrictive Email default Tracking   Restrictive Yes Not Set msgdpr_donottrack Allow
Email - default - Transactional - Disabled Email default Transactional   Disabled No Not Set donotbulkemail, donotemail Allow, Allow
Email - default - Transactional - Non-Restrictive Email default Transactional   Non-Restrictive Yes Not Set donotbulkemail, donotemail Allow, Allow
Email - default - Transactional - Restrictive Email default Transactional   Restrictive Yes Not Set donotbulkemail, donotemail Allow, Allow
Text Message - default - Commercial - Disabled Text Message default Commercial   Disabled Yes Not Set cmc_donotsmstext Allow
Text Message - default - Commercial - Non-Restrictive Text Message default Commercial   Non-Restrictive Yes Not Set cmc_donotsmstext Allow
Text Message - default - Commercial - Restrictive Text Message default Commercial   Restrictive Yes Not Set cmc_donotsmstext Allow
Text Message - default - Tracking - Disabled Text Message default Tracking   Disabled Yes Not Set msgdpr_donottrack Allow
Text Message - default - Tracking - Non-Restrictive Text Message default Tracking   Non-Restrictive Yes Not Set msgdpr_donottrack Allow
Text Message - default - Tracking - Restrictive Text Message default Tracking   Restrictive Yes Opted In msgdpr_donottrack Allow
Text Message - default - Transactional - Disabled Text Message default Transactional   Disabled No Not Set cmc_donotsmstext Allow
Text Message - default - Transactional - Non-Restrictive Text Message default Transactional   Non-Restrictive No Not Set cmc_donotsmstext Allow
Text Message - default - Transactional - Restrictive Text Message default Transactional   Restrictive No Not Set cmc_donotsmstext Allow