Creating Consent Headers

To use Consent Capture, business admins must first create consent header records to define a country and language for capturing consent. Each consent header is a container for the communication channels available for capturing consent.

By default the English language is enabled. Organizations can enable other languages from the list, or add new languages.

Who can use this feature?

  • Browser, iPad, iPhone Users
  • Users do not require an additional license
  • Business Admin Users, End Users

Configuring Consent Headers for

Ensure Configuring Consent Capture is complete.

Creating a Consent Header as

Business admins must create the same consent type and consent line records for consent headers with the same country but different languages.

To create a consent header:

  1. Navigate to Business Admin > Objects > Consent Headers.
  2. Select Create.
  3. Enter at least the following information:
    • name__v
    • country__v
    • language__v
  4. Set the consent_header_status__v field to Active or Staged after populating all the desired fields:
    • Active — displays consent channels and lines on the Consent Capture screen and prevents further editing
    • Staged — hides the consent records from end users while allowing consent admins to review how the Consent Capture screen displays

    5. After setting the consent_header_status__v field to Active, business admins cannot further edit the consent header, or create and edit related consent types and consent lines.

  5. Select Save.

Managing the Consent Capture Screen as

Business admins can control the help text which displays to end users at the top of the Consent Capture screen. Help text can be anything from overview information to instructions on how to use the functionality. Enter the appropriate help text in the consent_header_help_text__v field on the consent_header__v record.

Admins can disable the global subscription buttons to ensure HCPs only select the specific channels to which they want to consent. Enter a value of 1 in the subscription_option__v field on the consent_header__v record.

Logic for Displaying Consent Headers as

Not all consent headers display when a user navigates to the Consent Capture screen from an account. Different consent headers display for different accounts depending on the country fields for the consent headers, the account, and the user. Admins must understand the following logic to ensure the appropriate consent headers display for an account:

  • If the account’s country is specified, consent headers with matching country fields display
  • If the account’s country is unspecified OR there are no consent headers matching the account’s country, consent headers matching the user’s country display
  • If the account’s country is unspecified AND there are no consent headers matching the user’s country, consent headers with unspecified country fields display

The country__v field on the consent_header__v object is a lookup field to a Country (vcountry__v) record. When selecting the appropriate consent header, the consent header logic uses the following fields to retrieve the account's or user's country:

  • The account's country is retrieved from the vcountry__v field on the account__v object. The vcountry__v field on account__v is a lookup field to a Country (vcountry__v) record, similar to the country__v field on the consent_header__v object.
  • The user's country is retrieved from the country__v field on user__sys. This value is matched to the alpha_2_code__v field on the vcountry__v record specified on the consent header.

Related Topics