Managing Consent with SAP Customer Consent

• Compliance with Data Privacy Laws: It requires consent to terms of service and privacy policies as a prerequisite for using site services.

• Flexible Consent Statements: It allows for additional optional consent statements, providing flexibility in the relationship with the customer.

• Communication Preferences: Users can subscribe to various communication channels and optionally require double opt-in for confirmation.

• User Transparency: It clearly displays saved user data and offers options to withdraw consent and manage communication preferences.

• Consent Vault: It maintains an audit trail of customer agreements to site policies, including the version to which they consented.

• Unified User Database: It provides a holistic view of the customer by consolidating data from various platforms.

• Data Synchronization: It synchronizes consent-based user data to third-party platforms using Dataflows or GConnectors.

• Lite Registration Screens: It offers out-of-the-box lite registration screens for transparent interaction with guest users.

The Consent management dashboard allows you to create and manage versions of different types of user consent regarding user data and privacy.

SAP Customer Data Cloud offers configuring for three types of consent statements:

• Terms of Service: Users must agree to these terms to enjoy your site or app's services.

• Privacy Policy: Users must agree to these terms to enjoy your site or app's services.

• Other Consent Statements: These can be configured as mandatory or optional.

You need to present consent statements on lite and full registration screens as a prerequisite for receiving site services. The consent statement can be displayed in a local language. It may include the purpose or reason for collecting personal data and a link to the document to which they agree. User consent is captured and saved in the consent vault, including consent for mandatory terms, non-mandatory terms, and communication preferences.

It is essential that you add a separate checkbox for each of the relevant statements to the following screens:

• Registration

• Registration Completion

• Privacy

For more information, refer to the Consent Management Components documentation in the SAP Help Portal.

You can add a localized template that includes a locale, the purpose of this statement, and details of the document to which the user agrees.

1. Select the Locale.

2. Enter the Purpose  of this consent statement that is visible to the end user.

3. For Document Location, a PDF file or URL that contains the localized consent statement declaration is displayed to users. Choose one of the following:

   • Document URL: Provide your URL to the legal document. When providing your URL, it is your responsibility to ensure it is persistent and the document is publicly available on the defined URI for as long as required by the country of residence of the end user and also to maintain accurate records of any Consent Templates that were agreed to by the end user.

   • Upload Document: Upload a PDF document up to 5 MB that is stored in SAP Customer Data Cloud servers and available in a public URL. When adding the consent statement to a registration or other screen, you can link to this document for users to review.

4. Select Add.

5. Repeat for any other supported locales that you offer.

You can add Custom Data, which is audited in the Consent Vault. These pairs are saved to the Preferences Schema Object.

1. Select the +  button.

2. Enter the key and the value. Both are saved to the consent statement in string format (custom key-value pairs). The custom data is available on the account when calling accounts.search  or accounts.getAccountInfo.

   Note

   The maximum number of characters for the key is 20, and 256 for the value. The maximum number of custom key-value pairs per consent statement is 50.

3. Save your changes.

Use SAP Customer Data Cloud's screens and the UI Builder to maintain them. 

Update the URL to the one that contains the updated terms of service by using an HTML<a> tag. For example, if you have a checkbox with a label next to it, that reads "I have read and understood the Terms of Service", where "Terms of Service" should link to the updated terms, the label property in the right-hand Properties pane should contain the link according to the following format: 'I have read and understood the <a class="terms-of-service" href="https://terms-of-service-v-2.0">Terms of Use</a>'.

The IDs of the consent statements on your site are:

• terms.siteTerms

• privacy.consentPolicies

• someOtherConsent

When a user clicks the Terms of Use link, the consent document linked to the consent statement should open.

SAP Customer Data Cloud provides several options for flexibly customizing the consent record to your needs.

Use the tags property to set additional dynamic data against consent records in the consent vault.

Tags are appended to a specific consent interaction. For example, suppose that the same consent statement is added to two screens: Registration Completion and Profile Update. In that case, the tags can indicate the screen on which the user granted their consent, and to which interaction the consent corresponds.

Tags can be mapped to a metadata component and support multiple data values using an array structure.

One example use case of tags is that we can define different values for different screen sets. This way, once a user updates consent data, we know which exact screen this consent was initiated from and can capture this info in the consent record.

Activate Consent statements in one of two ways:

• In the Consent dashboard, using the Active toggle.

• In the UI Builder Properties, by setting the field to required on all screens.