Health Checks
Health checks scan your schemas, identities, and datasets in your sandbox and provide a summary of issues that you can explore and troubleshoot with AI Assistant.
Poor schema and identity configurations lead to significant downstream issues, including incorrect profile creation, failed segment qualification, and inaccurate activation. These issues are difficult to detect and often require specialized expertise to diagnose. Health checks shift your approach from reactive troubleshooting to proactive, preventative maintenance.
With health checks, you can:
- Detect configuration issues early: Identify missing best practices, misconfigurations, and patterns that lead to inefficiencies in personalization, activation, and more.
- Receive guided remediation: Get clear guidance on what each issue is and what to do about it.
- Monitor continuously: Currently, health checks run daily automatic scans so that you can catch problems before they become critical failures. The schedule may change in future releases.
Prerequisites prerequisites
To access health checks, you need the View Health Checks access control permission. Contact your system administrator to ensure you have the appropriate permissions.
Access health checks access-health-checks
To access health checks from the Experience Platform UI:
- Select Run and Operate from the left navigation.
- Select Health Checks.
The health checks dashboard displays a summary of your most recent scan results.
Understanding the dashboard understanding-dashboard
The health checks dashboard provides three areas of information to help you assess the state of your implementation.
Objects evaluated objects-evaluated
The Objects evaluated section shows the total number of schemas, identity namespaces, and datasets scanned, along with how many issues were found for each category. This gives you a quick view of the scope and severity of configuration problems in your sandbox.
Scan results scan-results
The Scan results section displays the number of failed checks. A failed check indicates that one or more of the health checks detected configuration issues that require attention. The Last daily health scan completed on timestamp shows when the most recent scan ran.
Identified issues identified-issues
The Identified issues section shows a card for each health check. Each card displays:
- The health check name and a brief description of the issue.
- The number of issues found, or a confirmation that no issues exist.
- A status indicator showing whether the check passed or requires attention.
Select any card to explore the details of that health check.
Available health checks available-health-checks
Health checks currently evaluate seven areas across schema, identity, and dataset configuration. The following table lists all available checks.
These checks target the most impactful data modeling and data lifecycle issues across the platform.
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.
Pseudonymous profile TTL pseudonymous-profile-ttl
Scans that the Pseudonymous Profile Expiration policy is active for the sandbox and lists relevant unauthenticated namespaces.
When you select the Pseudonymous Profile TTL card, a detail panel opens on the right. The panel shows:
- Description: Scans that the Pseudonymous Profile Expiration policy is active for the sandbox and lists relevant unauthenticated namespaces.
- Impact: Accumulation of pseudonymous profiles is the lead cause of Addressable Audience overages. Without a P-TTL policy, profiles reside indefinitely. This bloat slows real-time segmentation.
- General areas of impact: License compliance, as profiles that should have expired still count toward the total Addressable Audience. Performance, as bloated profiles increase the latency of profile lookups. No marketing value of excessive storage.
- Experience League Documentation: Links to pseudonymous profile expiration documentation and data management best practices.
- Configure profile settings: A button to navigate to profile settings and activate the expiration policy.
For more information, see the documentation on pseudonymous profile expiration and data management best practices.
Experience Event datasets TTL experience-event-datasets-ttl
Scans Lake and Profile event datasets to ensure that data expiration is appropriately configured.
When you select the Experience Event Datasets TTL card, a detail panel opens on the right. The panel shows:
- Description: Scans Lake and Profile event datasets to ensure that Experience Event Time to Live (E-TTL) is appropriately configured to prevent data bloat and performance degradations.
- Impact: Absence of a defined E-TTL leads to infinite data retention in the Profile Store and Data Lake. This may lead to degraded performance for ingestion and segmentation, and can impact Adobe Journey Optimizer performance, including audience qualification and journey execution.
- General areas of impact: Degraded query speeds and slow segmentation due to excessive data volume. System instability.
- Experience League Documentation: A link to Experience Event dataset retention documentation.
- Affected datasets: A list of Lake and Profile event datasets without a configured data expiration. Select a dataset to open it. When no issues are detected, the panel shows a Check Passed confirmation instead.
For more information, see the documentation on Experience Event dataset retention and Experience Event expirations.
Next steps next-steps
After reviewing your health check results, explore the following resources to deepen your understanding:
- 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.
- Configure pseudonymous profile expiration to manage data retention and reduce Addressable Audience overages.
- Set up Experience Event dataset retention to prevent data bloat and performance degradation.
- Explore other Run and Operate tools including Job Schedules for batch operation visibility.