What it is
The aep-cja-toolkit is a written plan to grow AEP Audit into a fuller kit for teams running Adobe Analytics and Customer Journey Analytics (CJA). Many teams are moving from the older Analytics product to CJA, and need to know what they have, whether it is healthy, how old pieces map to new ones, and whether the two systems agree on the numbers. The toolkit would answer each of those with one command.
How it works
As planned, five commands:
inventorytakes a snapshot of a setup (schemas, datasets, data views, report suites, tag rules) and saves it to a file.auditruns health and drift checks on a snapshot and writes a scored report, as AEP Audit does today.mapbuilds an editable workbook that matches old Analytics variables to new CJA components.paritycompares totals between the two systems over sample date ranges, or between two exported CSV files.diffcompares any two snapshots.
It would work offline on exported snapshots, or online with the user's own login. A redact option would strip identifiers before sharing, and a fixtures option would run everything on built-in sample data.
What exists today
- A requirements document (about 1,100 words) with milestones and open questions
- The AEP Audit engine, which would become the
auditcommand - Two fictional sample companies from AEP Audit to reuse as test data
What isn't there yet
- No code; the repository has not been created
- No live connection to Adobe services has been built or tested
- Inventory, map, parity and diff are all on paper only
- No decision yet on packaging or distribution
Under the hood
- Planned in Python 3.11+ with standard libraries for web calls (httpx), data checks (pydantic) and the command line (typer, rich)
- Reports in HTML, JSON and CSV, in the same look as AEP Audit
- Clean-room rule: built only from public Adobe documentation and synthetic data