Schemas and identities health checks
The schemas and identities health checks scan your schemas and identity namespaces for missing best practices and misconfigurations that lead to incomplete identity resolution, inflated profile counts, and inaccurate activation.
Identity field validation identity-field-validation
Scans to ensure identity fields have minimum and maximum length constraints and regex pattern rules for data integrity.
When you select the Identity Field Validation card, a detail panel opens on the right. The panel shows:
- Description: Scans to ensure identity fields have min/max lengths and regex pattern rules for data integrity. Lists affected schemas and fields.
- Impact: If identity fields in schemas do not have min/max lengths and pattern validations set, it can lead to inconsistent data, which can compromise integrity and quality of data.
- General areas of impact: Low-quality identifiers in Identity Service; unreliable stitching.
- Experience League Documentation: A link to best practices for data modeling.
- Affected Schemas: A list of affected schemas, each with an expander to view more details and a link to open the schema.
For more information, see the data integrity tips in the schema best practices documentation.
Identity graph linking rules identity-graph-linking-rules
Verifies that identity graph linking rules are configured for a sandbox to prevent collapsed profiles.
When you select the Identity Graph Linking Rules card, a detail panel opens on the right. The panel shows:
- Description: Verifies that proper linking rules are configured to prevent collapsed profiles. It shows current rule status and unique-per-graph identities.
- Impact: If identity graph linking rules are not set, certain data could try to merge multiple disparate profiles into a single profile. To prevent unwanted merges, configurations provided through identity graph linking rules should be used.
- General areas of impact: Collapsed or merged profiles.
- Experience League Documentation: A link to the Identity Graph Linking Rules overview for more information.
- Configure linking rules: When the check fails, a button appears so you can configure linking rules directly from the panel.
For more information, see the identity graph linking rules overview and the implementation guide.
People and non-people identity configuration people-non-people-identity
Validates the correct use of people and non-people identity types across schema classes.
When you select the People & Non-People Identity Config card, a detail panel opens on the right. The panel shows:
- Description: Validates proper use of identity types across schema classes. Lists misconfigured schemas and highlights wrong assignments.
- Impact: If a non-people entity is given a person identity, this will inflate the profile count and make this data ineligible as a lookup. If a person entity is given a non-people identity, the data is not available for streaming or edge segmentation.
- General areas of impact: Incomplete identity graphs; inflated profile counts; lookup misuse.
- Affected Schemas: A list of schemas with issues. Expand a schema row to see the path, identity name, and schema type for each misconfiguration. Use the link icon to open the schema.
For more information, see the identity type documentation and the schema best practices.
Custom identity namespace description namespace-missing-description
Scans to ensure that custom identity namespace metadata and descriptions are complete.
When you select the Custom Identity Namespace Description card, a detail panel opens on the right. The panel shows:
- Description: Scans to ensure namespace metadata and descriptions are complete. Displays namespaces and owners with empty description fields.
- Impact: Setting a description on a custom identity namespace enhances clarity by providing context of the purpose of each namespace. This helps team members and stakeholders quickly understand the function of each namespace without confusion.
- General areas of impact: Debug or usage confusion; unclear validation intent.
- Experience League Documentation: A link to Create Custom Namespaces for further information.
- Affected namespaces: A list of custom identity namespaces that are missing descriptions. Use the link icon next to each namespace to view or edit it.
For more information, see the documentation on creating custom namespaces.
Deprecated identity namespace deprecated-namespace
Detects obsolete or unused identity namespaces that should be marked for cleanup.
When you select the Deprecated Identity Namespace card, a detail panel opens on the right. The panel shows:
- Description: Detects obsolete or unused identity namespaces for cleanup. Lists unused namespaces with last usage timestamp or schema reference.
- Impact: Identity namespaces not used in any schema should be marked for removal by adding a “DEPRECATED” or “DO NOT USE” tag to their names. Deletion of identity namespaces is not currently supported.
- General areas of impact: Confusion and mislabeling risk.
- Experience League Documentation: A link to Obsolete Identity Namespaces for further documentation.
- Affected namespaces: A list of obsolete or unused identity namespaces. Use the link icon next to each namespace to view or manage it.
For more information, see the Experience Cloud knowledge base article on obsolete namespaces.
Non-person identity on relationship field non-person-identity-relationship-field
Flags schema fields that carry both an identity descriptor and a relationship descriptor at the same time.
When you select the Non-Person Identity on Relationship Field card, a detail panel opens on the right. The panel shows:
- Description: Explains that putting a relationship descriptor on a schema field establishes a direct, dynamic join between two separate schemas. It tells the Real-Time Customer Profile store and Segment Builder that a field in the primary or source schema acts as a foreign key pointing to a lookup or dimension record in the target schema. This check inspects for schema fields that carry both an identity descriptor and a relationship descriptor for the same field.
- Impact: These descriptors are mutually exclusive, and including both on the same field is a data modeling error. The results may include incorrect segmentation and audience activations.
- General areas of impact: Audience quality.
- Experience League Documentation: A link to XDM schema composition for identity.
- Affected schemas: A list of schemas with fields that have conflicting descriptors, when applicable. When no issues are detected, the panel shows a Check Passed confirmation instead.
For more information, see the schema composition documentation.
Multi-entity relationship count multi-entity-relationship-count
Monitors the number of multi-entity relationships defined in a sandbox as they approach the platform limit.
When you select the Multi-Entity Relationship Count card, a detail panel opens on the right. The panel shows:
- Description: Explains that multi-entity relationships link primary entities, such as Real-Time Customer Profiles or ExperienceEvents, to secondary dimension entities, such as product catalogs, store locations, or business accounts. This check inspects whether the limit of 5 multi-entity relationships defined in the sandbox is exceeded.
- Impact: High cardinality and excessive schema joins increase computational complexity across the Real-Time Customer Profile store. Exceeding the limit may degrade Segmentation Service performance and increase audience evaluation latency.
- General areas of impact: Batch segmentation.
- Experience League Documentation: A link to best practices for data modeling.
For more information, see the data modeling best practices and the multi-entity segmentation tutorial.
Missing audit field group missing-audit-field-group
Verifies that XDM Individual Profile schemas include the External Source System Audit Details field group.
When you select the Missing Audit Field Group card, a detail panel opens on the right. The panel shows:
- Description: Verifies that XDM Individual Profile schemas include the External Source System Audit Details field group, which is required for tracking record provenance and update timestamps.
- Impact: Without audit fields, there is no record-level visibility into when data was ingested into Experience Platform, which makes it difficult to troubleshoot stale or duplicate records.
- General areas of impact: Inability to audit external data changes.
- Experience League Documentation: A link to the External Source System Audit Details field group.
- Recommendation: Where missing, add the External Source System Audit Details field group.
- Affected schemas: A list of schemas that are missing the field group. Use the link icon next to each schema to open it.
For more information, see the External Source System Audit Details field group documentation.
Next steps next-steps
- Return to the health checks overview to explore other check categories.
- Learn about schema best practices for designing reliable data models.
- Understand identity graph linking rules to prevent profile collapse.
- Review identity namespace documentation for namespace management best practices.