Name: Implementing SAP ECPM in SAP Customer Data Cloud
Uploaded: 2025-7-29
Duration: 515 s
Description: In this video you’ll learn step-by-step how to implement SAP Enterprise Consent and Preference Management (ECPM) in SAP Customer Data Cloud. The video guides you through the entire process of creating and configuring a new consent statement, managing consent versioning, and integrating consents into your registration and profile update screens using the UI Builder.

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

Personalize your learning.

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

This browser is not supported

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn’t find what you’re looking for

To continue, please log in

Your session has timed out

Validate your skills and learning by completing the certification exam and gain a highly recognised accreditation.

Book your certification exam

Complete the assessment to validate your SAP PartnerEdge competency qualifications.

Ready to take your assessment?

Learn about the key features and essentials in the latest release to help you prepare for the Stay Certified assessment.

Prepare for assessment

Learn new skills you need at your own pace with our bite-sized lessons.

Prepare for certification

In your My Learning account you can view your certification and learn how to take your Stay Certified assessment.

Ready to take your Stay Certified assessment?

Explore {title} at SAP Learning. Find out more!

Assessment

Course Completion

Knowledge Badge

Overview

Support Resource

Certification Exam

Theoretical Exam

Schedule

External Course

Practical Exercise

Practical Test

External Hands-On

External Resource

Learning Journey

Learning Journey Assessment

Lesson

Live Session

Practice System

Quiz

Scenario Based Assessment

Course Assessment

Course

Stay Certified

Subscription

System Based Assessment

Test Out

Unit

Video

Video Playlist

Week

Want to remove this from your Learning List?

Your exclusive access to the SAP Learning Hub, event edition is ready. <link>Start learning now.</link>

Access activated

You can now register for free Live Sessions.

<div><div><div><div><div>In this video you’ll learn step-by-step how to implement SAP Enterprise Consent and Preference Management (ECPM) in SAP Customer Data Cloud. The video guides you through the entire process of creating and configuring a new consent statement, managing consent versioning, and integrating consents into your registration and profile update screens using the UI Builder.</div></div></div></div></div>

Implementing SAP ECPM in SAP Customer Data Cloud

In this video, you will learn about Implementing SAP Enterprise Consent and Preference Management, or ECPM. We will create and configure a new consent statement, manage consent versioning, and add it to screen sets using the UI Builder. Let’s get started with creating a new consent statement. Once you log into the SAP Customer Data Cloud console, navigate to Consent Statements, under Data Privacy, in the left-hand menu. SAP ECPM allows you to configure three types of consent statements: Terms of Service, Privacy Policies, and Other Consent Statements. When using screen sets, any active consent must be mapped to a checkbox on the registration form. When active, Terms of Service and Privacy Policy are always mandatory, and a customer cannot complete a registration without providing their explicit consent.  The Other Consent Statement type can be used for capturing consent for a variety of purposes, including marketing consent, sharing data with third parties, or data processing for personalization.  Other consent statements can be made mandatory or optional. For site groups, consent statements can be created and configured on the parent site and activated or de-activated for individual child sites. Click on the ‘+ Add’ button to create a new consent statement. Next, select the Type and enter the ID. The ID is the field name created in your schema. After defining the ID, you must choose how to version the consent. You can version either by date or by number. “Consent locale enforcement” defines the expected consent behavior for cases when a user switches between different locales. The “Strict” option means consent is required when a new version of the consent statement exists on the locale the user is currently using. “Not Strict” means consent is required only if the version on the locale that was accepted last has changed. In this video, we’ll just use the default “Strict” option. With the new consent solution, you can now configure consent level retention periods. The default retention period is 36 months. You can configure it on a global level on the Consent Vault page, under Data Privacy. If needed, you can click on the “Change” button and specify the retention period for the current consent statement on the “Confirm Retention Period Change” popup.  In this video, we’ll simply use the default retention period. You can add a localized template that includes a locale, the purpose of the template, and details of the document to which the user is agreeing.  You can add a new language by setting the locale.  With the new consent solution, we can now specify the versions on a localization template or locale level, instead of on a consent statement level. The value of the “Version” will be written against the customer’s account data when they register. account data when they register. Input an appropriate date or version number for this consent depending on the versioning scheme on the consent statement level. Please note, once the new consent is saved, the value of the ‘Versioning” field can no longer be changed. The “Re-consent cut-off” value controls the document versioning process and supports both major and minor versioning. To trigger a major version update of your legal document, where all users must have to re-consent, the value of the ‘re-consent cut-off’ field must match the value of the ‘Version” field. Any user who consented to a version anterior to the number or date specified under ‘Re-consent cut-off’, will be prompted to re-consent during their next login. For a minor version update of your consent document, there is no need to change the ‘Re-consent cut off’ value. Next define the “Purpose” of the locale template that will be visible to the end user. Specify the Document URL or Upload Document. The document must be a PDF and must be on a secure https URL. When you choose to upload a PDF document, it is stored in SAP Customer Data Cloud servers and available via a public URL. Both the “Purpose” and Document URL are recorded in the consent vault against customer consent interaction. Please note that any document URLs provided must be persisted and the document must be available on the defined URL for as long as is required by the country of residence of the end-user. It is your responsibility to maintain accurate records of any Consent Document that were agreed to by the end-user. Depending on what you would do next with the locale template, you can configure “Document Status” to be “Save as Draft” (the default) if you intend to come back later and update the template, or “Published” if you’re ready to finalize the template definition and use it in your Customer Data Cloud applications. Let’s choose “Published” for our example. Once you are happy with the configurations, click on the Add button to add the consent statement and locale template to the site. With the new consent solution, you can also add Custom Data specifically to the locale templates,  instead of the whole consent statement. One use case for custom data would be to specify a retention period for the consent statement.  On the “Edit Consent Statement” page, click on the “Custom Data” tab to add custom data on the consent statement level, and then click on the Expand button to expand the key value pairs. Enter “retentionPeriod” as the key and "36" for the value, then click on Save. As mentioned, you can also add custom data on a locale template. Click on the three-dot action menu of a locale template at the bottom and choose Edit Locale. Click the Custom Data tab and then the expand button to add the key value pairs as custom data, for example customKey and customValue. Let’s take a look at the data schema which is created as a result of the consent definition. Terms of service consent statements are always pre-pended with the word ‘terms’ and privacy policy consent statements are always pre-pended with ‘privacy’. Other consent statements do not have anything pre-pended. This particular schema shows consents created with a version number, instead of a date. The ‘currentDocVersion’ and ‘minDocVersion’ fields would be replaced with currentDocDate and minDocDate if the version by value was set to date.  In this section we will add the previously created consent statements to the Screen-Set using the UI Builder. Navigate to the UI Builder menu under “User Interfacing” in the SAP Customer Data Cloud Console and open the Default-RegistrationLogin Screen-Set in the UI Builder. Drag and drop a Checkbox control to the Registration screen to the Registration screen and map it to the isConsentGranted property of the new consent object in the Preferences schema. Note that any consent statement that is set to "active" for your site must be included in your registration and registration completion screens. Otherwise, users will not be able to complete their registration or renew their consent. The consent purpose and document URL, or custom data defined earlier in this video can be reflected on the screens using a placeholder. In this video you can see the ‘documentUrl’ as a Placeholder under the label value. Before you save your changes, make sure the ‘Checked by Default’ drop-down is set to ‘No’. Repeat the process for the Registration Completion screen. The Privacy screen available in the ProfileUpdate screen-set displays to registered users the details of the consent statement to which they agreed. The consent widget is available in the profile update screen-set. It shows the customer a snapshot of their mandatory consent interactions. In the ‘Properties pane’, map the widget to the relevant consent object.   Non-mandatory consents should be mapped to a checkbox, so the user has the ability to revoke their consent. This completes the consent creation process. Thank you for watching.