Symptom
Customers may require storing consent and subscription information across multiple countries and languages. A common requirement is to maintain structured data per country/language combination, for example:
- Country/language-specific consent status (e.g., marketing consent, terms acceptance)
- Subscription preferences segmented by region or locale
- Integration-related metadata per region (e.g., sync timestamps with external systems)
This often leads to questions about whether nested or dynamic schema structures should be used in SAP Customer Data Cloud (CDC).
Read more...
Environment
- SAP Customer Data Cloud (CDC)
- Schema Editor (Accounts / Profile schema)
- Consent & Subscription objects
Product
SAP Customer Data Cloud all versions
Keywords
- SAP Customer Data Cloud (CDC)
- Gigya schema
- CDC schema design
- Account schema
- Profile schema
- Custom data fields
- Schema Editor limits
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview