Notes / Audits

Audit checklists for legacy analytics

8 December 2025

The Legacy Tracker Review is a ten-day engagement. Between those bookings, alumni use a shorter checklist. It is not a full census of every row in the warehouse — that fantasy is how audits never start.

Sample, do not boil the ocean

Take the last 14 days of counts for names in your catalogue plus anything that looks like a duplicate (Levenshtein is enough; you do not need a research paper). Flag names with zero volume, names with a sudden 10× spike, and names that differ only by case.

Owners

If a name has no steward in the RFC, it is a candidate for archive. “Everyone uses it” is not an owner. Event Taxonomy Planning for Apps only sticks when someone can refuse a new parameter.

What the checklist cannot catch

Client-side sampling, consent-mode drops, and store review builds that still emit old names. We mention this in the review readout so finance does not treat the pack as a financial audit. It is a vocabulary audit.