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:

{modal="regular"}

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:

{modal="regular"}

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:

{modal="regular"}

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:

{modal="regular"}

For more information, see the documentation on creating custom namespaces.

Identity namespace not in use namespace-not-in-use

Detects obsolete or unused identity namespaces that should be marked for cleanup. This check was previously documented as “Deprecated identity namespace.”

When you select the Identity Namespace Not in Use card, a detail panel opens on the right. The panel shows:

{modal="regular"}

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:

{modal="regular"}

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:

{modal="regular"}

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:

{modal="regular"}

For more information, see the External Source System Audit Details field group documentation.

Primary identity uniqueness primary-identity-uniqueness

Compares how identity namespaces are used as primary identities against how they are defined in identity graph linking rules.

When you select the Primary Identity Uniqueness card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see the identity graph linking rules overview.

Multi-level relationships multi-level-relationships

Detects relationships that are incorrectly defined between two dimensional schemas.

When you select the Multi-Level Relationships card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see the data modeling best practices.

Primary identity field depth primary-identity-field-depth

Verifies that primary identity fields are not nested too deeply in the schema field hierarchy.

When you select the Primary Identity Field Depth card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see the data modeling best practices.

Duplicate field groups across schemas duplicate-field-groups-across-schemas

Detects non-identity field groups that remain active across more than one schema.

When you select the Duplicate Field Groups Across Schemas card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see Add field groups to a schema.

Bot detection field group missing bot-detection-field-group-missing

Verifies that ExperienceEvent schemas include the Bot Detection Information field group.

When you select the Bot Detection Field Group Missing card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see the Bot Detection Information field group documentation.

Zero-length strings allowed zero-length-strings-allowed

Verifies that string fields require a minimum length of one character.

When you select the Zero-Length Strings Allowed card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see the data modeling best practices.

Arrays without constraints arrays-without-constraints

Verifies that array fields define minimum and maximum item constraints.

When you select the Arrays Without Constraints card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see the data modeling best practices.

Consent field group missing consent-field-group-missing

Verifies that profile-enabled schemas include the Consent and Preference Details field group.

When you select the Consent Field Group Missing card, a detail panel opens on the right. The panel shows:

{modal="regular"}

For more information, see the Consents and Preferences field group documentation.

Next steps next-steps