Customer Data Cloud (CDC) previously known as Gigya is a significant offering in the product portfolio of SAP Cloud Services. It plays an important role in providing a unified experience to the user. CDC serves as a gateway for the user serving as the identity provider for authorization. The progressive profiling aspect of CDC helps to target customer more efficiently from Marketing perspective and helps business to expand by converting an anonymous visitor to a member.
CDC console is at the heart of the product. All the Configurations, Settings, Identity Access,Customer Insights, Reports, Password policies etc can be configured using the console. Deeper insights on the topics will be mentioned in the follow up blogs. Basically the implementation of Customer Data Cloud is done via the Console.
Console can be rightly termed as the cockpit to control, change or enhance the properties of a Site. It can be accessed via CDC Console
Broadly following features are available in the Console:
Following snapshots in sequence gives a 360 view of the console:
The very first step for the implementation is to create the site domain.
Post the creation of the site. All the configurations related to the Site can be administered using the Settings option available in the CDC Console. There are 5 data centers currently available for CDC which are US, EU, AU, RU, CN. One of the data centers need to be chosen during the Site creation. Russian and Chinese law require that user data of their respective citizens be stored in a dedicated local data center. To meet these data localization law requirements dedicated, physically located data centers are there (RU and CN).
Settings tab in the Console helps to maintain
This gives an overview of Console and its functions. Continuation of this blog post will take a deeper dive into the individual topics mentioned in the blog post like Site Administration, RAAS, etc.
CDC console is at the heart of the product. All the Configurations, Settings, Identity Access,Customer Insights, Reports, Password policies etc can be configured using the console. Deeper insights on the topics will be mentioned in the follow up blogs. Basically the implementation of Customer Data Cloud is done via the Console.
Console can be rightly termed as the cockpit to control, change or enhance the properties of a Site. It can be accessed via CDC Console
Broadly following features are available in the Console:
- Sites - List of Sites Created with the option to create New Sites
- Settings - Configurations related to the Sites
- Reports - Standard reports along with the availability of Identity Query Tool
- Customer Insights - Gives an insight, trends of the Customers
- Identity Access - Manage individual access of the registered users
Following snapshots in sequence gives a 360 view of the console:
The very first step for the implementation is to create the site domain.
Post the creation of the site. All the configurations related to the Site can be administered using the Settings option available in the CDC Console. There are 5 data centers currently available for CDC which are US, EU, AU, RU, CN. One of the data centers need to be chosen during the Site creation. Russian and Chinese law require that user data of their respective citizens be stored in a dedicated local data center. To meet these data localization law requirements dedicated, physically located data centers are there (RU and CN).
Settings tab in the Console helps to maintain
- Basic configurations like Site Settings, Permissions, SSO Configurations, Web SDK configurations.
- RAAS (Registration-as-a-Service) Configurations like Consent Management, Password Policies, ScreenSets, Schema, Webhooks
- IdentitySync management like maintenance of Dataflows and integrations with other systems
This gives an overview of Console and its functions. Continuation of this blog post will take a deeper dive into the individual topics mentioned in the blog post like Site Administration, RAAS, etc.
- SAP Managed Tags:
1 Comment
