All identifiers in this report are synthetic. No real organization, dataset, or schema is represented. Runs fully offline on the Python standard library.
Executive Summary
87
Health / 100 · Grade B
● 5 Critical● 6 Warning● 3 Info
We evaluated 10 datasets, 9 schemas, 3 data views, and 5 segments, then compared the current configuration against the 2026-04-15 baseline. The audit produced 14 findings.
Top issues requiring immediate attention:
Reporting timezone changed on data view 'Meridian Client Engagement'
Dataset 'meridian_client_portal_events' was rebound to a different schema
Field removed from schema 'Advisor CRM Profile v1'
Stitching coverage critically low on 'Meridian Client Engagement'
Dimension 'Advisor AUM Band' maps to a missing field
Health Score by Dimension
Dimension
Score
Grade
Coverage
Notes
Completeness
88
B
Datasets, schemas, and data-view references resolve cleanly.
Freshness
93
A
8/9 production datasets fresh.
Identity Stitching
73
C
2 stitched data view(s) assessed.
Naming & Hygiene
92
A
1 naming/hygiene offender(s) found.
Orphaned Components
91
A
1 orphaned dimension/metric(s).
Overall
87
B
Mean of dimension scores
Configuration Drift (Baseline → Current)
Severity
Area
Finding
Critical
Data Views
Reporting timezone changed on data view 'Meridian Client Engagement'
Critical
Datasets
Dataset 'meridian_client_portal_events' was rebound to a different schema
Critical
Schemas
Field removed from schema 'Advisor CRM Profile v1'
Warning
Datasets
Dataset disabled: 'meridian_email_campaigns'
Info
Data Views
Dataset added to data view 'Meridian Advisor Journey'
Info
Datasets
New dataset added: 'meridian_mobile_advisor_app'
Info
Segments
New segment created: 'Mobile-Only Advisors'
All Findings (Detail)
Critical (5)
Drift: Data Views
Critical Reporting timezone changed on data view 'Meridian Client Engagement'
Reporting timezone changed from 'America/New_York' to 'America/Chicago'. This silently shifts historical comparisons (sessions, day boundaries, or person counts).
Recommendation: Confirm the change was intentional and annotate dashboards so trend breaks are explained.
Drift: Datasets
Critical Dataset 'meridian_client_portal_events' was rebound to a different schema
Schema changed from 'https://ns.adobe.com/meridian/schemas/client_web_events_v1' to 'https://ns.adobe.com/meridian/schemas/client_web_events_v2'. Field-level reporting may break.
Recommendation: Validate field mappings against the new schema.
Drift: Schemas
Critical Field removed from schema 'Advisor CRM Profile v1'
Field 'advisor.aum_band' present at baseline was removed. Any dimension, metric, or segment referencing it will break.
Recommendation: Trace every component built on this field before removing it; restore if still in use.
Identity Stitching
Critical Stitching coverage critically low on 'Meridian Client Engagement'
Person-ID resolution is at 61.4% (method=private-graph, primary=ClientID). Below 75% means a large share of events are counted as anonymous, inflating unique counts and fragmenting journeys.
Recommendation: Audit the identity graph and event-level identity population; verify the primary identity is set and populated on all attached datasets.
Orphaned Components
Critical Dimension 'Advisor AUM Band' maps to a missing field
In data view 'Meridian Advisor Journey', the dimension is sourced from 'advisor.aum_band', which no longer exists in any attached schema. The component will return null/empty.
Recommendation: Repoint the dimension to a valid field or restore the field in the schema.
Warning (6)
Completeness
Warning Data view 'Meridian Client Engagement' includes a disabled dataset
Dataset 'meridian_email_campaigns' (ee5f6a7b8c9d0e1f2a3b4c5d) is disabled but still attached to data view dv_mc_b2c3d4e5f6a7. Its data will quietly stop flowing into reports.
Recommendation: Re-enable the dataset or detach it from the data view and communicate the metric impact to stakeholders.
Completeness
Warning Data view 'Meridian Marketing & Events' includes a disabled dataset
Dataset 'meridian_email_campaigns' (ee5f6a7b8c9d0e1f2a3b4c5d) is disabled but still attached to data view dv_mc_c3d4e5f6a7b8. Its data will quietly stop flowing into reports.
Recommendation: Re-enable the dataset or detach it from the data view and communicate the metric impact to stakeholders.
Warning Test/scratch dataset 'SANDBOX_lead_scoring_test' is enabled in production org
Dataset cc9d0e1f2a3b4c5d6e7f8a9b uses a scratch prefix yet is enabled. Scratch datasets in a production org inflate cost, pollute the schema picker, and risk accidental inclusion in data views.
Recommendation: Disable or delete scratch datasets, or move them to a development sandbox.
Staleness
Warning Dataset 'meridian_aum_snapshot' has stopped receiving data
Last batch was 13.1d ago (last_batch_at=2026-06-07T05:00:00Z). The dataset is enabled and tagged production but ingested 0 records in the last 24h.
Recommendation: Check the ingestion source / data feed for this dataset; a broken pipeline silently degrades every report and audience built on it.
Info (3)
Drift: Data Views
Info Dataset added to data view 'Meridian Advisor Journey'
Dataset dd0e1f2a3b4c5d6e7f8a9b0c was attached to the data view.
Recommendation: Verify metrics did not double-count after the addition.
Drift: Datasets
Info New dataset added: 'meridian_mobile_advisor_app'
Dataset dd0e1f2a3b4c5d6e7f8a9b0c (schema https://ns.adobe.com/meridian/schemas/advisor_mobile_events_v1) appeared since the baseline snapshot.
Recommendation: Confirm the new dataset is intentional and governed (schema, naming, data view membership).
Drift: Segments
Info New segment created: 'Mobile-Only Advisors'
Segment seg_mc_e5f6a7b8 appeared since baseline.
Recommendation: Confirm ownership and activation targets for the new audience.
Prioritized Recommendations
[Critical] Reporting timezone changed on data view 'Meridian Client Engagement' — Confirm the change was intentional and annotate dashboards so trend breaks are explained.
[Critical] Dataset 'meridian_client_portal_events' was rebound to a different schema — Validate field mappings against the new schema.
[Critical] Field removed from schema 'Advisor CRM Profile v1' — Trace every component built on this field before removing it; restore if still in use.
[Critical] Stitching coverage critically low on 'Meridian Client Engagement' — Audit the identity graph and event-level identity population; verify the primary identity is set and populated on all attached datasets.
[Critical] Dimension 'Advisor AUM Band' maps to a missing field — Repoint the dimension to a valid field or restore the field in the schema.
[Warning] Data view 'Meridian Client Engagement' includes a disabled dataset — Re-enable the dataset or detach it from the data view and communicate the metric impact to stakeholders.
[Warning] Data view 'Meridian Marketing & Events' includes a disabled dataset — Re-enable the dataset or detach it from the data view and communicate the metric impact to stakeholders.
[Warning] Dataset disabled: 'meridian_email_campaigns' — Verify this was intentional; downstream reports will show a step-change drop.
[Warning] Test/scratch dataset 'SANDBOX_lead_scoring_test' is enabled in production org — Disable or delete scratch datasets, or move them to a development sandbox.
[Warning] Dataset 'meridian_aum_snapshot' has stopped receiving data — Check the ingestion source / data feed for this dataset; a broken pipeline silently degrades every report and audience built on it.