Capturing and Verifying Consent Records in a Web Application

Objective

After completing this lesson, you will be able to capture and verify a customer consent record.

Consent Record

A consent record is a log of each user’s consent actions and preferences. User consent is captured and saved in the consent vault, including consent for mandatory terms, non-mandatory terms, and communication preferences.

Consent Vault screen in SAP Customer Data Cloud. Orange outline around the consent vault menu option and around the consent vault screen.

Consent Vault: The consent vault is a log of interactions between the site and site users. It logs the site user's consent to process their data. Data can be stored in the consent vault for up to 7 years (84 months).

You can use the consent vault to easily view and search the history of all consent records on your site such as:

  • Search by specific time period or date.
  • Filter by actions (consent granted, withdrawn, or renewed).
  • View the time stamp and version of a signed consent.

The consent interaction between the user and your site is captured and recorded in SAP Customer Data Cloud’s database (in a JSON object known as the Preferences Object). This interaction includes several fixed components, such as the type and expiration date of the consent statement, the version number, the country/region, and the time stamp of the consent action.

SAP Customer Data Cloud provides you with several options to customize the consent record to your business needs. These customization options include:

  • Custom Data: This allows you to add any additional information to the consent object, such as the legal entity that maintains it or the administrator who created it.
  • Tags: Appended to a specific consent interaction. For example, if the same consent statement is added to two different screens (Registration Completion and Profile Update), the tags can indicate the screen on which the user granted their consent.
  • Entitlements: An addition or appendix to the consent interaction. It’s an easy way to ask for additional input from a user without having to trigger the re-consent process.

Capture a Consent Record in SAP Customer Data Cloud

Once a Consent Statement is created and configured, you can link it to a Screen-set. This allows the company to keep consent record interactions. This screen capture is an example of a Terms of Use consent that was added to the Registration screen. 

Terms of Conditions option in a Registration screen-set.

Capturing a consent record enables the end user to:

  • Access the consent document.
  • Read and understand how their personal information is being used.
  • Determine their data protection level and privacy preferences.

Linking a Consent Statement: To link a Consent Statement to a screen-set:

  1. Determine which screen-set to configure.
  2. Ensure you have the proper corresponding consent statement.
  3. Add a checkbox to the screen-set and modify it to reflect the corresponding consent type.

The following exercises below, first you'll learn how to link a Consent Statement using the UI Builder to capture and record the customer's consent. Then, you'll learn how to check to ensure the customer consent record was accurately recorded.

How to Capture Consent Records in the UI Builder

Verifying a Consent Record

In the following exercise you'll learn how to check whether a customer consent was accurately recorded.

Log in to track your progress & complete quizzes