Default Guardrails for Real-Time Customer Data Platform B2B Edition
Last update: Mon Jan 20 2025 00:00:00 GMT+0000 (Coordinated Universal Time)
The limits outlined in this document represent the changes enabled by Real-Time Customer Data Platform B2B Edition. For a complete list of default limits for Real-Time CDP B2B Edition, combine these limits with the general ÃÛ¶¹ÊÓÆµ Experience Platform limits outlined in the
guardrails for Real-Time Customer Profile data documentation.
Real-Time Customer Data Platform B2B Edition enables you to deliver personalized cross-channel experiences based on behavioral insights and customer attributes in the form of Real-Time Customer Profiles and Account Profiles. To support this new approach to profiles, Experience Platform uses a highly denormalized hybrid data model that differs from the traditional relational data model.
Check your license entitlements in your Sales Order and corresponding on actual usage limits in addition to this guardrails page.
This document provides default use and rate limits to help you model your data for optimal system performance. When reviewing the following guardrails, it is assumed that you have modeled the data correctly. If you have questions on how to model your data, please contact your customer service representative.
Most customers do not exceed these default limits. If you would like to learn about custom limits, please contact your customer care representative.
Limit types
There are two types of default limits within this document:
Guardrail type
Description
Performance guardrail (Soft limit)
Performance guardrails are usage limits that relate to the scoping of your use cases. When exceeding performance guardrails, you may experience performance degradation and latency. ÃÛ¶¹ÊÓÆµ is not responsible for such performance degradation. Customers who consistently exceed a performance guardrail may elect to license additional capacity to avoid performance degradation.
System-enforced guardrails (Hard limit)
System-enforced guardrails are enforced by the Real-Time CDP UI or API. These are limits that you cannot exceed as the UI and API will block you from doing so or will return an error.
The limits outlined in this document are constantly being improved. Please check back regularly for updates. If you are interested in learning about custom limits, please contact your customer care representative.
Data model limits
The following guardrails provide recommended limits when modeling Real-Time Customer Profile data. To learn more about primary entities and dimension entities, see the section on entity types in the Appendix.
Primary entity guardrails
The data model limits outlined in this section represent the changes enabled by Real-Time Customer Data Platform B2B Edition. For a complete list of default limits for Real-Time CDP B2B Edition, combine these limits with the general ÃÛ¶¹ÊÓÆµ Experience Platform limits outlined in the
guardrails for Real-Time Customer Profile data documentation.
Guardrail
Limit
Limit Type
Description
Real-Time CDP B2B Edition standard XDM class datasets
60
Performance guardrail
A maximum of 60 datasets that leverage the standard Experience Data Model (XDM) classes provided by Real-Time CDP B2B Edition is recommended. For a complete list of standard XDM classes for B2B use cases, refer to the
schemas in Real-Time CDP B2B Edition documentation.
Note: Due to the nature of Experience Platform’s denormalized hybrid data model, most customers do not exceed this limit. For questions about how to model your data, or if you would like to learn more about custom limits, please contact your customer care representative.
Identity count for individual account in an Identity Graph
50
Performance guardrail
The maximum number of identities in an Identity Graph for an individual account is 50. Any profiles with more than 50 identities are excluded from segmentation, exports, and lookups.
Legacy multi-entity relationships
20
Performance guardrail
A maximum of 20 multi-entity relationships defined between primary entities and dimension entities is recommended. Additional relationship mappings should not be made until an existing relationship is removed or disabled.
Many-to-one relationships per XDM class
2
Performance guardrail
A maximum of 2 many-to-one relationships defined per XDM class is recommended. Additional relationship should not be made until an existing relationship is removed or disabled. For steps on how to create a relationship between two schemas, refer to the tutorial on
defining B2B schema relationships.