When to rebuild a tracking plan
Not every messy schema needs a rewrite. Signs that a rebuild will pay for itself—and signs that you should patch instead.
Rebuild when two or more product squads cannot answer the same activation question with the same event. Patch when only a few properties are missing on an otherwise consistent plan.
Another rebuild signal: your warehouse contains three generations of onboarding events that nobody dares delete. Historical compatibility is valuable until it blocks every new report.
Plan a rebuild like a product launch. Freeze new event requests for a short window, migrate critical dashboards, then deprecate old names with a clear sunset date.
Budget engineering time for dual-writing during transition. Analytics rebuilds that skip dual-write create a silent month where nobody trusts the numbers—and that month is expensive.