Name: Implementing SAP ECPM without SAP CIAM for B2C in SAP Customer Data Cloud
Uploaded: 2024-5-29
Duration: 302 s
Description: In this video, you'll learn how to implement SAP ECPM without SAP CIAM for B2C. ECPM stands for Enterprise Consent and Preference Management.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

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?

<div><div><div><div><div><div><div>In this video, you'll learn how to implement SAP ECPM without SAP CIAM for B2C. ECPM stands for Enterprise Consent and Preference Management.</div></div></div></div></div></div></div>

Implementing SAP ECPM without SAP CIAM for B2C in SAP Customer Data Cloud

In this video, you'll learn about implementing SAP ECPM without SAP CIAM for B2C.  ECPM stands for Enterprise Consent and Preference Management.  As SAP ECPM is being implemented without SAP CIAM, it is assumed that you are using an external system to handle the registration and authentication.  There are two methods for collecting consent from your customers: either through the SAP Customer Data Cloud Screen-sets, or through your own custom UI. Both approaches will be covered in this video.  The first thing you need to do is to ensure that you configure your consent statements as described in the 'Implementing SAP ECPM' video.  Let’s take a look at our first method of collecting consent by using SAP Customer Data Cloud Screen-sets.  In order to trigger the screen-sets, include the web SDK into the head of your website.  After you have registered your customer in the external system, you must notify SAP Customer Data Cloud of this event, so that a stub account can be created from which to store the consent information.  Please note that an authenticated session should not be created for your customer until consent has been collected.  To notify SAP Customer Data Cloud about the registration event, you can call the accounts.notifyLogin REST endpoint.  This endpoint expects two parameters in addition to the usual authorization parameters which are - siteUID and skipValidation.  Site UID is the unique identifier used by your site to identify the user, and the value for skipValidation should be set to true.  accounts.notifyLogin will return session information.  By default the sessionInfo object contains cookieName and cookieValue string fields, which should be used to create a session cookie with the “name” and “value” specified by the fields.  Once the cookie is set, it will be read by the SAP Customer Data Cloud web SDK and the registration completion screen of your default Screenset will be automatically displayed to the customer.  You should ensure that this screen has all the necessary consent statements included as checkboxes.  When the customer submits the screen, the consent data is set against the SAP Customer Data Cloud account.  The benefit to using Screen-sets is that the logic required to submit the data to SAP Customer Data Cloud is handled automatically by the web SDK.  Finally, an “onLogin” event will be fired.  This is an indicator that all the required consent data has been collected and you are free to create a session for your user.  For subsequent logins, unless a re-consent flow has been triggered from the SAP Customer Data Cloud console, the same procedure will apply but the “onLogin” event will be fired directly after setting the session cookie.  Our second method of collecting consent is without using SAP Customer Data Cloud Screen-sets.  Similar to the earlier approach, after you have registered your customer in your external system, you must notify SAP Customer Data Cloud of this event, so that a stub account can be created in order to store consent information.  As before, you can notify SAP Customer Data Cloud about the event by calling the accounts.notifyLogin REST endpoint.  This time, only siteUID is expected as a parameter, in addition to the usual authorization parameters.  If there are any active consent statements, the call to accounts.notifyLogin will return an error with details of those consent fields, along with a regToken.  At this point, you can display your own custom user interface to collect the necessary consent.  When the screen is submitted by your customer, the consent data needs to be set against the SAP Customer Data Cloud account, by making a call to the accounts.setAccountInfo REST endpoint.  This endpoint accepts the regToken returned from the accounts.notifyLogin endpoint and a preferences object, which represents the consent.  After you get a successful response, you need to make one final REST call to accounts.finalizeRegistration.  This endpoint accepts the same regToken that you used previously.  Once the account is finalized you can use this as an indicator that all the required consent has been provided and can create a session.  For subsequent logins, unless a re-consent flow has been triggered from the SAP Customer Data Cloud console, the same procedure will apply but the call to accounts.notifyLogin will return a normal response.  This is how you implement SAP ECPM without SAP CIAM for B2C, with or without Screen-Sets.  Thank you for learning with us.