Schemas evolve, identity stitching breaks, data views get quietly misconfigured — and the dashboards keep rendering. Know exactly where your implementation is degrading, scored and ranked, in days — not a consulting quarter.
The problem
Every downstream decision — attribution, audiences, exec reporting — inherits the rot. Teams usually find out months later, from a number that "looks off," after the bad data has already shipped.
Fields get removed or renamed without tracing which dimensions, metrics, and segments depend on them — they silently return null.
Person-ID resolution drops below threshold. Journeys fragment. Unique counts inflate. No error is thrown — reports just get quietly wrong.
Timezones, lookback windows, and session timeouts change on data views without annotation — breaking historical trend comparisons overnight.
Disabled datasets stay attached to data views. Production ingestion pipelines stop feeding. Test sandboxes stay enabled in prod orgs.
Live demo reports
The audit engine runs against your configuration snapshot (no raw PII — config metadata only) and produces a scored, ranked, evidence-backed report. These are the actual outputs for two synthetic organizations.
northwind_app_push references a schema not present in the registry — reporting on this dataset will fail or silently drop fields.
Person-ID resolution on the Web + Mobile data view is below the 75% threshold, inflating unique visitor counts and fragmenting journeys.
loyalty.tier removed from schema; dimensions "Loyalty Tier" and "Country" now return null/empty across two data views.
"Email Engaged Non-Buyers" dropped from 27,510 to 12,030 members. Large swings indicate a data or definition problem before activation.
meridian_client_portal_events was switched from client_web_events_v1 to _v2 — field-level reporting breaks without a field-mapping audit.
The Client Engagement data view resolves only 61.4% of events to a person ID — well below the 75% floor, fragmenting client journey reporting.
Data view "Meridian Client Engagement" was shifted from America/New_York to America/Chicago, silently invalidating all historical session and day-boundary comparisons.
meridian_aum_snapshot is enabled and tagged production but has ingested 0 records for 13 days — silently degrading every audience built on it.
Deliverables
A polished Config Health & Drift Audit Report generated against your AEP/CJA configuration snapshot — no raw customer PII required, just config metadata via Adobe's APIs or UI exports.
0–100 score with per-domain sub-scores: Schemas, Datastreams, Identity, Derived Fields, Governance, CJA Data Views.
Every finding names the specific object, what changed, and the concrete downstream risk — no vague "review recommended."
Ranked fix list by effort vs. impact. Know what to do Monday morning, not just what is wrong.
A single page a non-technical sponsor can read — summary findings, business risk, and priority actions.
Dan walks your team through findings and remediation, answers questions, and leaves you with the plan.
Async follow-up on the findings as your team digs in — so nothing gets stuck in ambiguity.
Pricing
Senior Adobe/CJA consulting bills $150–$300/hr. A bespoke config audit as a custom engagement runs $10k–$25k and weeks of calendar time. This is the diagnosis, at a fraction of the cost, delivered in days.
Who this is for
The buyer is a technical peer — the Analytics Engineering Lead, Sr. Adobe Analytics / CJA practitioner, or MarTech platform owner who gets paged when a number looks wrong and can't get headcount to audit the config proactively.
Running Adobe CJA/AEP with multiple datasets, custom schemas, identity stitching, and several data views — and living in the platform for 12+ months.
Marketing spend, audience activation, and exec attribution all flow through your AEP implementation — drift here is not an abstraction, it's a revenue risk.
Early-stage or simple Adobe Analytics implementations without CJA/AEP, or orgs that don't use custom schemas or identity stitching.
Get a scored, evidence-backed audit of your AEP/CJA config — or start with a no-pressure discovery call to see if this is the right fit.
Or email directly: d.z.bonomo@gmail.com — response within one business day.